Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

WAS 5.0.2 Scheduler Service Help Needed

6 views
Skip to first unread message

nauman

unread,
Sep 8, 2004, 4:05:02 PM9/8/04
to

Hi,
We are trying to configure the Scheduler Service in Websphere 5.0.2
but we are getting the following exception:

[9/8/04 11:37:07:695 MST] 785161bc TraceNLS u No message text
associated with key in bundle IBMDataStoreAdapterNLS
[9/8/04 11:37:07:694 MST] 785161bc WSRdbXaResour I
[9/8/04 11:37:07:696 MST] 785161bc WSRdbXaResour W DSRA0302E:
XAException occurred. Error code is: XAER_RMFAIL. Exception is:
<null>
[9/8/04 11:37:07:700 MST] 785161bc StaleConnecti A CONM7007I: Mapping
the following SQLException, with ErrorCode -99,999 and SQLState 40003,
to a StaleConnectionException: COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI
Driver] CLI0108E Communication link failure. SQLSTATE=40003
at
COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(SQLExceptionGenerator.java:267)
at
COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(SQLExceptionGenerator.java(Inlined
Compiled Code))
at
COM.ibm.db2.jdbc.app.SQLExceptionGenerator.check_return_code(SQLExceptionGenerator.java(Compiled
Code))
at
COM.ibm.db2.jdbc.app.DB2Statement.setEscapeProcessing(DB2Statement.java:1605)
at
com.ibm.websphere.rsadapter.DB2DataStoreHelper.doStatementCleanup(DB2DataStoreHelper.java:287)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.closeWrapper(WSJdbcPreparedStatement.java(Compiled
Code))
at
com.ibm.ws.rsadapter.jdbc.WSJdbcObject.close(WSJdbcObject.java(Compiled
Code))
at
com.ibm.ws.rsadapter.jdbc.WSJdbcObject.closeChildWrappers(WSJdbcObject.java(Compiled
Code))
at
com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.dissociate(WSJdbcConnection.java:843)
....
...
...
...
[9/8/04 11:37:07:703 MST] 785161bc ConnectionEve A J2CA0056I: The
Connection Manager received a fatal connection error from the Resource
Adaptor for resource jdbc/sessionxa. The exception which was received
is com.ibm.websphere.ce.cm.StaleConnectionException: [IBM][CLI Driver]
CLI0108E Communication link failure. SQLSTATE=40003[9/8/04
11:37:07:706 MST] 785161bc WSJdbcConnect W DSRA8650W: Error closing a
JDBC child wrapper,
com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement@4301e185
com.ibm.websphere.ce.cm.StaleConnectionException: [IBM][CLI Driver]
CLI0108E Communication link failure. SQLSTATE=40003
at java.lang.reflect.Constructor.newInstance(Native Method)
at
com.ibm.websphere.rsadapter.GenericDataStoreHelper.mapExceptionHelper(GenericDataStoreHelper.java:458)
at
com.ibm.websphere.rsadapter.GenericDataStoreHelper.mapException(GenericDataStoreHelper.java:499)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcUtil.mapException(WSJdbcUtil.java:823)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.closeWrapper(WSJdbcPreparedStatement.java(Compiled
Code))
at
com.ibm.ws.rsadapter.jdbc.WSJdbcObject.close(WSJdbcObject.java(Compiled
Code))
at
com.ibm.ws.rsadapter.jdbc.WSJdbcObject.closeChildWrappers(WSJdbcObject.java(Compiled
Code))
at
com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.dissociate(WSJdbcConnection.java:843)
at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.dissociateHandles(WSRdbManagedConnectionImpl.java:1832)
at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanup(WSRdbManagedConnectionImpl.java:1948)
at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1156)
at
com.ibm.ejs.j2c.poolmanager.FreePool.cleanupAndDestroyMCWrapper(FreePool.java:450)
at
com.ibm.ejs.j2c.poolmanager.FreePool.returnToFreePool(FreePool.java:275)
at
com.ibm.ejs.j2c.poolmanager.PoolManager.release(PoolManager.java:1218)
at
com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.java:1657)
at
com.ibm.ejs.j2c.XATransactionWrapper.afterCompletionCode(XATransactionWrapper.java:374)
at
com.ibm.ejs.j2c.XATransactionWrapper.afterCompletion(XATransactionWrapper.java:315)
at
com.ibm.ejs.jts.jta.TransactionImpl$SyncronizationWrapper.after_completion(TransactionImpl.java:1284)
at
com.ibm.ejs.jts.jts.CoordinatorImpl$Sync.afterResolution(CoordinatorImpl.java:1260)
at
com.ibm.ejs.jts.tran.EventCallback.executeCallback(EventCallback.java:178)
at
com.ibm.ejs.jts.tran.EventCallback.executeCallback(EventCallback.java:137)
at
com.ibm.ejs.jts.tran.EventAbort.CompleteUndo(EventAbort.java:682)
at
com.ibm.ejs.jts.tran.EventAbort.AttemptUndo(EventAbort.java:629)
at
com.ibm.ejs.jts.tran.EventAbort.PerformUndo(EventAbort.java:567)
at
com.ibm.ejs.jts.tran.EventAbort.event_Kill(EventAbort.java:510)
at
com.ibm.ejs.jts.tran.EventAbort.AbortSomething(EventAbort.java:978)
at
com.ibm.ejs.jts.tran.EventAbort.event_Abort(EventAbort.java:915)
at
com.ibm.ejs.jts.tran.EventAbort.event_AbortRequest(EventAbort.java:112)
at
com.ibm.ejs.jts.tran.TrecInterface.abort(TrecInterface.java:71)
at
com.ibm.ejs.jts.tran.TransactionContextCallback.abort(TransactionContextCallback.java:74)
at
com.ibm.ejs.jts.jts.ResourceVector.beforePrepare(ResourceVector.java:394)
at
com.ibm.ejs.jts.tran.EventCallback.executeCallback(EventCallback.java:161)
at
com.ibm.ejs.jts.tran.EventCallback.executeCallbackTree(EventCallback.java:132)
at
com.ibm.ejs.jts.tran.EventCallback.executeCallbackTree(EventCallback.java:123)
at
com.ibm.ejs.jts.tran.EventPrepare.ExecuteBeforePrepareCallbacks(EventPrepare.java:312)
at
com.ibm.ejs.jts.tran.EventPrepare.event_LocalPrepareWork(EventPrepare.java:287)
at
com.ibm.ejs.jts.tran.EventPrepare.event_BecomeCoordinator(EventPrepare.java:970)
at
com.ibm.ejs.jts.tran.EventControl.event_EndTopLevel(EventControl.java:295)
at
com.ibm.ejs.jts.tran.TrecInterface.end(TrecInterface.java:89)
at
com.ibm.ejs.jts.jts.TerminatorImpl.commit(TerminatorImpl.java:104)
at
com.ibm.ejs.jts.jts.CurrentImpl.commit(CurrentImpl.java:249)
at com.ibm.ejs.jts.jts.CurrentSet.commit(CurrentSet.java:316)
at com.ibm.ejs.jts.jta.JTSXA.commit(JTSXA.java:227)
at
com.ibm.ws.extensionhelper.tran.impl.TransactionControlImpl.postinvoke(TransactionControlImpl.java:274)
at
com.ibm.ws.scheduler.SchedulerDaemonImpl.poll(SchedulerDaemonImpl.java:536)
at
com.ibm.ws.scheduler.SchedulerDaemonImpl.run(SchedulerDaemonImpl.java:342)
at
com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java:174)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:378)
at
com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:106)
at
com.ibm.ws.asynchbeans.J2EEContext$DoAsProxy.run(J2EEContext.java:227)
at java.security.AccessController.doPrivileged(Native Method)
at
com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:472)
at
com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContextImpl.java:113)
at
com.ibm.ws.asynchbeans.WorkItemImpl.run(WorkItemImpl.java:176)
at java.lang.Thread.run(Thread.java:513)
---- Begin backtrace for Nested Throwables
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] CLI0108E
Communication link failure. SQLSTATE=40003
at
COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(SQLExceptionGenerator.java:267)
at
COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(SQLExceptionGenerator.java(Inlined
Compiled Code))
...

