Recently the Transactions Team delivered a training course to the Red Hat support staff to help them support JBossTS. As part of the course I delivered a demo configuring XTS (our Web service Transactions implementation) and debugging common issues. I created myself a script to help make the demo run smoothly. As I was preparing the demo I realized that this could make a great community resource, so I put a little bit more effort in and added some commentary.
Here's the result:
http://community.jboss.org/wiki/XTSWhirlwindTour
The XTS Whirlwind Tour covers:
- A simple single server scenario
- A simple distributed scenario
- Running an XTS server behind a gateway (Apache)
- Recovery
- Bridging WS-AT to JTA
- Many common issues and how to debug them.
I hope you find this useful. Remember, this is a community document so please get involved, comments are strongly encouraged!
If you find this type of document useful, please let us know as we may be able to do more in the future.
Enjoy!
3 comments:
Hi,
We are using JBoss 5.1.0.GA for deploying our application on the mainframe environment.
The problem is that in a secure environment, we need to control the port assignment for the transaction service - so we went ahead and changed the value of the property "com.arjuna.ats.internal.arjuna.utils.SocketProcessIdPort" to a port number of our choice (from the default value of "0").
property name="com.arjuna.ats.internal.arjuna.utils.SocketProcessIdPort" value="0"
changed to
property name="com.arjuna.ats.internal.arjuna.utils.SocketProcessIdPort" value="28084"
(in the jbossts-properties.xml file).
Unfortunately, even after changing this value, the port number which was being assigned is a random one only. We also verified that port 28084 is free, and was ready to be assigned/used.
Can you help us out on this - by explaning why does changing the property value in the jbossts-properties.xml doesnt have any effect on the random port assignment?
Thanks & Regards,
Suman.
Hi Suman,
I believe this got answered over on our forums?
Tom
Post a Comment