• Post Reply Bookmark Topic Watch Topic
  • New Topic

XA Transactions don't release connections

 
Mohammad Norouzi
Ranch Hand
Posts: 71
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello
We have configured a distributed transaction in our application server in order to support transaction between Java and .NET running in a service call. The .NET clients are served by webservices and we are using OpenJPA. The problem is that after a bunch of service calls the app. server cannot allocate more connection and it seems the acquired connections won't be released. However this problem will remove if we change it into normal transaction but in this case we can't join the transaction of .NET to Java systems.

I hope you share your experience on this

here is the error:
------
[#|2009-12-21T18:29:24.484-0500|SEVERE|sun-appserver9.1|com.sun.xml.ws.server.sei.EndpointMethodHandler|_ThreadID=27;_ThreadName=httpSSLWorkerThread-8080-6;_RequestID=a56fb08a-bf34-4f98-85eb-989ed77b23ab;|Exception thrown from bean; nested exception is: <openjpa-1.2.1-r752877:753278 fatal general error> org.apache.openjpa.persistence.PersistenceException: Error in allocating a connection. Cause: In-use connections equal max-pool-size and expired max-wait-time. Cannot allocate more connections.
javax.ejb.TransactionRolledbackLocalException: Exception thrown from bean; nested exception is: <openjpa-1.2.1-r752877:753278 fatal general error> org.apache.openjpa.persistence.PersistenceException: Error in allocating a connection. Cause: In-use connections equal max-pool-size and expired max-wait-time. Cannot allocate more connections.
<openjpa-1.2.1-r752877:753278 fatal general error> org.apache.openjpa.persistence.PersistenceException: Error in allocating a connection. Cause: In-use connections equal max-pool-size and expired max-wait-time. Cannot allocate more connections.
-----

Thanks
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!