when updating the state in SCHSTATUS, we occasionally receive the following 
error:
TimeStamp:    2004-05-18 05:48:53.378
Thread ID:    <Scheduler replicateAuth#2>
Class:        com.ibm.commerce.scheduler.SchedulerJob
Method:       UpdateState
Severity:     1
Message Text: CMN0409E The following error occurred during processing: java.
rmi.ServerException: RemoteException occurred in server thread; nested excep
tion is:
com.ibm.websphere.cpi.CPIException: COM.ibm.db2.jdbc.DB2Exception: [IBM]
[CLI Driver][DB2/6000] SQL0911N  The current transaction has been ro
lled back because of a deadlock or timeout.  Reason code "2".  SQLSTATE=4000
1
; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2/6000] SQL09
11N  The current transaction has been rolled back because of a deadlock or t
imeout.  Reason code "2".  SQLSTATE=40001
.

Any ideas what is causing this?  It causes the thread to hang and the "user"
 that is running the job ends up hanging our LDAP connection.

Any info is much appreciated.

[ Post a follow-up to this message ]

Hi Jeff,

Which versions/operating system are you on? Are you running a cloned
environment? Reason code "2" is a deadlock. In a deadlock situation both
threads involved in the deadlock will hang until the database detects the
deadlock and rolls one thread back. The other will then complete correctly.
You can vary the deadlock detection interval inside the database
configuration.

To find out why it's deadlocking you could start by putting on a deadlock
monitor (assuming DB2) to find which tables are involved.

Deadlocking associated with the scheduler is not uncommon in cloned
environments - each clone is competing to run the same job. See

http://www-1.ibm.com/support/docvie...uid=swg21051145

I don't quite understand why a scheduled job should cause an LDAP failure?

Cheers,
Glen.

<jeff.alspaugh@nashfinch.com> wrote in message
news:1105056722.1085002918757.JavaMail.wasadmin@swg3ws006...
> when updating the state in SCHSTATUS, we occasionally receive the
following error:
> TimeStamp:    2004-05-18 05:48:53.378
> Thread ID:    <Scheduler replicateAuth#2>
> Class:        com.ibm.commerce.scheduler.SchedulerJob
> Method:       UpdateState
> Severity:     1
> Message Text: CMN0409E The following error occurred during processing:
java.rmi.ServerException: RemoteException occurred in server thread; nested
exception is:
> com.ibm.websphere.cpi.CPIException: COM.ibm.db2.jdbc.DB2Exception:
[IBM][CLI Driver][DB2/6000] SQL0911N  The current transaction ha
s been
rolled back because of a deadlock or timeout.  Reason code "2".
SQLSTATE=40001
> ; nested exception is:
> COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2/6000] SQL0911N  T
he
current transaction has been rolled back because of a deadlock or timeout.
Reason code "2".  SQLSTATE=40001
> .
>
> Any ideas what is causing this?  It causes the thread to hang and the
"user" that is running the job ends up hanging our LDAP connection.
>
> Any info is much appreciated.

[ Post a follow-up to this message ]