I was investigating
GERONIMO-3354. Found that the exception
getting thrown was due to an XAResource getting passed to the the
geronimo transaction manager instead of a NamedXAResource .
To fix this we need to change the method
public MessageEndpoint createEndpoint(XAResource xaResource) throws UnavailableException in
In this method in the case of using the Geronimo Transaction Manager we need to pass a NamedXAResource if we need transaction logging to function.
Directly passing a NamedXAResource will fix this problem at the openEJB side for now but we need to bring in a layer of abstraction since the NamedXAResource is a geronimo TM specific class and in OpenEJB standalone the TM must be pluggable.
For the time being its acceptable to use NamedXAResource.
This requires a fix in AMQ also to work . The JIRA in question is
|Fix Version/s||3.0 [ 12312805 ]|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Fix Version/s||3.0.x [ 12312806 ]|
|Resolution||Fixed [ 1 ]|
|Assignee||David Jencks [ djencks ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|163d 23h 23m||1||David Jencks||15/Mar/08 07:05|