Ansync Web Service is Blocking

Question

Hello,
I have build an asynchronous web service and have implemented a polling
interface for my Java client to access it. Here is the call sequence:
1. Client calls "start" method which is buffered and also starts a
conversation.
2. Client calls "isReady" which returns true|false depending on the status
of the service completion
3. Client calls "getInfo" which returns the result of the service
If the "start" method processing takes over 30 seconds the following
exception is genreated when calling "isReady":
####<Sep 15, 2003 9:57:51 AM PDT> <Error> <WLW> <OKCOMPUTER> <ssa_admin>
<ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<anonymous>>
<BEA1-001F36642240> <000000>
<Failure=javax.ejb.TransactionRolledbackLocalException: [EJB:010107]The lock
request from EJB:PersistentContainer with primary
key:192.168.1.101-1556d12.f7a62f4472.-8000 timed-out after waiting 30,000
ms. The transaction or thread requesting the lock was:Name=[EJB
com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.
core.request.Request)],Xid=BEA1-001F36642240(27960095),Status=Active,numRepl
iesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=30,seconds
left=270,activeThread=Thread[ExecuteThread: '13' for queue:
'weblogic.kernel.Default',5,Thread Group for Queue:
'weblogic.kernel.Default'],SCInfo[domain_ssa+ssa_admin]=(state=active),prope
rties=({weblogic.transaction.name=[EJB
com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.
core.request.Request)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorD
escriptor=(CoordinatorURL=ssa_admin+192.168.1.101:7001+domain_ssa+t3+,
XAResources={JMS_FileStore, weblogic.jdbc.wrapper.JTSXAResourceImpl,
JMS_cgJMSStore},NonXAResources={})]).; nested exception is:
weblogic.ejb20.locks.LockTimedOutException: [EJB:010107]The lock request
from EJB:PersistentContainer with primary
key:192.168.1.101-1556d12.f7a62f4472.-8000 timed-out after waiting 30,000
ms. The transaction or thread requesting the lock was:Name=[EJB
com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.
core.request.Request)],Xid=BEA1-001F36642240(27960095),Status=Active,numRepl
iesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=30,seconds
left=270,activeThread=Thread[ExecuteThread: '13' for queue:
'weblogic.kernel.Default',5,Thread Group for Queue:
'weblogic.kernel.Default'],SCInfo[domain_ssa+ssa_admin]=(state=active),prope
rties=({weblogic.transaction.name=[EJB
com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.
core.request.Request)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorD
escriptor=(CoordinatorURL=ssa_admin+192.168.1.101:7001+domain_ssa+t3+,
XAResources={JMS_FileStore, weblogic.jdbc.wrapper.JTSXAResourceImpl,
JMS_cgJMSStore},NonXAResources={})]). [ServiceException]>
There are several things to note in this error message:
1. The the timeout occurred after 30,000 ms
2. The "seconds since begin" is equal to 30
3. The "seconds left" is equal to 270
If seems that if the "seconds since begin" is less than "seconds left" then
the exception should not occurr until the condition is false.
Also, the client call to "isReady" seems to be blocking based on the
exception and some debug/tracing I did. The server log confirms that the
when the client class "isReady" and the "start" method is still executing it
will wait until "start" is completed before letting the "isReady" call
continue.
A couple of questions:
1. Is this how an async Web service is supposed to behave when using
polling?
2. Where are the time out values specified that are displayed in the
stacktrace above?
-Joe

Answer 1

Hi,
Could you please try this>?
In the wlw-config.xml Configuration File please change
<ejb-concurrency-strategy> to Database.
Also please try this
How to set txn timeout in JWS files?
You should also be able to set this via a -D on the command line or through
the jws-config.properties. The property you want to set is
"weblogic.jws.TransactionTimeout". Give it some integer value corresponding
to the number of seconds you want the txn timeout value to be:
-Dweblogic.jws.TransactionTimeout=72000
would timeout transactions after 20 hours
Now, since this value gets cooked into deployment descriptors, you need to
have this property set when you deploy (in debug) or when you build your
production ear.
Vimala
"Joe Chavez" <[email protected]> wrote in message
news:[email protected]...
Hello,
I have build an asynchronous web service and have implemented a polling
interface for my Java client to access it. Here is the call sequence:
1. Client calls "start" method which is buffered and also starts a
conversation.
2. Client calls "isReady" which returns true|false depending on the status
of the service completion
3. Client calls "getInfo" which returns the result of the service
If the "start" method processing takes over 30 seconds the following
exception is genreated when calling "isReady":
####<Sep 15, 2003 9:57:51 AM PDT> <Error> <WLW> <OKCOMPUTER> <ssa_admin>
<ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<anonymous>>
<BEA1-001F36642240> <000000>
<Failure=javax.ejb.TransactionRolledbackLocalException: [EJB:010107]Thelock
request from EJB:PersistentContainer with primary
key:192.168.1.101-1556d12.f7a62f4472.-8000 timed-out after waiting 30,000
ms. The transaction or thread requesting the lock was:Name=[EJB
com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.
>
core.request.Request)],Xid=BEA1-001F36642240(27960095),Status=Active,numRepl
iesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=30,seconds
left=270,activeThread=Thread[ExecuteThread: '13' for queue:
'weblogic.kernel.Default',5,Thread Group for Queue:
'weblogic.kernel.Default',SCInfo[domain_ssa+ssa_admin]=(state=active),prope
rties=({weblogic.transaction.name=[EJB
com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.
>
core.request.Request)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorD
escriptor=(CoordinatorURL=ssa_admin+192.168.1.101:7001+domain_ssa+t3+,
XAResources={JMS_FileStore, weblogic.jdbc.wrapper.JTSXAResourceImpl,
JMS_cgJMSStore},NonXAResources={})]).; nested exception is:
weblogic.ejb20.locks.LockTimedOutException: [EJB:010107]The lock request
from EJB:PersistentContainer with primary
key:192.168.1.101-1556d12.f7a62f4472.-8000 timed-out after waiting 30,000
ms. The transaction or thread requesting the lock was:Name=[EJB
com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.
>
core.request.Request)],Xid=BEA1-001F36642240(27960095),Status=Active,numRepl
iesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=30,seconds
left=270,activeThread=Thread[ExecuteThread: '13' for queue:
'weblogic.kernel.Default',5,Thread Group for Queue:
'weblogic.kernel.Default',SCInfo[domain_ssa+ssa_admin]=(state=active),prope
rties=({weblogic.transaction.name=[EJB
com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.
>
core.request.Request)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorD
escriptor=(CoordinatorURL=ssa_admin+192.168.1.101:7001+domain_ssa+t3+,
XAResources={JMS_FileStore, weblogic.jdbc.wrapper.JTSXAResourceImpl,
JMS_cgJMSStore},NonXAResources={})]). [ServiceException]>
There are several things to note in this error message:
1. The the timeout occurred after 30,000 ms
2. The "seconds since begin" is equal to 30
3. The "seconds left" is equal to 270
If seems that if the "seconds since begin" is less than "seconds left"then
the exception should not occurr until the condition is false.
Also, the client call to "isReady" seems to be blocking based on the
exception and some debug/tracing I did. The server log confirms that the
when the client class "isReady" and the "start" method is still executingit
will wait until "start" is completed before letting the "isReady" call
continue.
A couple of questions:
1. Is this how an async Web service is supposed to behave when using
polling?
2. Where are the time out values specified that are displayed in the
stacktrace above?
-Joe