Transaction management in time out

Hi,
I have one question regarding the transaction handling if the program time out.
If I call one function module and there is several SQL statements in it, each SQL statement takes long time, after some of them executed, the program is time out, will the executed SQL statement will be commited or rollback? I think it's should be rollback, isn't it?
Best Regards,
Robin

you do not normally have time-out's with an updare-process. you would get exclusive lockwaits and several other problems, but not a time-out ...
anyway if you get one, your work should be rolled back. of course this depends a bit on how it's developed. there are notes where such updates are divided on several logical processes and caused inconsistencies -> see [1053723|https://websmp130.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1053723&nlang=DE&smpsrv=https%3a%2f%2fwebsmp110%2esap-ag%2ede]. so you would have to be more specific about your problem.

Similar Messages

  • Desktop Manager Download Times Out

    I have tried to download the desktoop manager onto my computer for the past 2 days.  Everytime I try it gets to 99% and then gives me an error it has timed out.  Can anyone help, I don't have an older version installed.

    Hi jacmax69 and welcome to the BlackBerry Support Community Forums!
    Where are you downloading the software from? Try going to http://www.blackberry.com/go/softwaredownloads to download it.  Also, when downloading, make sure to click Save and not Run.  This will save the file in a specified location instead of running it from your temporary folder.
    Let me know if this helps!
    -CptS
    Come follow your BlackBerry Technical Team on twitter! @BlackBerryHelp
    Be sure to click Kudos! for those who have helped you.Click Solution? for posts that have solved your issue(s)!

  • Receiving Transaction Manager Errors out

    I am getting this meesage whle doing Inter-Org transfer that Receiving Transaction Manager as errored out. There is no error code displayed or similar.
    Any thoughts where I can find the log/details of this error?
    Thx

    Please see the solution in (PODAMGR And RCVOLTM Inactive And Cannot Be Started (Doc ID 726158.1)).
    Are there any errors in the database log file?
    If the above didn't help, please run cmclean.sql and ccm.sql scripts.
    Concurrent Processing - CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables (Doc ID 134007.1)
    Concurrent Processing - CCM.sql Diagnostic Script to Diagnose Common Concurrent Manager Issues (Doc ID 171855.1)
    Thanks,
    Hussein

  • Time Out by select on DD04L inner join DD04T

    Hello,
    I just installed ERP 2005. After the import of a language package (SMLT, IT, FR, ES) I get some problem.
    If I logon with EN or IT (and I think with any language other than DE) many transaction get a Time Out error in the function module DDIF_FIELDINFO_GET by the following selection:
    *             get texts of primary language (inner join here !)
                  SELECT DD04L~ROLLNAME DD04L~DOMNAME DD04L~HEADLEN
                         DD04L~SCRLEN1  DD04L~SCRLEN2 DD04L~SCRLEN3
                         DD04T~DDLANGUAGE DD04T~DDTEXT    DD04T~REPTEXT
                         DD04T~SCRTEXT_S  DD04T~SCRTEXT_M DD04T~SCRTEXT_L
                         INTO TABLE Rolltexts
                         FROM DD04L inner JOIN DD04T
                         ON DD04T~ROLLNAME = DD04L~ROLLNAME AND
                            DD04T~AS4LOCAL = 'A' AND
                            DD04T~DDLANGUAGE = langu_loc
                         FOR ALL ENTRIES IN missing
                         WHERE DD04L~ROLLNAME = missing-ROLLNAME
                           AND DD04L~AS4LOCAL = 'A'.
    That is, the ERP is using sequential read instead of direct read.
    Any idea is welcomed.
    Thanks & regards,
    Tommaso

    Hello,
    Thanks for your replies.
    I checked OSS and I found nothing.
    ST05 gives me this SQL command: (more than 500 sec!)
    SELECT T_00 . "ROLLNAME" , T_00 . "DOMNAME" , T_00 . "HEADLEN" , T_00 . "SCRLEN1" , T_00 . "SCRLEN2" , T_00 . "SCRLEN3" , T_01 . "DDLANGUAGE" , T_01 . "DDTEXT" , T_01 . "REPTEXT" , T_01 . "SCRTEXT_S" , T_01 . "SCRTEXT_M" , T_01 . "SCRTEXT_L" FROM "DD04L"
    T_00 INNER JOIN "DD04T" T_01 ON T_01 . "ROLLNAME" = T_00 . "ROLLNAME" AND T_01 . "AS4LOCAL" = 'A' AND T_01 . "DDLANGUAGE" = 'I' WHERE T_00 . "ROLLNAME" = 'VAL_TEXT' AND T_00 . "AS4LOCAL" = 'A'
    I executed it in SQL Studio and I got also a big execution time.
    But if I try
    SELECT  "ROLLNAME" ,  "DOMNAME" ,  "HEADLEN" , "SCRLEN1" , "SCRLEN2" , "SCRLEN3"  FROM "DD04L" WHERE T_00 . "ROLLNAME" = 'VAL_TEXT' AND T_00 . "AS4LOCAL" = 'A'
    I get the result in 1 ms.
    Is there something wrong in the inner join?
    What does it mean the operation "REOPEN"?
    How can I see from ST05 if an index has been used?
    Thanks & Regards,
    Tommaso

  • ABAP Program analysis with se30 how to avoid time out ?

    Hi Gurus,
    my problem is that I would like to analysis the performance issues of an ABAP Specific transaction.
    BAsically, I launch se30, provide transaction code under transaction field and click on execute.
    This launch transaction and then I put parameters and :
    a ) launch transcation
    b ) launch in background immediate.
    In both cases it doesn't work due to time out and I never obtain a usefull result.
    My question is : how can I use to analys such a transaction and avoid time out problem ?
    Thanks for your help,
    Regards
    Morgan

    One way would be to limit the selection criteria in such a way that the processed data is still representative but it finishes before the time out.
    Even when a time out occurs, there should already be a trace file up to that point that you can evaluate. Depends on your processing logic, if it is one big outer loop it might be valid data, if you have several independent blocks, then you might be missing something important.
    There is also the option "in parallel mode" where you can capture running BDC processes for analysis, maybe try this option as well. The trace file might grow pretty big though the longer your process runs, depending on aggregation level.
    Thomas

  • Receiving Transaction Manager Time out in iProcurement Receiving!

    Hi All,
    Database:10.2.0.4.0
    Oracle Aps:12.0.6
    O/S:AIX 64 bits 5.3 L
    We are unable to create any receipts due to following error.Checked Receiving Transaction Manager and that is running fine.
    Error Message
    Your receipt could not be created successfully because your receiving transaction manager timed out.
    Please contact your System Administrator for further assistance.
    Steps To Reproduce
    The issue can be reproduced at will with the following steps:
    1. In Iprocurement select requisition to receive
    2. Enter required data and press submit
    3. on screen receive Items: review and submit get above error message
    Profile RCV: Processing Mode is currently set to 'online'
    Could anyone please share resolution to such an issue faced before.
    Thanks for your time!
    Regards,

    Follow the Metalink ID: 375152.1

  • 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,
    Kaoru

    No, 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

  • Transaction time out

    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
    > >                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • How to Increase Time-out for Agent Manager in OLT?

    Hello All,
    When using the Oracle Load Testing Agent Manager for a load test of multiple scripts, I often get time-outs at the start of a test from OLT:
    "Error communicating with.... : timed out after 60 seconds".
    When I check the agentmanager.log file on the remote PC (Win XP SP2) I can see that the communcation started with the last line saying
    "connected to server=......yaddayadda.... queue=queue/AgentPoolNotificationQueue"
    which I assume means there was communication. And there were 2 attempts to start. After the first attempt, the entry:
    05:31:09,513 WARN [AgentProcess] Forcibly terminating process 8041484 for agent agId1530_rndd49ae6b9-a8ec-4a0d-920d-16ee6c7021f4
    The agentmanager_auth.log file show 2 lines near the start time of the test:
    2010-05-12 05:30:18,606 INFO [URL:t3://..........au:8088;Requestor Username: oats;Requestor Key:f6272e33-9428-425b-b52d-c0363f863e43;Requestor Queue:queue/AgentPoolNotificationQueue;Request ID:36;Request:startagent;] - authentication successful
    2010-05-12 05:31:09,513 INFO [URL:t3://..........au:8088;Requestor Username: oats;Requestor Key:f6272e33-9428-425b-b52d-c0363f863e43;Requestor Queue:queue/AgentPoolNotificationQueue;Request ID:42;Request:stopagent;] - authentication successful
    Why was there a 'stopagent'?
    The log from a successful agent show lines after the "Connected to server...." line ( "startAgent( pathTo.....a.. Launching agent.... Launched process 8792944 for agaent agId.....") so something appears to have not happened on the failed agents.
    When starting a test immediately (rather than scheduling it as I want to for off-peak times) and the agents time out, I can stop it & restart test. Usually then they all start successfully.
    Does anyone have any suggestions on failure reasons & possible solutions?
    If there's nothing else that I might have missed, I'd like to trying increasing the time-out to say 120 or 500 seconds.
    How can I do this?
    Is there a way to get the agents to try starting again, or add a new vUser/script instance one the test is running?
    Many thanks,
    Neil
    Edited by: Neil S on May 12, 2010 9:16 AM

    Hi Ramesh,
                          I guess you need to increase the parameter "icm/keep_alive_timeout" value, it's default value is 60. please gothrough the link
    http://help.sap.com/saphelp_webas630/helpdata/en/0b/1c7e7abbc311d5993a00508b6b8b11/content.htm
    To increase this go to RZ10 and add this parameter in Instance profile and modify the value then restart the server to make  the changes effective.
    Regards,
    Hari
    PS: Point's are welcome

  • 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
    Vivek

    Hi,
    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 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

  • Coherence and EclipseLink - JTA Transaction Manager - slow response times

    A colleague and I are updating a transactional web service to use Coherence as an underlying L2 cache. The application has the following characteristics:
    Java 1.7
    Using Spring Framework 4.0.5
    EclipseLink 12.1.2
    TopLink grid 12.1.2
    Coherence 12.1.2
    javax.persistence 12.1.2
    The application is split, with a GAR in a WebLogic environment and the actual web service application deployed into IBM WebSphere 8.5.
    When we execute a GET from the server for a decently sized piece of data, the response time is roughly 20-25 seconds. From looking into DynaTrace, it appears that we're hitting a brick wall at the "calculateChanges" method within EclipseLink. Looking further, we appear to be having issues with the transaction manager but we're not sure what. If we have a local resource transaction manager, the response time is roughly 500 milliseconds for the exact same request. When the JTA transaction manager is involved, it's 20-25 seconds.
    Is there a recommendation on how to configure the transaction manager when incorporating Coherence into a web service application of this type?

    Hi Volker/Markus,
    Thanks a lot for the response.
    Yeah Volker, you are absolutely right. the 10-12 seconds happens when we have not used the transaction for several minutes...Looks like the transactions are moved away from the SAP buffer or something, in a very short time.
    and yes, the ABAP WP's are running in Pool 2 (*BASE) and the the JAVA server, I have set up in another memory pool of 7 GB's.
    I would say the performance of the JAVA part is much better than the ABAP part.
    Should I just remove the ABAP part of the SOLMAN from memory pool 2 and assign the JAVA/ABAP a separate huge memory pool  of say like 12-13 GB's.
    Will that likely to improve my performance??
    No, I have not deactivated RSDB_TDB in TCOLL from daily twice to weekly once on all systems on this box. It is running daily twice right now.
    Should I change it to weekly once on all the systems on this box?  How is that going to help me?? The only thinng I can think of is that it will save me some CPU utilization, as considerable CPU resources are needed for this program to run.
    But my CPU utilization is anyway only like 30 % average. Its a i570 hardware and right now running 5 CPU's.
    So you still think I should deactivate this job from daily twice to weekly once on all systems on this box??
    Markus, Did you open up any messages with SAP on this issue.?
    I remember working on the 3.2 version of soultion manager on change management and the response times very much better than this as compared to 4.0.
    Let me know guys and once again..thanks a lot for your help and valuable input.
    Abhi

  • Transaction on Oracle 9i data source connection times out before JTA transaction

    Hello,
    I have a MDB with a long-running transaction (3600 second timeout).
    In the MDB, I make a call to another EJB that has its transaction
    attribute set to NotSupported (I do this because I need
    non-transactional semantics in the called method).
    If the EJB call take more than about a minute to complete, then I get a
    datasource error when using the data source in the MDB after the return
    (see error at bottom). However, if the call completes quickly, then I do
    not get this error. It seems like the datasource connection somehow
    times out, but I don't see where I can change this timeout.
    pseudocode:
    // timeout set to 3600 seconds
    transactional MDB onMessage() {
    // receive connection from Oracle BEA driver
    // myEJB performLongOperation has transaction attribute
    // set to NotSupported
    String result = myEJB.performLongOperation();
    // use connection from Oracle BEA driver
    If the performLongOperation takes more than about a minute, then I get
    the following error when using the connection after the operation:
    Caused by: java.sql.SQLException: XA error: XAER_NOTA : The XID is not
    valid start() failed on resource 'Oracle IDENT Connection Pool':
    XAER_NOTA : The XID is not valid
    javax.transaction.xa.XAException: [BEA][Oracle JDBC Driver]Oracle XA
    Error Occurred. Native Error: 24756
    at
    weblogic.jdbcx.oracle.OracleImplXAResource.checkError(Unknown Source)
    at weblogic.jdbcx.oracle.OracleImplXAResource.start(Unknown Source)
    at weblogic.jdbcx.base.BaseXAResource.start(Unknown Source)
    at weblogic.jdbc.jta.DataSource.start(DataSource.java:617)
    at
    weblogic.transaction.internal.XAServerResourceInfo.start(XAServerReso
    urceInfo.java:1075)
    at
    weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerRe
    sourceInfo.java:1007)
    at
    weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerRes
    ourceInfo.java:218)
    at
    weblogic.transaction.internal.ServerTransactionImpl.enlistResource(Se
    rverTransactionImpl.java:419)
    at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1287)
    at
    weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1
    250)
    at
    weblogic.jdbc.wrapper.JTAConnection.getXAConn(JTAConnection.java:185)
    at
    weblogic.jdbc.wrapper.JTAConnection.checkConnection(JTAConnection.jav
    a:80)
    at
    weblogic.jdbc.wrapper.Connection.createStatement(Connection.java:297)

    Thanks for the reply.
    I don't have contract customer support access with BEA, and thus I can't
    download the patch. Is there any other workaround for this?
    Thanks
    Slava Imeshev wrote:
    Steven,
    Please check this:
    http://www.viewtier.com/newsgroups/thread.jspa?threadID=20&tstart=0
    Hope this helps.
    Regards,
    Slava Imeshev
    "Steven Ostrowski" <[email protected]> wrote in message news:40cf35cc@mktnews1...
    I have a MDB with a long-running transaction (3600 second timeout).
    In the MDB, I make a call to another EJB that has its transaction
    attribute set to NotSupported (I do this because I need
    non-transactional semantics in the called method).
    If the EJB call take more than about a minute to complete, then I get a
    datasource error when using the data source in the MDB after the return
    (see error at bottom). However, if the call completes quickly, then I do
    not get this error. It seems like the datasource connection somehow
    times out, but I don't see where I can change this timeout.
    pseudocode:
    // timeout set to 3600 seconds
    transactional MDB onMessage() {
    // receive connection from Oracle BEA driver
    // myEJB performLongOperation has transaction attribute
    // set to NotSupported
    String result = myEJB.performLongOperation();
    // use connection from Oracle BEA driver
    If the performLongOperation takes more than about a minute, then I get
    the following error when using the connection after the operation:
    Caused by: java.sql.SQLException: XA error: XAER_NOTA : The XID is not
    valid start() failed on resource 'Oracle IDENT Connection Pool':
    XAER_NOTA : The XID is not valid
    javax.transaction.xa.XAException: [BEA][Oracle JDBC Driver]Oracle XA
    Error Occurred. Native Error: 24756
    at
    weblogic.jdbcx.oracle.OracleImplXAResource.checkError(Unknown Source)
    at weblogic.jdbcx.oracle.OracleImplXAResource.start(Unknown Source)
    at weblogic.jdbcx.base.BaseXAResource.start(Unknown Source)
    at weblogic.jdbc.jta.DataSource.start(DataSource.java:617)
    at
    weblogic.transaction.internal.XAServerResourceInfo.start(XAServerReso
    urceInfo.java:1075)
    at
    weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerRe
    sourceInfo.java:1007)
    at
    weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerRes
    ourceInfo.java:218)
    at
    weblogic.transaction.internal.ServerTransactionImpl.enlistResource(Se
    rverTransactionImpl.java:419)
    at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1287)
    at
    weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1
    250)
    at
    weblogic.jdbc.wrapper.JTAConnection.getXAConn(JTAConnection.java:185)
    at
    weblogic.jdbc.wrapper.JTAConnection.checkConnection(JTAConnection.jav
    a:80)
    at
    weblogic.jdbc.wrapper.Connection.createStatement(Connection.java:297)

  • 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,
    CD

    What 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 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!
    Young

    What 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.

