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 associate
d 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 o
ccurred.  Error code is: XAER_RMFAIL.  Exception is: <null>
[9/8/04 11:37:07:700 MST] 785161bc StaleConnecti A CONM7007I: Mapping the followi
ng SQLException, with ErrorCode -99,999 and SQLState 40003, to a StaleConnectionE
xception: COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] CLI0108E  Communicatio
n link failure. SQLSTATE=40003
        at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(SQL
ExceptionGenerator.java:267)
        at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(SQL
ExceptionGenerator.java(Inlined Compiled Code))
        at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.check_return_code(SQLE
xceptionGenerator.java(Compiled Code))
        at COM.ibm.db2.jdbc.app.DB2Statement.setEscapeProcessing(DB2Statemen
t.java:1605)
        at com.ibm.websphere.rsadapter.DB2DataStoreHelper.doStatementCleanup
(DB2DataStoreHelper.java:287)
        at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.closeWrapper(WS
JdbcPreparedStatement.java(Compiled Code))
        at com.ibm.ws.rsadapter.jdbc.WSJdbcObject.close(WSJdbcObject.java(Co
mpiled Code))
        at com.ibm.ws.rsadapter.jdbc.WSJdbcObject.closeChildWrappers(WSJdbcO
bject.java(Compiled Code))
        at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.dissociate(WSJdbcConne
ction.java:843)
....
...
...
...
[9/8/04 11:37:07:703 MST] 785161bc ConnectionEve A J2CA0056I: The Connection Mana
ger received a fatal connection error from the Resource Adaptor for resource jdbc
/sessionxa.  The exception which was received is com.ibm.websphere.ce.cm.StaleCon
nectionException: [IBM][CLI Driver] CLI0108E  Communication link failure. SQLSTAT
E=40003[9/8/04 11:37:07:706 MST] 785161bc WSJdbcConnect W DSRA8650W: Error c
losing a JDBC child wrapper, com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStateme
nt@4301e185
com.ibm.websphere.ce.cm.StaleConnectionException: [IBM][CLI Driver] CLI0108E  Com
munication link failure. SQLSTATE=40003
        at java.lang.reflect.Constructor.newInstance(Native Method)
        at com.ibm.websphere.rsadapter.GenericDataStoreHelper.mapExceptionHe
lper(GenericDataStoreHelper.java:458)
        at com.ibm.websphere.rsadapter.GenericDataStoreHelper.mapException(G
enericDataStoreHelper.java:499)
        at com.ibm.ws.rsadapter.jdbc.WSJdbcUtil.mapException(WSJdbcUtil.java
:823)
        at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.closeWrapper(WS
JdbcPreparedStatement.java(Compiled Code))
        at com.ibm.ws.rsadapter.jdbc.WSJdbcObject.close(WSJdbcObject.java(Co
mpiled Code))
        at com.ibm.ws.rsadapter.jdbc.WSJdbcObject.closeChildWrappers(WSJdbcO
bject.java(Compiled Code))
        at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.dissociate(WSJdbcConne
ction.java:843)
        at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.dissociateHan
dles(WSRdbManagedConnectionImpl.java:1832)
        at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanup(WSRdb
ManagedConnectionImpl.java:1948)
        at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1156)
        at com.ibm.ejs.j2c.poolmanager.FreePool.cleanupAndDestroyMCWrapper(F
reePool.java:450)
        at com.ibm.ejs.j2c.poolmanager.FreePool.returnToFreePool(FreePool.ja
va:275)
        at com.ibm.ejs.j2c.poolmanager.PoolManager.release(PoolManager.java:
1218)
        at com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.java:165
7)
        at com.ibm.ejs.j2c.XATransactionWrapper.afterCompletionCode(XATransa
ctionWrapper.java:374)
        at com.ibm.ejs.j2c.XATransactionWrapper.afterCompletion(XATransactio
nWrapper.java:315)
        at com.ibm.ejs.jts.jta.TransactionImpl$SyncronizationWrapper.after_c
ompletion(TransactionImpl.java:1284)
        at com.ibm.ejs.jts.jts.CoordinatorImpl$Sync.afterResolution(Coordina
torImpl.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:97
8)
        at com.ibm.ejs.jts.tran.EventAbort.event_Abort(EventAbort.java:915)
        at com.ibm.ejs.jts.tran.EventAbort.event_AbortRequest(EventAbort.jav
a:112)
        at com.ibm.ejs.jts.tran.TrecInterface.abort(TrecInterface.java:71)
        at com.ibm.ejs.jts.tran.TransactionContextCallback.abort(Transaction
ContextCallback.java:74)
        at com.ibm.ejs.jts.jts.ResourceVector.beforePrepare(ResourceVector.j
ava:394)        at com.ibm.ejs.jts.tran.EventCallback.executeCallback(EventC
allback.java:161)        at com.ibm.ejs.jts.tran.EventCallback.executeCallba
ckTree(EventCallback.java:132)
        at com.ibm.ejs.jts.tran.EventCallback.executeCallbackTree(EventCallb
ack.java:123)        at com.ibm.ejs.jts.tran.EventPrepare.ExecuteBeforePrepa
reCallbacks(EventPrepare.java:312)
        at com.ibm.ejs.jts.tran.EventPrepare.event_LocalPrepareWork(EventPre
pare.java:287)
        at com.ibm.ejs.jts.tran.EventPrepare.event_BecomeCoordinator(EventPr
epare.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.posti
nvoke(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(WorkWithEx
ecutionContextImpl.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 fai
lure. SQLSTATE=40003
        at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(SQL
ExceptionGenerator.java:267)
        at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(SQL
ExceptionGenerator.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

[ Post a follow-up to this message ]

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

[ Post a follow-up to this message ]

Ken - Thanks for the response. 

I have found out the rootcause ...The global transaction is timing out (afte
r 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

[ Post a follow-up to this message ]

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.

[ Post a follow-up to this message ]

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/infoc...ontranserv.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
cdjohnson@us.ibm.com

"Paul Ilechko" <plechik@us.ibm.com> wrote in message
news:chse0s$5pca$1@news.boulder.ibm.com...
> nauman wrote: 
>
> 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.
>

[ Post a follow-up to this message ]