java.sql.SQLTransactionRollbackException: A lock could not be obtained within the time requested

2 messages Options
Embed this post
Permalink
BMN

java.sql.SQLTransactionRollbackException: A lock could not be obtained within the time requested

Reply Threaded More More options
Print post
Permalink
Some javascript/style in this post has been disabled (why?)

Hi,

This is regarding an issue while logging of our request in to file.

we are using IEP component in cluster enviornment to get log in our webservices.while testing with small request(1,10 threads )using SOAPUI(testing tool for Webservices) it is working fine but as we increase(20,30,50) the thread size we are getting some fail test results.

Below is the details of Exception in server log we get.

[#|2009-06-30T09:55:22.668+0100|SEVERE|sun-appserver9.1|com.sun.jbi.engine.iep.core.runtime.IEPEngine|_ThreadID=154;_ThreadName=Thread-547;_RequestID=3ab91b92-0083-4997-a1ac-54754d3a069a;|IEPSEaja02029: Fail to retrieve processing-state of event processor: 0

java.sql.SQLTransactionRollbackException: A lock could not be obtained within the time requested

at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)

at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)

at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)

at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)

at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)

at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)

at org.apache.derby.impl.jdbc.EmbedResultSet.closeOnTransactionError(Unknown Source)

at org.apache.derby.impl.jdbc.EmbedResultSet.movePosition(Unknown Source)

at org.apache.derby.impl.jdbc.EmbedResultSet.next(Unknown Source)

at com.sun.jbi.engine.iep.core.runtime.util.Util.getPrevTimestampToCheck(Util.java:2009)

at com.sun.jbi.engine.iep.IEPSEOutOnlyThread.run(IEPSEOutOnlyThread.java:228)

Caused by: java.sql.SQLException: A lock could not be obtained within the time requested

at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)

at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source)

... 11 more

|#]

[#|2009-06-30T09:56:22.681+0100|SEVERE|sun-appserver9.1|com.sun.jbi.engine.iep.core.runtime.IEPEngine|_ThreadID=154;_ThreadName=Thread-547;_RequestID=3ab91b92-0083-4997-a1ac-54754d3a069a;|IEPSEaja02029: Fail to retrieve processing-state of event processor: 1

java.sql.SQLTransactionRollbackException: A lock could not be obtained within the time requested

at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)

at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)

at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)

at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)

at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)

at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)

at org.apache.derby.impl.jdbc.EmbedResultSet.closeOnTransactionError(Unknown Source)

at org.apache.derby.impl.jdbc.EmbedResultSet.movePosition(Unknown Source)

at org.apache.derby.impl.jdbc.EmbedResultSet.next(Unknown Source)

at com.sun.jbi.engine.iep.core.runtime.util.Util.getPrevTimestampToCheck(Util.java:2009)

at com.sun.jbi.engine.iep.IEPSEOutOnlyThread.run(IEPSEOutOnlyThread.java:228)

Caused by: java.sql.SQLException: A lock could not be obtained within the time requested

at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)

at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source)

... 11 more

|#]

can anybody help me out this?

Thanks

-Brij

Michael.Czapski

Re: java.sql.SQLTransactionRollbackException: A lock could not be obtained within the time requested

Reply Threaded More More options
Print post
Permalink
Some javascript/style in this post has been disabled (why?)
Hello, Brij.

I am afraid I can not help you with this issue. You will be steerer served by submitting this to the [hidden email] (I am sending this to that mailing list).

Regards

Michael

Brij Mohan Negi (India) wrote:

Hi,

This is regarding an issue while logging of our request in to file.

we are using IEP component in cluster enviornment to get log in our webservices.while testing with small request(1,10 threads )using SOAPUI(testing tool for Webservices) it is working fine but as we increase(20,30,50) the thread size we are getting some fail test results.

Below is the details of Exception in server log we get.

[#|2009-06-30T09:55:22.668+0100|SEVERE|sun-appserver9.1|com.sun.jbi.engine.iep.core.runtime.IEPEngine|_ThreadID=154;_ThreadName=Thread-547;_RequestID=3ab91b92-0083-4997-a1ac-54754d3a069a;|IEPSEaja02029: Fail to retrieve processing-state of event processor: 0

java.sql.SQLTransactionRollbackException: A lock could not be obtained within the time requested

at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)

at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)

at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)

at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)

at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)

at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)

at org.apache.derby.impl.jdbc.EmbedResultSet.closeOnTransactionError(Unknown Source)

at org.apache.derby.impl.jdbc.EmbedResultSet.movePosition(Unknown Source)

at org.apache.derby.impl.jdbc.EmbedResultSet.next(Unknown Source)

at com.sun.jbi.engine.iep.core.runtime.util.Util.getPrevTimestampToCheck(Util.java:2009)

