ASA9 to SA12 migration JDBC problems ...

[former_SQLA_member1694894]

Hi all We've a consolidated Web Application that works on Linux using:

• Tomcat 7.0.22
• JDK 1.6.0_27 (64bit)
• ASA 9.0.2.3340 (64bit)
• JConnect 6.0 build 25570 for JDBC 3.0 (jconn3.jar)

... NO PROBLEM for many years ... Now we've planned to migrate to SA12 using:

• Tomcat 7.0.22 (same version)
• JDK 1.6.0_27 (same version)
• SA 12.0.1.3519 (64bit)
• SqlAnywhere JDBC driver (sajdbc4.jar)

All works (apparently) fine for a few days ...but, we started experiencing Tomcat crashes (while SA12 server continues to function properly) with the following exception:

2012-04-20 07:51:20,895 [http-bio-8080-exec-9] WARN  jplus.data.GenericDataSource - ping failed:  [Sybase][JDBC Driver][SQL A
nywhere]Connection was terminated
java.sql.SQLException: [Sybase][JDBC Driver][SQL Anywhere]Connection was terminated
        at sybase.jdbc4.sqlanywhere.IIStatement.execute(Native Method)
        at sybase.jdbc4.sqlanywhere.IStatement.execute(IStatement.java:309)
        at jplus.data.GenericDataSource.ping(GenericDataSource.java:832)
        at jplus.data.GenericDataSource.getConnection(GenericDataSource.java:511)
        at jplus.web.jsf.AbstractApplication.getConnection(AbstractApplication.java:1175)
        at jplus.web.jsf.AbstractApplication.getConnection(AbstractApplication.java:1164)
        at ergon.Session.authenticate(Session.java:618)
        at jplus.web.filters.Auth.doFilter(Auth.java:128)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
        at jplus.web.filters.UploadFilter.doFilter(UploadFilter.java:68)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
        at jplus.web.filters.PrettyFilter.doFilter(PrettyFilter.java:25)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
        at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:929)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:405)
        at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:964)
        at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:515)
        at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:302)
        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:662)

Any help greatly appreciated.

Regards,

Nicola.

[chris_keating]

This error can occur for the following reasons: the connection was dropped via a DROP STATEMENT, or the database server was shutdown, or the network connection to the database server was interrupted. You can add LogFile=<filespect> to the connection string and -z (with -o <filespec> to capture the output to a file) to enable communications diagnostic logging which can likely help isolate what is happening. If you have questions about the information collected in the logs, please ask or post the files here for comment.

[former_SQLA_member1694894]

It seems to be an HTTP options !? .....

[chris_keating]

Try Log=<file_spec> where filespec is a path and filename .

If you continue to have problems, can you post your connection string (masking confidential info with ***.

[former_SQLA_member1694894]

OK, applied. I will post the debugging results in the next days .... Thanks.