开发者

WebSphere local transaction containment boundary issue J2CA0086W

开发者 https://www.devze.com 2023-01-16 20:34 出处:网络
In WebSphere, if you code opens two concurrent database connections, you get an error of the form: J2CA0086W: Shareable connection MCWrapper id 556e556eManaged connection WSRdbManagedConnectionImpl@5

In WebSphere, if you code opens two concurrent database connections, you get an error of the form:

J2CA0086W: Shareable connection MCWrapper id 556e556e Managed connection WSRdbManagedConnectionImpl@52365236 State:STATE_TRAN_WRAPPER_INUSE from resource jdbc/abc was used within a local transaction containment boundary.

Our framework allows us to do so (nested transactions which can be on a separate conn开发者_StackOverflowection or multiple named transactions). I've seen lots of references to turning off some switch in WebSphere to turn on connection sharing but no details on how to set this flag. Can someone point me to the steps to achieve this?

Specifically, if you see this article: http://www-01.ibm.com/support/docview.wss?rs=180&context=SSEQTP&dc=DB520&dc=D600&dc=DB530&dc=D700&dc=DB500&dc=DB540&dc=DB510&dc=DB550&q1=j2ca0086w&uid=swg21121449&loc=en_US&cs=utf-8&lang=en

under "Resolving the problem" I want to know how to set the connection pool to be unshareable (assuming that indeed solves the problem).


What version of IBM WAS are you using? If you have WAS 8, go to Resources-> JDC-> Datasources-> your datasources -> WebSphere Application Server properties -> Datasources no transactional.

Sorry for my english.


The message happens when dataSource.getConnection() is called twice in a servlet. The datasource jdbc/oracle is lookup from local reference. Call it once and reuse the connection or call con.close() before doing the 2nd getConnection()

0

精彩评论

暂无评论...
验证码 换一张
取 消

关注公众号