I suspect your problem arises from using a Synchronization to update JBC. JBC itself uses a Synchronization to control replication of transactional changes around the cluster. If your Synchronization's beforeCompletion is executed by the TransactionManager after JBC's, I'm not sure what will happen. Are you able to ensure that your Synchronization is registered with the transaction before any call goes into JBC?
I'm not sure from your original post -- do you see this with both pessimistic and optimistic locking?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995664#3995664
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995664
"yahro" wrote : Hi guys,
| as far as I know in 2.0.0B2, in launch configuration tabs are mislabeled - put -u username -p password in Stop tab instead of Twiddle tab and it works fine...
This is correct and probably should be logged as a bug in JIRA.
Taking this into account this is what you should set
In the twiddle tab (which is really shutdown):
| -S -s <server>:1099 -a jmx/rmi/RMIAdaptor --user=<user> --password=<password>
In the shutdown tab (which is really twiddle):
-s <server>:1099 -a jmx/rmi/RMIAdaptor --user=<user> --password=<password>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995659#3995659
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995659