Wednesday, April 30, 2008

Process Log from MscProcessing at Wed Apr 30 09:30:00 EDT 2008

MscProcessing starting at Wed Apr 30 09:30:00 EDT 2008

JZ00L: Login failed. Examine the SQLWarnings chained to this exception for the reason(s).
com.sybase.jdbc3.jdbc.ErrorMessage.raiseError(Unknown Source)
com.sybase.jdbc3.tds.Tds.for(Unknown Source)
com.sybase.jdbc3.tds.Tds.a(Unknown Source)
com.sybase.jdbc3.tds.Tds.login(Unknown Source)
com.sybase.jdbc3.jdbc.SybConnection.a(Unknown Source)
com.sybase.jdbc3.jdbc.SybConnection.a(Unknown Source)
com.sybase.jdbc3.jdbc.SybConnection.(Unknown Source)
com.sybase.jdbc3.jdbc.SybConnection.(Unknown Source)
com.sybase.jdbc3.jdbc.SybDriver.connect(Unknown Source)
java.sql.DriverManager.getConnection(DriverManager.java:525)
java.sql.DriverManager.getConnection(DriverManager.java:140)
opuslib.util.adaptors.StdbDriverManager.getConnection(StdbDriverManager.java:298)
opuslib.util.adaptors.StdbDriverManager.getConnection(StdbDriverManager.java:195)
opuslib.database.triggers.MscDeliveryTrigger.(MscDeliveryTrigger.java:68)
opuslib.quartz.MscProcessingJob.execute(MscProcessingJob.java:42)
org.quartz.core.JobRunShell.run(JobRunShell.java:202)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
MscProcessing has terminated abnormally at Wed Apr 30 09:30:00 EDT 2008

1 comment:

  1. Apparently the database was not available for this triggering.

    No explanation yet.

    ReplyDelete