at com.sun.jbi.engine.iep.IEPSEOutOnlyThread.run(IEPSEOutOnlyThread.java:228)

Caused by: java.sql.SQLException: A lock could not be obtained within the time requested

at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)

at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source)

... 11 more

|#]

[#|2009-06-30T09:56:22.681+0100|SEVERE|sun-appserver9.1|com.sun.jbi.engine.iep.core.runtime.IEPEngine|_ThreadID=154;_ThreadName=Thread-547;_RequestID=3ab91b92-0083-4997-a1ac-54754d3a069a;|IEPSEaja02029: Fail to retrieve processing-state of event processor: 1

java.sql.SQLTransactionRollbackException: A lock could not be obtained within the time requested

at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)

at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)

at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)

at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)

at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)

at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)

at org.apache.derby.impl.jdbc.EmbedResultSet.closeOnTransactionError(Unknown Source)

at org.apache.derby.impl.jdbc.EmbedResultSet.movePosition(Unknown Source)

at org.apache.derby.impl.jdbc.EmbedResultSet.next(Unknown Source)

at com.sun.jbi.engine.iep.core.runtime.util.Util.getPrevTimestampToCheck(Util.java:2009)

at com.sun.jbi.engine.iep.IEPSEOutOnlyThread.run(IEPSEOutOnlyThread.java:228)

Caused by: java.sql.SQLException: A lock could not be obtained within the time requested

at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)

at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source)

... 11 more

|#]

can you help me out for the same?

Thanks

-Brij

 

From: [hidden email] [[hidden email]]
Sent: Wednesday, June 24, 2009 12:44 PM
To: [hidden email]
Subject: Database BC, BPEL SE and MySQL don't play nicely together - "Too many connections" from MySQL

I have a multi-operation web service implemented following the instructions in "GlassFish ESB v 2.1 - Creating a Healthcare Facility Web Service Provider", at http://blogs.sun.com/javacapsfieldtech/entry/glassfish_esb_v_2_1. As part of the solution there is a Soap UI testing project. When I execute the opGetFacList, or opGetFacDetails, or both 15 times I get an exception in server.log that says "Too many open connections". It seems to me that the BPEL SE or the Database BC of the JBI container do not release connections between service invocations. The pool gets exhausted and the service comes to a grinding halt.

