I used to use Client Access for a Client for about 3 years. When we upgraded to CFMX, the ODBC-JDBC bridge
continuosly failed and was locking up the CFMX instance. We dropped client access and went to JDBC Type IV
driver for AS400, this has been quite stable and reliable.
You can download it from here.
http://www-1.ibm.com/servers/eserver/iseries/toolbox/downloads.htm
Its a free driver and comes with all the instructions to setUp. If you are having problems with the SetUp, check the
archives, this topic has been discussed a few times.
I would suggest you write a simple Java Standalone program that checks the AS400 Connections every 5 minutes
and updates some kind of Flag on a Database or XML File.
HTH
Joe Eugene
- Original Message -
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
To: CF-Talk
Sent: Wednesday, December 17, 2003 8:13 AM
Subject: DB Connection Timeout
We use Client Access to connect to a DB/2 400 database. However when the AS/400 is down for maintenance attempts to connect to that machine eventually lock up the CF server and I need to restart it. I've tried a CFTRY, CATCH but the connection doesn't return an error it just hangs. Is there a way to force the operation to quit if it isn't done in a specified amt of time? I've tried using the CFQUERY timeout attribute, as well as the CF Admin DSN, the Client Access timeout settings to no avail. Whenever the 400 is down (usually overnights, and weekends) our webserver crashes, so I need a way to not make the DB calls if the 400 is down.
Thanks for any ideas,
Daron Smith
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
