Transaction Time out in BPEL
Hi All,
About my issue ,
A legacy system written in PL/SQL procedures written to process huge chunk of data ( kind of adapter which processes more than 2000 files each invoke updates some tables , which takes around 6 hrs to complete ). and we are trying to invoke those pl/sql procedures to integrate the system with SOA(11G).
We have developed a BPEL communicating to DB through DBadapter ( invokes the required PL/SQL procedures ).
All BPELs used are asynchronous processes . wanted to know how the DB Adapter works . is it a good practice to make the BPEL wait for the pl/sql procedure to return (Though BPEL process is a Asynchronous one) .
Please advice me on this .
Cheers
Vamsi
Vamsi,
I believe configuring Pick activity will not help in this case. If you are configuring a DB adapter in a BPEL process then between the invoke and DB adapter it is a sync call. So try increasing transaction time out period through admin console and let me know the results.
Another option is, remove all activities and services from main BPEL after invoke activity (of DB adapter) and create another BPEL and create the removed activities. Create a concurrent program to invoke the PLSQL procedure and at the end of the procedure call the end point url of the second bpel and send the out variables to this bpel.
Hope this helps
Thanks
Similar Messages
-
Transaction Time out error in EJB while using Websphere Application Server.
Hi All,
I am using Websphere Application server and getting the transaction time out error. By default the transaction time out is 120 second. I am using session bean for doing a set of transaction. These set are dynamically generated. Is there any way to set the transaction time out for only this session bean to infinite ?
Thanks in advance
VivekHi,
According to WAS 6 , every opened connection has to be commited (or rolledback) explicitly (didnt try autocommit) before closing. Even if all you have done with that connection is a SELECT Query.
This has apparently solved the same problem I was getting. implement it and see whether it helps you. -
Transaction time out for an single ejb
Hi,
I have one ejb which need to run for long time.
Did a quick search on the forum and find out that you can modify data-source.xml and server.xml to increase the time out period.
But this is a "global" setting which will affect all the ejbs in the application.
Is there a setting where only one ejb's transaction time-out can be specified?
Thanks in advance!
YoungWhat is the exact error code? I.e. the ORA-nnnn error code.
It is not possible to diagnose a problem if the actual problem is not known. Responders are guessing at what the problem is and offering solutions.. and these could be very far of the mark. -
Transaction aborted (possibly due to transaction time out) - Question
This one is driving me insane!
Bellow you will find the code, the descriptor stuff and the exception. The code belongs to a CMP EJB using CMT (transactions). This gets called from a session bean. Please help.
Here is the code:
public Object ejbCreate( String id )
throws CreateException {
s_logger.debug( "ejbCreate()" ); // this prits
//setId( id );
return null;
public void ejbPostCreate( String id )
throws CreateException {
s_logger.debug( "ejbPostCreate()" ); // this also prints
here is descriptor stuff:
<container-transaction>
<method>
<ejb-name>AgentBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
here is the !@#$ exception (sorry been tracing this one for hours):
RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: Transaction aborted (possibly due to transaction time out).; nested exception is: javax.transaction.RollbackException: Transaction marked for rollback; nested exception is:
javax.transaction.RollbackException: Transaction marked for rollback
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: Transaction aborted (possibly due to transaction time out).; nested exception is: javax.transaction.RollbackException: Transaction marked for rollback; nested exception is:
javax.transaction.RollbackException: Transaction marked for rollback
java.rmi.RemoteException: Transaction aborted (possibly due to transaction time out).; nested exception is: javax.transaction.RollbackException: Transaction marked for rollback; nested exception is:
javax.transaction.RollbackException: Transaction marked for rollback
javax.transaction.RollbackException: Transaction marked for rollback
<<no stack trace available>>It usually means that you're doing something which creates a loop in your locking. Something like setting a value in each instance from an update method of one of the instances. Your posted code doesn't seem to be the trouble, but I could be missing something.
Success,
S. -
Hi,
I have a stateless session bean invoking methods on an entity bean reference.
When 2 methods are invoked using the home reference, I get the following error
Start server side stack trace:
javax.transaction.TransactionRolledbackException: Transaction timed out after
64 seconds
Name=[EJB com.aol.quack.usabilityTools.recTuningBeans.UsabilityReportBean.createFreqReport(java.lang.Str
e=active),properties=({weblogic.transaction.name=[EJB com.aol.quack.usabilityTools.recTuningBeans.Usabil
at weblogic.transaction.internal.TransactionManagerImpl.receiveRequest(TransactionManagerImpl.ja
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:153)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:253)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:220)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy79.findRecognitions(Unknown Source)
at com.aol.quack.usabilityTools.util.FuncLib.processForEachMode(FuncLib.java:190)
at com.aol.quack.usabilityTools.util.FrequencyReport.generate(FrequencyReport.java:128)
at com.aol.quack.usabilityTools.recTuningBeans.UsabilityReportBean.createFreqReport(UsabilityRep
at com.aol.quack.usabilityTools.recTuningBeans.UsabilityReportBean_earfgg_EOImpl.createFreqRepor
at com.aol.quack.usabilityTools.recTuningBeans.UsabilityReportBean_earfgg_EOImpl_WLSkel.invoke(U
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:257)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
Does anyone have idea whats wrong? Is it the code?
The same code works for small tables though.
Thanks,
Priya
I don't think you can call a stored procedure from a CMP. What i meant was you might try calling a stored
procedure from a BMP or a Stateless bean if it is only required to get records from the table.
Shiva.
Priya wrote:
Hi,
How do I get stored procedures to work for container managed bean?
Priya
Shiva Paranandi <[email protected]> wrote:
If it is failing for large data means you need to have an alternate solution
like getting a stored procedure to
pass the results or doing some caching. Or maybe you might even try splitting
the obtained data so your
transactions might spawn for less than 60 seconds. Worst case increase
the time. Also check out what is the
time it takes to get the same data through a sql plus. Check if there
is a huge amount of time difference and
then you might want to see where this time difference is coming from.
Shiva.
Priya wrote:
Hi,
I am using CMP for the entity beans and have already set the timeoutvalue to
60 secs.
Also, this works for small tables but fails for big ones while calling2 finder/home
methods consecutively.
Priya
Shiva Paranandi <[email protected]> wrote:
Does the transaction only involve getting records from the table?
You
can change the transaction time out
value in your ejb's or in the console of WLS. Hope you are using PreparedStatements
in your SQL code. You
might also want to turn on your JDBC log to check out what might behappening.
Shiva.
Priya wrote:
Hi,
I have a stateless session bean invoking methods on an entity
bean
reference.
When 2 methods are invoked using the home reference, I get the followingerror
Start server side stack trace:
javax.transaction.TransactionRolledbackException: Transaction timedout after
64 seconds
Name=[EJB com.aol.quack.usabilityTools.recTuningBeans.UsabilityReportBean.createFreqReport(java.lang.Str
e=active),properties=({weblogic.transaction.name=[EJB com.aol.quack.usabilityTools.recTuningBeans.Usabil
at weblogic.transaction.internal.TransactionManagerImpl.receiveRequest(TransactionManagerImpl.ja
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:153)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:253)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:220)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy79.findRecognitions(Unknown Source)
at com.aol.quack.usabilityTools.util.FuncLib.processForEachMode(FuncLib.java:190)
at com.aol.quack.usabilityTools.util.FrequencyReport.generate(FrequencyReport.java:128)
at com.aol.quack.usabilityTools.recTuningBeans.UsabilityReportBean.createFreqReport(UsabilityRep
at com.aol.quack.usabilityTools.recTuningBeans.UsabilityReportBean_earfgg_EOImpl.createFreqRepor
at com.aol.quack.usabilityTools.recTuningBeans.UsabilityReportBean_earfgg_EOImpl_WLSkel.invoke(U
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:257)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
Does anyone have idea whats wrong? Is it the code?
The same code works for small tables though.
Thanks,
Priya
> > -
Transaction time out after 300 seconds..
Hi guys,
I have very intersting problem. I get transaction time out exception after 300 seconds. I use WLP8.1 SP3. I get this when I try to add a new portlet using admin tool
to home page (which is customized by many users)
Here is the error msg:
<weblogic> <> <BEA-415037> <PortalAdminInstanceManager.addPlaceableToPageInstance() -- java.rmi.RemoteException: EJB Exception: ; nested exception is:
javax.ejb.EJBException: SQL Error while trying to getLayoutDefinition on 2004: SQL [select LAY.MARKUP_DEFINITION_ID, LAY.INTERSECTION_ID, PL.PLACEHOLDER_DEFINITION_ID, PL.MARKUP_DEFINITION_ID, PL.LAYOUT_LOCATION, PL.INTERSECTION_ID, LAY.ICON_URI, LAY.HTML_LAYOUT_URI, LAY.WEBAPP_NAME, LAY.LAYOUT_FILE, LAY.IS_LAYOUT_FILE_DELETED from PF_LAYOUT_DEFINITION LAY, PF_PLACEHOLDER_DEFINITION PL where LAY.LAYOUT_DEFINITION_ID = ? and PL.LAYOUT_DEFINITION_ID = LAY.LAYOUT_DEFINITION_ID] database error code [0] SQL state [null] 040.; nested exception is: java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds
Name=[EJBHi guys,
I have very intersting problem. I get transaction time out exception after 300 seconds. I use WLP8.1 SP3. I get this when I try to add a new portlet using admin tool
to home page (which is customized by many users)
Here is the error msg:
<weblogic> <> <BEA-415037> <PortalAdminInstanceManager.addPlaceableToPageInstance() -- java.rmi.RemoteException: EJB Exception: ; nested exception is:
javax.ejb.EJBException: SQL Error while trying to getLayoutDefinition on 2004: SQL [select LAY.MARKUP_DEFINITION_ID, LAY.INTERSECTION_ID, PL.PLACEHOLDER_DEFINITION_ID, PL.MARKUP_DEFINITION_ID, PL.LAYOUT_LOCATION, PL.INTERSECTION_ID, LAY.ICON_URI, LAY.HTML_LAYOUT_URI, LAY.WEBAPP_NAME, LAY.LAYOUT_FILE, LAY.IS_LAYOUT_FILE_DELETED from PF_LAYOUT_DEFINITION LAY, PF_PLACEHOLDER_DEFINITION PL where LAY.LAYOUT_DEFINITION_ID = ? and PL.LAYOUT_DEFINITION_ID = LAY.LAYOUT_DEFINITION_ID] database error code [0] SQL state [null] 040.; nested exception is: java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds
Name=[EJB -
Transaction time out for a simple query
I have a table with 39 million records in the table. When I try to fetch data from teh table with one single where clause. it is raising Transaction timed Out.
What is the best way to fetch full data with out Time Out.
Can we use the first_rows hint to fetch data batch by batch ?
Thanks,
CDWhat is the exact error code? I.e. the ORA-nnnn error code.
It is not possible to diagnose a problem if the actual problem is not known. Responders are guessing at what the problem is and offering solutions.. and these could be very far of the mark. -
WebLogic Server 6.1 Transaction Time out Transaction
Hi all,
I got the following time out exception when executing a session bean. However, the exception does not happen every time when being executed.
Original Exception Stack Trace:
javax.transaction.TransactionRolledbackException: EJB Exception: : javax.transaction.TransactionRolledbackException: EJB Exception: : weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1139)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:500)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1629)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:463)
at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1595)
at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1526)
at weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(ServerTransactionImpl.java:450)
at weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:158)
at weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:218)
at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:155)
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:63)
at com.finessealliance.clarity.cts.bfs.TxLogServicesBean_xlsia_EOImpl.execute(TxLogServicesBean_xlsia_EOImpl.java:25)
at com.finessealliance.clarity.cts.tpf.BOEvent.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRule.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl.execute(TransactionRuleBean_fptf06_EOImpl.java:37)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:178)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:268)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:235)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy80.execute(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.executeTransactionRule(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.processMessage(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.run(Unknown Source)
; nested exception is:
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1139)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:500)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1629)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:463)
at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1595)
at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1526)
at weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(ServerTransactionImpl.java:450)
at weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:158)
at weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:218)
at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:155)
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:63)
at com.finessealliance.clarity.cts.bfs.TxLogServicesBean_xlsia_EOImpl.execute(TxLogServicesBean_xlsia_EOImpl.java:25)
at com.finessealliance.clarity.cts.tpf.BOEvent.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRule.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl.execute(TransactionRuleBean_fptf06_EOImpl.java:37)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:178)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:268)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:235)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy80.execute(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.executeTransactionRule(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.processMessage(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.run(Unknown Source)
; nested exception is:
javax.transaction.TransactionRolledbackException: EJB Exception: : weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1139)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:500)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1629)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:463)
at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1595)
at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1526)
at weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(ServerTransactionImpl.java:450)
at weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:158)
at weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:218)
at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:155)
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:63)
at com.finessealliance.clarity.cts.bfs.TxLogServicesBean_xlsia_EOImpl.execute(TxLogServicesBean_xlsia_EOImpl.java:25)
at com.finessealliance.clarity.cts.tpf.BOEvent.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRule.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl.execute(TransactionRuleBean_fptf06_EOImpl.java:37)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:178)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:268)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:235)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy80.execute(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.executeTransactionRule(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.processMessage(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.run(Unknown Source)
; nested exception is:
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
javax.transaction.TransactionRolledbackException: EJB Exception: : weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1139)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:500)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1629)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:463)
at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1595)
at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1526)
at weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(ServerTransactionImpl.java:450)
at weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:158)
at weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:218)
at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:155)
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:63)
at com.finessealliance.clarity.cts.bfs.TxLogServicesBean_xlsia_EOImpl.execute(TxLogServicesBean_xlsia_EOImpl.java:25)
at com.finessealliance.clarity.cts.tpf.BOEvent.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRule.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl.execute(TransactionRuleBean_fptf06_EOImpl.java:37)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:178)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:268)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:235)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy80.execute(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.executeTransactionRule(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.processMessage(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.run(Unknown Source)
; nested exception is:
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1139)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:500)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1629)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:463)
at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1595)
at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1526)
at weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(ServerTransactionImpl.java:450)
at weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:158)
at weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:218)
at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:155)
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:63)
at com.finessealliance.clarity.cts.bfs.TxLogServicesBean_xlsia_EOImpl.execute(TxLogServicesBean_xlsia_EOImpl.java:25)
at com.finessealliance.clarity.cts.tpf.BOEvent.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRule.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl.execute(TransactionRuleBean_fptf06_EOImpl.java:37)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:178)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:268)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:235)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy80.execute(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.executeTransactionRule(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.processMessage(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.run(Unknown Source)
at com.finessealliance.clarity.cts.tpf.BOEvent.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRule.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl.execute(TransactionRuleBean_fptf06_EOImpl.java:37)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:178)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:268)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:235)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy80.execute(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.executeTransactionRule(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.processMessage(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.run(Unknown Source)
Thanks,
KaoruNo, I haven't set the attribute in the weblogic-ejb-jar.xml.
The transaction type of the stateless session bean is container. So, I suppose it uses the JTA time-out value which is now set to 30 secs.
Thanks,
Kaoru -
Hi,
I have a MDB with no transaction attribute specified in ejb-jar.xml. This MDB does not have any business logic in it. It in turn calls a session bean with transaction attribute Required+.
We are using Weblogic app server and the JTA is set to 300 sec and we are using Container Managed Transactions.
I am getting a Transaction Timed Out Exception in MDB. But in fact, I am not doing anything in my MDB. Everything is done by the session bean itself and this exception is not thrown by the session bean.
Did anybody face the similar problem? Any pointers?
Thanks & Regards,
Yong-Lohwhich JavaEE version is being used? If it is one with EJB 3.0 support, the MDB will most likely get a container managed transaction by default if you do not explicitly state that it shouldn't have one.
-
Time Out Error while waiting for response from DB Procedure
Hi Gurus,
We are encountering a problem in our production environment. The system is implemented using AIA foundation pack 2.5 on SOA suite 10.1.3.4.
We have a BPEL process A which calls an ESB Service which inturn calls BPEL Process B. In process B, we have a DB procedure call which waits for a response from
a DB procedure. The procedure doesn't reply on time and Process B remains in waiting state to get the response from DB Procedure wherein Process A errors out by showing as "Timed Out Error".
This issue is intermittent and we have already increased transaction-time outs in transaction-manager.xml to 7200 and ejb-orion-jar.xml to 3600.
When we encountered this problem, we found out that there are too many connections open and when we bounced the server, everything was restored to nornal but as it is a production env. we can't do it over and over again.
We have 2 nodes each having max connections as 100 and min. as 0.
Is there a limit to max no. of connections or can we do something in DB side to ensure that it doesn't happen again ?
Please suggest.
Thanks,
Vikas ManchandaHi Anuj,
I don't think it is a problem with connection reaching to max numbers because this issue is coming on very intermittent basis.we don't have any other processes using
the same connection pool and this issue is coming even when there is no load on the server. This is recent trace from the production environment. Also i don't have any thing called "abandoned-connection-pool" in my data-sources.xml.
<2011-07-07 13:09:16,101> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "delivery": Waiting for response has timed out. The conversation id is null. Please check the process instance for detail.
com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is null. Please check the process instance for detail.
at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:109)
at sun.reflect.GeneratedMethodAccessor113.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
at com.evermind.server.ThreadState.runAs(ThreadState.java:693)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
at DeliveryBean_RemoteProxy_4bin6i8.request(Unknown Source)
at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processNormalOperation(SOAPRequestProvider.java:451)
at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processBPELMessage(SOAPRequestProvider.java:274)
at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processMessage(SOAPRequestProvider.java:120)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:956)
at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:466)
at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:194)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:400)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:414)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
Caused by: com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is null. Please check the process instance for detail.
at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:576)
at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:465)
at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:134)
at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java)
Please suggest.
Thanks,
Vikas Manchanda -
How to extend transaction time on EJBSessionBean method?
Hi,
I am importing some data from XML files, and for that I have several methods in a SessionBean. The import may take several minutes, so with larger sets of data I get "Transaction time out" error. I know I can set transactions to bean-managed (haven't tried it yet, though), but is there a way to set a single method's transaction (in a container-managed-transaction bean) to take all the time it needs?
Thanks,
PedjaOk now it is even worse ir seems to have stopped ringing totally my phone is updated using the latest version of IOS and the ringer is on full I am missing all of my calls!!!! Is there anyone that can help??
-
Hi everyone,
I have a problem.
When I load my selected objects for example 100 products into my planning view then everything comes but when create a selection for only 10 products and I load this then the transaction times out.
Can anyone maybe explain to me why this is happening.
Thanks
RobertHi Robert,
1) check is there any data mismatches between data between planning area
/infocube/planning book etc for those products
2) Check whether those products are locked by any user/transaction/programme
3) Check for whether all authorisation objects for those products/selections are
maintained
4) Check whether number of users are more accessing the same product
5) Check any background processing/job is happening accessing data of those
products
Regards
R. Senthil Mareeswaran. -
WebLogic 10.3.6 Times Out When Starting Web App
When starting our web app on WebLogic 10.3.6 using startWebLogic.sh on OEL (8 cores, 64 GB box), after about 5 to 6 minutes we receive a timeout error from WebLogic saying that it timed out trying to start the web app. The web app has some pre-computed indices to load which will take an estimated 10 to 15 minutes to load. Is there are way to control this timeout?
The time-out you are getting is that related to a transaction?
You can set the transaction time-out in the WebLogic console go to the JTA page for the domain, and change the value in the Timeout Seconds field.
When you are using EJBs, you can also set the time-out on a EJB basis, instead of configuring the time-out for the whole domain.
For example, in weblogic-ejb-jar.xml, you can configure the time-out by using:
<weblogic-ejb-jar ...>
<weblogic-enterprise-bean>
<ejb-name>YOUR_EJB_NAME</ejb-name>
<enable-call-by-reference>True</enable-call-by-reference>
<stateless-session-descriptor>
<pool>
<initial-beans-in-free-pool>25</initial-beans-in-free-pool>
<max-beans-in-free-pool>50</max-beans-in-free-pool>
</pool>
</stateless-session-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>600</trans-timeout-seconds>
</transaction-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>The transactions this EJB spawns can last for 10 minutes. -
Hi,
I have to handle DB time out in bpel when database is not responding within 4 seconds. How can i perform this db time out?
Please suggest any useful information and kindly explain in details.
Thanks in Advance
Edited by: 997123 on 09-May-2013 06:47Hello Friends,
While invoking DBAdapter, How can i handle this exception. And more ever how can i delay the DB response. I am unable to do this. Can you please expain it in details.
Please suggest me what to do? By which fault handler i can catch this DB time out exception in bpel while invoking DB.
Thanks in Advance,
Edited by: 997123 on 03-Jun-2013 22:22 -
Time out Through MAXTRANTIME in tuxedo 8.1
Request all to share inputs on MAXTRANTIME parameter introduced in Tuxedo 8.1. I am using Tuxedo 8.1 and tried to use MAXTRANTIME but effect/behavior is not clear to me from Tuxedo 8.1 documentation.
We use global transaction ( time out used in tpbegin is 0 - i.e. no time outs) and MAXTRANTIME is not taking in to effect and Transaction are not getting time out. I can not verify that as i am not clear of effect/behavior.
Thanks,
AjeetAjeet,
There are currently no known issues with the MAXTRANTIME feature.
Verify that you have executed tmloadcf after updating the UBBCONFIG file and
run tmunloadcf to make sure that the TUXCONFIG file updated is the one being
used by your application.
The tmadmin subcommand "verbose" followed by "printtrans" can be used to
show the time remaining until timeout for all currently active transactions.
Remember that transaction timeout can occur up to SCANUNIT seconds after the
specified time due to the timing of the BBL scan.
Timeout will be detected when the next ATMI call is made on behalf of the
transaction, but timeout does not send a signal or other notification to
processes involved in the transaction. A server which is executing
long-running database operations or other long-running application code will
continue to operate on a transaction until an ATMI call is made which
detects the transaction timeout.
If none of the above suggestions solves the problem, then you'll need to
open a case with customer support.
Ed
<AJEET TEWARI> wrote in message news:[email protected]..
Request all to share inputs on MAXTRANTIME parameter introduced in Tuxedo
8.1. I am using Tuxedo 8.1 and tried to use MAXTRANTIME but effect/behavior
is not clear to me from Tuxedo 8.1 documentation.
We use global transaction ( time out used in tpbegin is 0 - i.e. no time
outs) and MAXTRANTIME is not taking in to effect and Transaction are not
getting time out. I can not verify that as i am not clear of
effect/behavior.
Thanks,
Ajeet
Maybe you are looking for
-
Workflow Status column for new content type
Hi, Initially I had a document library and several workflows associated with it. After that I created a new content type inheriting Folder content type. My existing workflows could be started and work fine with any item of this new content type excep
-
Illustrator and other CS4 Apps crashing in snow leopard
Hello, Just upgraded from 10.5.8 to 10.6 and am having some very serious CS4 issues. I first noticed in flash when it constantly kept crashing on save. Now it seems that same issue is also on Illustrator durring open or save or export. I went over to
-
Hi all, We encounter a Essbase perfromance issue that we don't know the root cause. We have configured a server to run Essbase with 8 core CPU and 16GB RAM. We found that the Essbase calculation can use up to 80% CPU and about 8GB RAM only. I also ch
-
How to Store word doc in java using oracle
hi my name is jagapathi raju i am working in Niit LTD can any one tell me how to store A word doc in oracle using java
-
Hi all, I have a table which has no primary key then I made the complex primary key by 2 fields which are foriegn keys(Primary key in other tables or entity beans) , the problem is that whenever I write a finder method ,I face with an error telling t