Issue Description:
Orchestration designer version is 6.0.13 and Tomcat version is 7.0.53, where the DB connections available in the connection pool had gone to deadlock. Hence new calls are not able to get the DBConnection from the DB connection pool. Application is using the Avaya DBOP operation. They are facing the below issue when application is running on Tomcat7.

The application is now working fine on TOMCAT 6 and this needs to be upgraded to TOMCAT 7 asap, they are worried if they move the application back to TOMCAT 7 with any proper confirmation they might end up again getting into the same deadlock exceptions that happened last week.


Snippet from the app trace:
-------------------------------

* D09EB9846C4CE5B1BE70D82DF6EB6FC9:/EIB_IVR_SERVION : Executing DB statement : [{ call ODS.PROC_EIB_UPDATE_ENDCALL ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) }]

Line 71795: 07/03/2016 18:17:59:222 INFO - D09EB9846C4CE5B1sBE70D82DF6EB6FC9:/EIB_IVR_SERVION : Capturing exception [java.sql.SQLException]. Message [invalid arguments in call]


* Data Base Service org.apache.tomcat.dbcp.dbcp.SQLNestedException: Could not retrieve connection info from pool

at org.apache.tomcat.dbcp.dbcp.datasources.PerUserPoolDataSource.getPooledConnectionAndInfo(PerUserPoolDataSource.java:385)

at org.apache.tomcat.dbcp.dbcp.datasources.InstanceKeyDataSource.getConnection(InstanceKeyDataSource.java:669)

at com.wipro.host.DataBaseService.getDBConnection(DataBaseService.java:63)


Please advice.

Can you describe more of the problem behavior? Does it not work at all or you get the problem intermittently? What database are you using? This doesn't look like a database driver from the database vendor. You may want to try a different database driver, preferably one from the database vendor.

Wilson,

We got this issue when we moved the OD 6 application from Tomcat 6 to Tomcat 7, after few days the dbop DB connections stalled. Hence new calls were not able to get the DBConnection from the connection pool. Only after tomcat restart db connection worked. Once we got this problem we reverted back the application to tomcat 6, since then it is working fine in tomcat 6.

Below are the information you requested:
Database type: Oracle
Version: 9
JDBC jar: ojdbc14.jar(downloaded from oracle site)
Complete stack trace:
DEBUG - CE6775F6BF4CD0F918CAA45FF93AAEFC:/EIB_IVR_SERVION : Executing DB statement : [{ call ODS.PROC_EIB_FINANCIALTRANS_UPD ( ?, ?, ?, ?, ?) }]
INFO - CE6775F6BF4CD0F918CAA45FF93AAEFC:/EIB_IVR_SERVION : Capturing exception [javax.servlet.ServletException]. Message [ EXCEPTION>
java.sql.SQLException: invalid arguments in call
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.check_error(DBError.java:1160)
at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:183)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:346)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:468)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:314)
at java.sql.DriverManager.getConnection(DriverManager.java:579)
at java.sql.DriverManager.getConnection(DriverManager.java:221)
at org.apache.tomcat.dbcp.dbcp.cpdsadapter.DriverAdapterCPDS.getPooledConnection(DriverAdapterCPDS.java:177)
at org.apache.tomcat.dbcp.dbcp.cpdsadapter.DriverAdapterCPDS.getPooledConnection(DriverAdapterCPDS.java:132)
at org.apache.tomcat.dbcp.dbcp.datasources.InstanceKeyDataSource.testCPDS(InstanceKeyDataSource.java:749)
at org.apache.tomcat.dbcp.dbcp.datasources.PerUserPoolDataSource.registerPool(PerUserPoolDataSource.java:460)
at org.apache.tomcat.dbcp.dbcp.datasources.PerUserPoolDataSource.getPooledConnectionAndInfo(PerUserPoolDataSource.java:373)
at org.apache.tomcat.dbcp.dbcp.datasources.InstanceKeyDataSource.getConnection(InstanceKeyDataSource.java:669)
at org.apache.tomcat.dbcp.dbcp.datasources.InstanceKeyDataSource.getConnection(InstanceKeyDataSource.java:653)
at com.avaya.sce.runtime.jdbc.Database.open(Database.java:61)
at com.avaya.sce.runtime.jdbc.Database.open(Database.java:99)
at com.avaya.sce.runtime.connectivity.db.DbQuery.executeSQL(DbQuery.java:191)
at com.avaya.sce.runtime.connectivity.db.DbQuery.execute(DbQuery.java:134)
at com.avaya.sce.runtime.Data.evaluateActions(Data.java:191)
at flow.subflow.WaterAndElectricityPayments.updateFinanicalDetails_Success.executeDataActions(updateFinanicalDetails_Success.java:83)
at com.avaya.sce.runtime.Data.handleRequest(Data.java:104)
at com.avaya.sce.runtime.AppServlet.processRequest(AppServlet.java:96)
at com.avaya.sce.runtime.SCEServlet.requestHandler(SCEServlet.java:283)
at com.avaya.sce.runtime.SCEServlet.doGet(SCEServlet.java:182)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1070)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:722)
...............
07/03/2016 15:10:05:115 DEBUG - D387C66B591C4419F396ED33C4E28256:/EIB_IVR_SERVION : Executing DB statement : [{ call ODS.PROC_EIB_MASTERCALLDETAILS ( ?, ?, ?, ?, ?) }]
07/03/2016 15:10:08:990 INFO - 5C979638DD9370D74AEBED2BBF46E4B9:/EIB_IVR_SERVION : Capturing exception [java.sql.SQLException]. Message [invalid arguments in call]
...............

07/03/2016 13:33:06:612 INFO - 4175A5A1B1523F3F8455BFE00E30D749:/EIB_IVR_SERVION : Using SCESession 4175A5A1B1523F3F8455BFE00E30D749:/EIB_IVR_SERVION servlet : Insert_Transaction_Log-INS_TRANS_HISTORY
07/03/2016 13:33:06:612 DEBUG - 4175A5A1B1523F3F8455BFE00E30D749:/EIB_IVR_SERVION : Executing DB statement : [INSERT INTO ODS.EIB_TRANS_HISTORY_1 ( CALLERID, IVRREFID, TRANSACTIONID, TRANSACTIONTYPE, FROMACCT, TOACCT, CONSUMERNO, RESULT, RESULTDESC, CCID, ADDITIONALINFO, REFERENCENO, PYMTUPDTREF, SOURCECURRENCY, DESTCURRENCY, AMOUNT, CHANNEL, AGENT, COMMENTS, ENTEREDBY, PACKET_NAME ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )]
...............

I am not sure what really causes the disruption. I highly doubt this has anything to do with the Tomcat version. It could be a network issue. However, this problem sounds like one you can solve by setting a few parameters with the DBCP for the database connection pool to recover by itself. Please refer to the following existing post which has the details on the parameters:

http://www.devconnectprogram.com/forums/posts/list/46.page#p176