|
Home > Archive > WebSphere Commerce suite > December 2005 > My Prev post for Send Password Notification
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
My Prev post for Send Password Notification
|
|
|
| As i debugged the problem looks the transports are not getting initialized because of this below problem. Hence the sendpassword notitication or any email isnt working. can you please help me with some leads. I am running WCS express 5.6. Application Serv
er 5.0.2 CF 14 and DB2 8.1.5 in Redhat Linux.
The below problem started after the fix for a WC server crash problem due to memory leaks, for which we moved from 5.0.2 CF12 to 5.0.2 CF14.
[12/8/05 3:28:11:242 PST] 52874204 CommerceSrvr E com.ibm.commerce.scheduler.Scheduler getReadyToRunLateJob CMN0417E: The following SQL Exception occurred during processing: "com.ibm.websphere.ce.cm.StaleConnectionException: [IBM][CLI Driver] SQL1224N A
database agent could not be started to service a request, or was terminated as a result of a database system shutdown or a force command. SQLSTATE=55032
".
[12/8/05 3:28:11:529 PST] 52874204 ExceptionUtil E CNTR0019E: Non-application exception occurred while processing method "findByPrimaryKey". Exception data: com.ibm.websphere.csi.CSITransactionRolledbackException: Global tx rolled back
at com.ibm.ejs.csi.TransactionControlImpl. getCurrentTransactionalUOW(TransactionCo
ntrolImpl.java:655)
at com.ibm.ejs.csi.TransactionControlImpl.preInvoke(TransactionControlImpl.java:347)
at com.ibm.ejs.container.EJSContainer.preInvoke_internal(EJSContainer.java:2707)
at com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java:2449)
at com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java:2434)
at com.ibm.commerce.messaging.objects.EJSRemoteCMPTransportHome_e972f78f. findByPrimaryKey(EJSRemoteCMPTransportHo
me_e972f78f.java:56)
at com.ibm.commerce.messaging.objects._TransportHome_Stub.findByPrimaryKey(_TransportHome_Stub.java:387)
at com.ibm.commerce.messaging.objects.TransportAccessBean.instantiateEJB(TransportAccessBean.java:187)
at com.ibm.ivj.ejb.runtime.AbstractEntityAccessBean._instantiate(AbstractEntityAccessBean.java:165)
at com.ibm.ivj.ejb.runtime.AbstractEntityAccessBean. refreshCopyHelper(AbstractEntityAccessBe
an.java:304)
at com.ibm.commerce.messaging.objects.TransportAccessBean.refreshCopyHelper(TransportAccessBean.java:257)
at com.ibm.commerce.messaging.util.ConnectorsInfo.initializeOutbound(ConnectorsInfo.java:1569)
at com.ibm.commerce.messaging.util.ConnectorsInfo.getOutboundConnectors(ConnectorsInfo.java:222)
at com.ibm.commerce.messaging.outboundservice.ConnectorsHolder.initializeConnectors(ConnectorsHolder.java:47)
at com.ibm.commerce.messaging.outboundservice.Messaging._init(Messaging.java:385)
at com.ibm.commerce.messaging.outboundservice.Messaging.<init>(Messaging.java:292)
at com.ibm.commerce.messaging.outboundservice.Messaging.<init>(Messaging.java:272)
at com.ibm.commerce.messaging.ras.ErrorNotificationHandler.<init>(ErrorNotificationHandler.java:36)
at com.ibm.commerce.messaging.ras.ErrorNotificationHandler.<clinit>(ErrorNotificationHandler.java:21)
at java.lang.Class.forName1(Native Method)
at java.lang.Class.forName(Class.java(Compiled Code))
at com.ibm.commerce.ras.ECLoggingProvider.outputMessage(ECLoggingProvider.java:639)
at com.ibm.commerce.ras.ECLoggingProvider.out(ECLoggingProvider.java:517)
at com.ibm.commerce.ras.ECMessageLog.out(ECMessageLog.java:149)
at com.ibm.commerce.exception.ECException.logMessage(ECException.java:285)
at com.ibm.commerce.exception.ECSystemException.<init>(ECSystemException.java:200)
at com.ibm.commerce.scheduler.Scheduler.getReadyToRunLateJob(Scheduler.java:922)
at com.ibm.commerce.scheduler.Scheduler.prepareLateJobs(Scheduler.java:1278)
at com.ibm.commerce.scheduler.Scheduler.serverLoop(Scheduler.java:1636)
at com.ibm.commerce.scheduler.Scheduler.process(Scheduler.java:1491)
at com.ibm.commerce.scheduler.SchedulerSecurityPriviledgedAction.run(SchedulerSecurityPriviledgedAction.java:59)
at com.ibm.commerce.scheduler.Scheduler.run(Scheduler.java:1467)
[12/8/05 3:28:11:555 PST] 52874204 CommerceSrvr E com.ibm.commerce.messaging.util.ConnectorsInfo initializeOutbound() CMN0412E: The following Remote Exception occurred during processing: "javax.transaction.TransactionRolledbackException: CORBA TRANSACTIO
N_ROLLEDBACK 0x0 No; nested exception is:
org.omg.CORBA.TRANSACTION_ROLLEDBACK: javax.transaction.TransactionRolledbackException: ; nested exception is:
com.ibm.websphere.csi.CSITransactionRolledbackException: Global tx rolled back minor code: 0 completed: No".
| |
| Robert Brown 2005-12-11, 5:56 pm |
| > As i debugged the problem looks the transports are not getting initialized because of this below problem. Hence the sendpassword notitication or any email isnt working. can you please help me with some leads. I am running WCS express 5.6. Application Se
rver 5.0.2 CF 14 and DB2 8.1.5 in Redhat Linux.
>
> The below problem started after the fix for a WC server crash problem due to memory leaks, for which we moved from 5.0.2 CF12 to 5.0.2 CF14.
>
> [12/8/05 3:28:11:242 PST] 52874204 CommerceSrvr E com.ibm.commerce.scheduler.Scheduler getReadyToRunLateJob CMN0417E: The following SQL Exception occurred during processing: "com.ibm.websphere.ce.cm.StaleConnectionException: [IBM][CLI Driver] SQL1224N
A database agent could not be started to service a request, or was terminated as a result of a database system shutdown or a force command. SQLSTATE=55032
> ".
This is a serious database connection issue and I would not chase it as
a WC scheduler configuration problem initially. I'll assume the WC
instance can start successfully, making the connection to the database,
by pulling connection information from the instance's xml configuration
file. You're basically saying this occurs after stopping the WC and
database and restarting the applications? Based on what you've
described, only the scheduler component is failing even though the WC
instance is running smoothly. Memory leaks, CFs applied, what else has
changed recently? Have memory leaks been confirmed as a JVM problem and
not from a WC command? Perhaps another scheduler command is part of the
problem disrupting scheduler communication with the database for other
scheduled commands! That sounds more likely...
R
|
|
|
|
|