Maybe you are looking for

  • How to create a dynamic fields in the Adobe Interactive form ?....urgent...

    Hi Experts, I'm working on Adobe Interactive form developed in WDP ABAP.( I have successfully config the ADS in my server.) Action: 1. Create two view - first_view and second_view in the WDP ABAP.. 2. In the first_view, there are a input field( named

  • MRBR release invoices automatically quantity variance

    For a purchase order item there are several good receipts and several invoices. Although the quantity of the goods receipt is smaller than the quantity invoiced, the quantity of goods received is bigger than the first invoice. So the first invoice sh

  • Text file generator gets out of sync!

    Has anyone any experience of this behaviour in the text file generator in Motion...... Basically the first entry in the list is only displayed for half the time of the other entries! This means that any repeat keyframes that I apply (even if I apply

  • Tumblr's images won't expand -- known to be only a Firefox issue

    In the last three-ish days, I've been noticing that my Tumblr dashboard: a] won't load past a few pages (I use infinite scrolling) b] won't expand any images when I click on them c] won't let me edit posts, period All of these are not an issue in Chr

  • Error in swap buffer!

    Has anyone seen this error message? This is happening on one of my machine. I tried the same program on another machine and it ran fine! This is a graphic program so I think it might have something to do with double buffering? How do I fix this? Thx