For such scenario you should change the Tx system from JTA to JTS.
There is a ant script to change that (it has worked for me years ago) in docs/examples/transactions see the README file.
After that you the transaction is propagated to the remote server and will follow commit/rollback.
In my understanding the container decide what you get back if you do a lookup, as you are in a managed environment you get the ServerVM* from the server.
At client side this is a implementation which can not run in a managed environment.
Thanks Wolf-Dieter Fink. This is what other guys at the forum have told me in the Transaction Space (can't thank Tom and Michael enough) i.e. to change to JTS from JTA. I have changed my local machine's JBoss to use JTS using that very script. I have raised a request to get the remote JBoss to use JTS( I do not have the permissions to do that). But I just want to confirm that this is a normal case that you get ServerVMClientUserTransaction when doing a lookup on "UserTransaction" from a JBoss client... I just hope that I am not doing something wrong here....
You might use a 'fake' application with another server which you can change to JTS to check that the Tx work as you expect.
I think the problem is that you have to do the change in a productional environment and everybody need to be sure that this will not have bad impacts.
I understand what you are saying but this is a 3rd party owned tool so we don't have much leverage to 'try' things out.... But I've raised the request already... Let's just hope it works out...