The Soap UI response looks like:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP-ENV:Body>
      <SOAP-ENV:Fault>
         <faultcode>SOAP-ENV:Server</faultcode>
         <faultstring><![CDATA[BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;jbi:message xmlns:sxeh=&quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&quot; type=&quot;sxeh:faultMessage&quot; version=&quot;1.0&quot; xmlns:jbi=&quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&quot;&gt;&lt;jbi:part&gt;Error occured while looking up jndi resource with jndi name.&lt;/jbi:part&gt;&lt;/jbi:message&gt;. Sending errors for the pending requests in the process scope before terminating the process instance]]></faultstring>
         <faultactor>sun-bpel-engine</faultactor>
         <detail>
            <detailText><![CDATA[BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;jbi:message xmlns:sxeh=&quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&quot; type=&quot;sxeh:faultMessage&quot; version=&quot;1.0&quot; xmlns:jbi=&quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&quot;&gt;&lt;jbi:part&gt;Error occured while looking up jndi resource with jndi name.&lt;/jbi:part&gt;&lt;/jbi:message&gt;. Sending errors for the pending requests in the process scope before terminating the process instance
   Caused by: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=DBList, portType={http://j2ee.netbeans.org/wsdl/FacListDB}jdbcPortType, operation=opGetFacList)
BPCOR-6129: Line Number is 44
BPCOR-6130: Activity Name is Invoke1
   Caused by: Error occured while looking up jndi resource with jndi name.
   Caused by: Error in allocating a connection. Cause: Connection could not be allocated because: Data source rejected establishment of connection,  message from server: &quot;Too many connections&quot;]]></detailText>
         </detail>
      </SOAP-ENV:Fault>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

The server.log extract is at the end of this message.

I did not have this issue doing the equivalent in Java CAPS 6 Repository with eInsight BPEL 1.0 and teh JDBC eWay.
I am using GlassFish ESB v2.1, RC2 distribution, from about a week before GA with JDK 1.6.0_10.

Please advise.

Regards

Michael
--

--

<!--[if !vml]--><!--[endif]-->

Podcast 1   Podcast 2


Michael Czapski, BSc Computing, MSc eBus.Tech.
Principal Field Technologist, Software
SOA/BI/Java CAPS

Sun Microsystems
33 Berry Street, North Sydney
NSW 2060 Australia
Phone +61 2 9466 9427
Email [hidden email]

Blog: http://blogs.sun.com/javacapsfieldtech/

LinkedIn: MichaelCzapski

Skype: michaelczapski

Screencasts and Document Archives: http://mediacast.sun.com/users/Michael.Czapski-Sun

[#|2009-06-24T17:11:55.156+1000|INFO|sun-appserver2.1|sun-database-binding.org.glassfish.openesb.databasebc.OutboundMessageProcessor|_ThreadID=29;_ThreadName=pool-5-thread-2;Context=context;|Executing SQL....select * from ui_facility where facility_code = ?|#]

[#|2009-06-24T17:11:55.171+1000|WARNING|sun-appserver2.1|javax.enterprise.resource.resourceadapter|_ThreadID=29;_ThreadName=pool-5-thread-2;cp_pblog_XA;Connection could not be allocated because: Data source rejected establishment of connection,  message from server: "Too many connections";Context=context;_RequestID=9102c836-93e6-49a7-8de5-7e3ed785c86a;|RAR5117 : Failed to obtain/create connection from connection pool [ cp_pblog_XA ]. Reason : Connection could not be allocated because: Data source rejected establishment of connection,  message from server: "Too many connections"|#]

[#|2009-06-24T17:11:55.171+1000|WARNING|sun-appserver2.1|javax.enterprise.resource.resourceadapter|_ThreadID=29;_ThreadName=pool-5-thread-2;Error in allocating a connection. Cause: Connection could not be allocated because: Data source rejected establishment of connection,  message from server: "Too many connections";Context=context;_RequestID=9102c836-93e6-49a7-8de5-7e3ed785c86a;|RAR5114 : Error allocating connection : [Error in allocating a connection. Cause: Connection could not be allocated because: Data source rejected establishment of connection,  message from server: "Too many connections"]|#]

[#|2009-06-24T17:11:55.171+1000|SEVERE|sun-appserver2.1|sun-database-binding.org.glassfish.openesb.databasebc.OutboundMessageProcessor|_ThreadID=29;_ThreadName=pool-5-thread-2;Context=context;_RequestID=9102c836-93e6-49a7-8de5-7e3ed785c86a;|Failed to write message:.
java.lang.Exception: Failed to denormalize message.
    at org.glassfish.openesb.databasebc.OutboundMessageProcessor.processInOut(OutboundMessageProcessor.java:583)
    at org.glassfish.openesb.databasebc.OutboundMessageProcessor.execute(OutboundMessageProcessor.java:276)
    at org.glassfish.openesb.databasebc.OutboundMessageProcessor.run(OutboundMessageProcessor.java:171)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:619)
Caused by: java.sql.SQLException: Error occured while executing SQL.select * from ui_facility where facility_code = ? Reason: Error in allocating a connection. Cause: Connection could not be allocated because: Data source rejected establishment of connection,  message from server: "Too many connections" SQLState: null ErrorCode: 0
    at org.glassfish.openesb.databasebc.OutboundMessageProcessor.executeOutboundSQLSelect(OutboundMessageProcessor.java:1385)
    at org.glassfish.openesb.databasebc.OutboundMessageProcessor.processInOut(OutboundMessageProcessor.java:575)
    ... 5 more
|#]

[#|2009-06-24T17:11:55.171+1000|SEVERE|sun-appserver2.1|sun-database-binding.org.glassfish.openesb.databasebc.OutboundMessageProcessor|_ThreadID=29;_ThreadName=pool-5-thread-2;Context=context;_RequestID=9102c836-93e6-49a7-8de5-7e3ed785c86a;|Unexpected exception: null source
java.lang.IllegalArgumentException: null source
    at java.util.EventObject.<init>(EventObject.java:38)
    at javax.sql.StatementEvent.<init>(StatementEvent.java:39)
    at com.mysql.jdbc.jdbc2.optional.JDBC4PreparedStatementWrapper.close(JDBC4PreparedStatementWrapper.java:70)
    at org.glassfish.openesb.databasebc.OutboundMessageProcessor.processInOut(OutboundMessageProcessor.java:760)
    at org.glassfish.openesb.databasebc.OutboundMessageProcessor.execute(OutboundMessageProcessor.java:276)
    at org.glassfish.openesb.databasebc.OutboundMessageProcessor.run(OutboundMessageProcessor.java:171)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:619)
|#]

[#|2009-06-24T17:11:55.171+1000|INFO|sun-appserver2.1|sun-database-binding.org.glassfish.openesb.databasebc.OutboundMessageProcessor|_ThreadID=29;_ThreadName=pool-5-thread-2;Context=context;|Finished processing outbound messages.|#]

[#|2009-06-24T17:11:55.203+1000|WARNING|sun-appserver2.1|com.sun.jbi.engine.bpel.BPELSEHelper|_ThreadID=39;_ThreadName=sun-bpel-engine-thread-0;Process Instance Id=192.168.60.4:631061e5:122111901cf:-7e7b;Service Assembly Name=FacilitySvc_CA;BPEL Process Name=facilitySvc_BM;_RequestID=e91b355f-c9c6-4c53-bd15-d93d90485a1b;|BPJBI-6001: Sending ERROR status (Service Name = {http://enterprise.netbeans.org/bpel/FacilitySvc_BM/facilitySvc_BM}FacilutyRR, Endpoint Name = FacilitySvcPortTypeRole_myRole, Operation Name = {urn:Sun:Michael.Czapski:WSDLs:/FacilitySvc}opGetFacDetails, Message Exchange Id = 162912225252056-45757-134651203151560199)
 Error properties
  com.sun.jbi.crl.faultcode = Server
  com.sun.jbi.crl.faultstring = BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>Failed to denormalize message.</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance
  com.sun.jbi.crl.faultactor = sun-bpel-engine
  com.sun.jbi.crl.faultdetail =
   BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>Failed to denormalize message.</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance
   Caused by: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=DBDetails, portType={http://j2ee.netbeans.org/wsdl/FacDetailsDB}jdbcPortType, operation=opGetFacDetails)
BPCOR-6129: Line Number is 88
BPCOR-6130: Activity Name is Invoke2
   Caused by: Failed to denormalize message.
   Caused by: Error occured while executing SQL.select * from ui_facility where facility_code = ? Reason: Error in allocating a connection. Cause: Connection could not be allocated because: Data source rejected establishment of connection,  message from server: "Too many connections" SQLState: null ErrorCode: 0|#]

[#|2009-06-24T17:11:55.203+1000|SEVERE|sun-appserver2.1|com.sun.jbi.httpsoapbc.OutboundMessageProcessor|_ThreadID=40;_ThreadName=HTTPBC-InboundReply-2;_RequestID=d6b53d1c-f872-4b6d-8012-ad24b7dacd6a;|HTTPBC-E00720: Provider for service [{urn:Sun:Michael.Czapski:WSDLs:/FacilitySvc}FacilitySvcService] endpoint [FacilitySvcPort] responded with an error status. Error detail is: BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>Failed to denormalize message.</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance|#]

[#|2009-06-24T17:11:55.218+1000|WARNING|sun-appserver2.1|com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.BPELProcessInstanceImpl|_ThreadID=39;_ThreadName=sun-bpel-engine-thread-0;Process Instance Id=192.168.60.4:631061e5:122111901cf:-7e7b;Service Assembly Name=FacilitySvc_CA;BPEL Process Name=facilitySvc_BM;_RequestID=e91b355f-c9c6-4c53-bd15-d93d90485a1b;|BPCOR-6151: The process instance has been terminated because a fault was not handled; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>Failed to denormalize message.</jbi:part></jbi:message>
com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=DBDetails, portType={http://j2ee.netbeans.org/wsdl/FacDetailsDB}jdbcPortType, operation=opGetFacDetails)
BPCOR-6129: Line Number is 88
BPCOR-6130: Activity Name is Invoke2
    at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:969)
    at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:542)
    at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:182)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:162)
    at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1031)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:289)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1291)
    at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:374)
    at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:231)
    at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:183)
