I've not seen that error before. My guess would be that it's a mismatch between XTS and the web services libraries. Are you tied to particular versions of the software? JBossTS 4.2.3.SP5 on JBossAS 4.2.1.GA should be better and will give you a smoother upgrade path as we push out the new features for TS 4.4 milestone releases.
I would prefer to use jboss 4.0.4 GA since it is already in use in the project. But changing to a new jboss shouldn't be to much of a hassle since this part of the project is not too big.
However, even after installing jboss4.2.1GA and jbossts4.2.3.SP5, still the same error appears.
Anyway, installing this example is just a step in solving the main problem: being the creation of a usertransaction, in a separate application. The problem is that the usertransaction is retreived, but it doesn't seem to have any context whatsoever(ut.toString gives "Unknown"). Is there a hands-on tutorial that might solve this problem?
> However, even after installing jboss4.2.1GA and jbossts4.2.3.SP5, still the same error appears.
That sounds like a problem with your environment, as XTS 4.2.3.SP5 demo app runs ok on AS 4.2.1.GA for me. Have you altered any of the libraries in either product, or have alternative versions on the classpath that may be causing issues? Are you building from source or using the binaries?
I'm not aware of changing anything with any specific importance. the classpath and path just hold some references to xmlbeans and java-locations. And I just installed clean versions of the jbossas and jbosstm from binaries. Furthermore I used the 'INSTALL' file in jbosstm and ran the demo... still with the same strange exception.
> the classpath and path just hold some references to xmlbeans and java-locations
What exactly are these? What happens if you run JBossAS with no CLASSPATH set?
Same shit, different day:
with the classpath not set and the path set as: Path=c:\javajdk1.6.0\bin;c:\jre1.6.0;e:\ant\bin;c:\windows\system32
still the same exception is given:
Transaction failed! Cause: java.rmi.RemoteException: Call invocation failed; nested exception is: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
By the way, I tried it on several computers and constantly the same problem occurred... frustrating, especially since no-one else seems to have this problem
Try it on java 5, the app server does not support 6.
nice, those java-versioning issues. However it doesn't completely solve the problem, the following exception comes up:
Transaction failed! Cause: java.rmi.RemoteException: Call invocation failed; nested exception is: java.io.IOException: Could not transmit message
and when the process is ran twice, this exception shows:
Transaction failed! Cause: com.arjuna.wst.WrongStateException
I hope this looks somehow like a familiar problem
thanks in advance
That looks like misconfiguration of the http transport. Are the URLs set correctly in the properties file? Are you using a real hostname or 'localhost'? Any strange routing or firewalling?
Hi, after recompiling a few times (switching to a different Java(5)) and changing some parameters, like localhost, I found out that the parameters in the web.xml from xts-demo.war where not adapted. After changing that manually, the demo worked!
thanks for all the help!