OD scheduler - connection errors

John742

We have recently started seeing connection problems to the OD scheduler DB.
od 6.0.2
the OD scheduler properties are as follows:

 schedulerProperties jdbcDriverClass="oracle.jdbc.driver.OracleDriver"
  dbUrl="dbcracle:thin:@SERVERORT:INSTANCE"

This has been setup and working fine for a long time. recently the scheduler UI and odbase log are giving this error

ENG: 2006-09-28 16:49:49 EDT GMT-04:00 ***ERROR - Failed to get schedule jobs. 
SchedulerException: SQL error 3: Io exception: Connection reset by peer: socket write error
API: 2006-09-28 16:49:49 EDT GMT-04:00 ***ERROR - server failed in getting scheduler jobs.
Error - SCHEDULER_FAILED, ***ERROR - Failed to get schedule jobs. 

An OD restart corrects this issue for some time.
I am checking on DB side issues
Also we did used to have a scheduled deployment that ran very frequently(every hour), which was recently suspended.

the oracle driver used was classes12.jar

After updating the driver to - ojdbc14.jar
the following error is thrown at the same frequency as the old error:

ENG: 2006-10-02 08:41:44 EDT GMT-04:00 ***ERROR - Failed to get schedule jobs. 
SchedulerException: SQL error 3: Io exception: Software caused connection abort: socket write error
API: 2006-10-02 08:41:44 EDT GMT-04:00 ***ERROR - server failed in getting scheduler jobs.
Error - SCHEDULER_FAILED, ***ERROR - Failed to get schedule jobs.

Any Ideas?

John742

Ok so I was able to identify the reason for the error. OpenJMS failed to startup and was giving JNDI errors.
The actual Open JMS process that is invoked as part of the Opendeploy start process has a hardcoded classpath to the driver( this is set in eventreportingconfig.xml)
The class path has the actual driver name hardcoded, so renaming it as I did effectively broke eventreporting. I have since updated the classpath with the new driver and all seems to be fine for now. Od scheduler and event reporting are working and no errors are being thrown in the logs. Once the database connections drops I will be able to tell if this driver is able to recover the connection better than the previous.