Caused by: java.lang.Exception: Failed to denormalize message.
    at org.glassfish.openesb.databasebc.OutboundMessageProcessor.processInOut(OutboundMessageProcessor.java:583)
    at org.glassfish.openesb.databasebc.OutboundMessageProcessor.execute(OutboundMessageProcessor.java:276)
    at org.glassfish.openesb.databasebc.OutboundMessageProcessor.run(OutboundMessageProcessor.java:171)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:619)
Caused by: java.sql.SQLException: Error occured while executing SQL.select * from ui_facility where facility_code = ? Reason: Error in allocating a connection. Cause: Connection could not be allocated because: Data source rejected establishment of connection,  message from server: "Too many connections" SQLState: null ErrorCode: 0
    at org.glassfish.openesb.databasebc.OutboundMessageProcessor.executeOutboundSQLSelect(OutboundMessageProcessor.java:1385)
    at org.glassfish.openesb.databasebc.OutboundMessageProcessor.processInOut(OutboundMessageProcessor.java:575)
    ... 5 more
|#]




--

--

Podcast 1   Podcast 2

 

Michael Czapski, BSc Computing, MSc eBus.Tech.
Principal Field Technologist, Software
SOA/BI/Java CAPS

Sun Microsystems
33 Berry Street, North Sydney
NSW 2060 Australia
Phone +61 2 9466 9427
Email [hidden email]

Blog: http://blogs.sun.com/javacapsfieldtech/

LinkedIn: MichaelCzapski

Skype: michaelczapski

Screencasts and Document Archives: http://mediacast.sun.com/users/Michael.Czapski-Sun

JavaOne 2008 SYS-CON.TV Interview with Michael Czapski and Brendan Marry: http://tv.sys-con.com/node/674561