The client is a webapp running on the server hosting JBM.
We tried to add the aop libs inside the /lib of our server folder.
Nothing better...
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221188#4221188
Reply to the post :
http://www.jboss.org/index.h
It seems that something didn't work correctly while installing the aspects on
your client. I have seen that when users didn't follow version recommendations
(AOP on client for instance) or missing other libraries.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p
May you please elaborate on the classpath error?
It seems that the state of the connectionState of the clientConnectionDelegate
of the XAConnection is null.
connectionState does not appear to be serializable.
Does that mean that the same XAConnection cannot be shared between the nodes?
If it
The NPE seems some classPath issue on trying to install the AOP.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220784#4220784
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220784
__
Hello,
thx for your answer, we finally had time to try a version using XA.
We tried to share in cluster the XAConnection so that when a node fails the
transaction can continue on the other nodes using this shared connection:
| XASession session = mySharedXAConnection.createXASession();
|
If you are using an XASession then you can join an already running tx if you
know the Xid, just specify the Join flags:
| XAResource res = xaSession.getXAResource();
| res.start(xid, XAResource.TMJOIN);
|
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4