Version Info:
[AppServer: 5.0.2 on Linux, Database DB2 08.01.0003 FP3, JDBC Driver
version 07.02.0009]

Any help in this regard would be highly appreciated.

Thanks
Nauman

--
nauman
------------------------------------------------------------------------
Posted via http://www.webservertalk.com
------------------------------------------------------------------------
View this thread: http://www.webservertalk.com/message383733.html

Ken Hygh

unread,
Sep 9, 2004, 6:24:42 AM9/9/04
to
nauman wrote:

>Hi,
> We are trying to configure the Scheduler Service in Websphere 5.0.2
>but we are getting the following exception:
>
>[9/8/04 11:37:07:695 MST] 785161bc TraceNLS u No message text
>associated with key in bundle IBMDataStoreAdapterNLS
>[9/8/04 11:37:07:694 MST] 785161bc WSRdbXaResour I
>[9/8/04 11:37:07:696 MST] 785161bc WSRdbXaResour W DSRA0302E:
>XAException occurred. Error code is: XAER_RMFAIL. Exception is:
><null>
>[9/8/04 11:37:07:700 MST] 785161bc StaleConnecti A CONM7007I: Mapping
>the following SQLException, with ErrorCode -99,999 and SQLState 40003,
>to a StaleConnectionException: COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI
>Driver] CLI0108E Communication link failure. SQLSTATE=40003
>
>
>

