I've been experimenting with WS-Atomic Transaction
for a number of years now, though none of that work has made it past the POC stages...until now. Then, recently I've started working on a web service that made use of WS-AT to ensure that data was committed atomically between two distinct products in the stack, both of which were running in separate WebLogic managed servers. Everything was going just fine until we enabled the use of TransactionalFeature
on the web service proxies and all hell broke loose...
None of the WS-AT enabled web service calls would work and failed with the following exception...
This was strange because all of the code was dot-to-dot as per the documentation
and the data source connection pool was set up with the oracle.jdbc.xa.client.OracleXADataSource
driver. It should have worked.
I figured that there had to be some problem with the data source still, so I went looking around. And I didn't have to go far because the Transaction
configuration tab revealed the problem.
The "Use XA Data Source Interface"
option was not enabled! The fix was of course to enable this option and then restart WebLogic. Once that was done all WS-AT calls worked perfectly.
So the exception message may not have been very intuitive but the fix certainly was. It pays to inspect configuration on the managed server side when using new features that depend on the environment being configured correctly first. Lesson learned - don't assume that all configuration is going to be as expected!
Hope you found this post useful...
...so please read on! I love writing articles that provide beneficial information,
tips and examples to my readers. All information on my blog is provided free of
charge and I encourage you to share it as you wish. There is a small favour I ask in return however -
engage in comments below, provide feedback, and if you see mistakes let me know.
If you want to show additional support and help me pay for web hosting and
domain name registration,
donations, no matter how small, are always welcome!
Use of any information contained in this blog post/article is subject to this disclaimer
Other posts you may like...