JDBC connection to SyBase 125 timing out

, ,
1

Having successfully installed wM6.1 on a Win2003 blade and tested all packages and connections, we made an image and deployed this to another blade.
We then reconfigured the JDBC Pools to connect to a new Oracle 9.2 server which worked fine.
However on this other blade our connection to our SyBase 12.5 server times out.
Below the errors seen in the jdbc.log. Until the timeout error occurs the log is identical between the first and the second blade.
The Alias is set up same way on both servers.
----->
>>>>> (JDBCConnection) loading driver com.sybase.jdbc2.jdbc.SybDriver
registerDriver: driver[className=com.sybase.jdbc2.jdbc.SybDriver,com.sybase.jdbc2.jdbc.SybDriver@73e8287b]
registerDriver: driver[className=com.sybase.jdbc2.jdbc.SybDriver,com.sybase.jdbc2.jdbc.SybDriver@7326687b]
DriverManager.deregisterDriver: com.sybase.jdbc2.jdbc.SybDriver@73e8287b
registerDriver: driver[className=com.sybase.jdbc2.jdbc.SybDriver,com.sybase.jdbc2.jdbc.SybDriver@7326687b]
DriverManager.getConnection(“jdbc:sybase:Tds:10.31.206.30:4101/nfl_db”)
trying driver[className=com.wm.dd.jdbc.oracle.OracleDriver,com.wm.dd.jdbc.oracle.OracleDriver@753ce862]
trying driver[className=com.sybase.jdbc2.jdbc.SybDriver,com.sybase.jdbc2.jdbc.SybDriver@7326687b]
java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Operation timed out: connect

Any suggestions will be much appreciated.

2

Hmmm. Curious.

To isolate the problem, try increasing the timeout in the adapter connection settings on your second blade. Also, what happens if the IS server on the first blade is not running.

You can also write a very simple java command line app that uses the same Sybase jdbc drivers as you are attempting to use from the IS adapter connection. If that app experiences the same timeout issue you will have narrowed things down a bit.

Here’s one such app that you can modify to suit your needs.

TestSybaseJDBCConnection.java
TestSybaseJDBCConnection.java (2.2 k)

		HTH,

Mark