[snip]

>Version Info:
>[AppServer: 5.0.2 on Linux, Database DB2 08.01.0003 FP3, JDBC Driver
>version 07.02.0009]
>
>Any help in this regard would be highly appreciated.
>
>Thanks
>Nauman
>
>
>
>--
>nauman
>------------------------------------------------------------------------
>Posted via http://www.webservertalk.com
>------------------------------------------------------------------------
>View this thread: http://www.webservertalk.com/message383733.html
>
>
>

Looks like DB2 went down for a backup, a firewall rule fired, something
that would cause a communications failure.

Ken

nauman

unread,
Sep 9, 2004, 6:45:32 PM9/9/04
to

Ken - Thanks for the response.

I have found out the rootcause ...The global transaction is timing out
(after 40 s) while the application processing is in progress ( it takes
almost 5 min and 12 sec) which is causing the communication link
failure. But I dont know how I can increase the time for the global
transaction.
Kindly advise if anybody have any idea of how to do this.

Thanks
nauman

Paul Ilechko

unread,
Sep 10, 2004, 10:34:05 AM9/10/04
to
nauman wrote:
> Ken - Thanks for the response.
>
> I have found out the rootcause ...The global transaction is timing out
> (after 40 s) while the application processing is in progress ( it takes
> almost 5 min and 12 sec) which is causing the communication link
> failure. But I dont know how I can increase the time for the global
> transaction.
> Kindly advise if anybody have any idea of how to do this.

You really don't want a global transaction to be active for over 5
minutes ... you need to find out why it's taking so long, and if you
can't reduce the time, think about an alternative design. Maybe doing
something with asynchronous message queues.

Chris D Johnson

unread,
Jan 5, 2005, 5:02:55 PM1/5/05
to
Nauman:

The Scheduler was designed to run lots of quick-running requests. If you
really need to keep transactions open longer than the default transaction
timeout, you'll need to increase the transaction timeout in the application
server and on your resources:
http://publib.boulder.ibm.com/infocenter/ws51help/topic/com.ibm.websphere.wbifz.doc/info/wbifz/ae/udat_contranserv.html

This is becoming a common scenario for customers who want to run large batch
operations with the scheduler. The scheduler will always keep a transaction
open for the duration of the TaskHandler EJB call. If you want to run your
work asynchronously, you can use asynchronous beans to spawn a daemon
thread. The scheduler will not know that the task is running asynchronously
and will mark it complete, which is OK for some customers. You would need
to keep track of the state of the job independently.
--
Chris D. Johnson
WebSphere Development
Rochester, MN
cdjo...@us.ibm.com

"Paul Ilechko" <ple...@us.ibm.com> wrote in message
news:chse0s$5pca$1...@news.boulder.ibm.com...

0 new messages