F.27 Transaction timeout error
Hello
In ECC Production, F.27 Transaction is running foreground morethan 45 minutes and it got terminated due to timout error,
But same report executed and completed background within 01 Min, Report also fine.
I don't how it get completed, Anybody have this idea?
Regards
Karthik.M
Hi Karthik
I thing you may require to apply the SAP Note for code correction. before that check with ABAPer / function consultant
1926253 - COLLECT_OVERFLOW in FI correspondence
BR
SS
Similar Messages
-
Transaction timeout error in 14.0
Hi,
I am working on MII 14.0 SP05.
One of my transactions deals with a huge volume of data due to which I get a time out error while executing the transaction in workbench and a NULL alert when I run it from my UI page.
I checked running the SQL package in the source system, though it takes around 30 mins but gets executed successfully.
Through UI I get the NULL alert exactly after 10 min.
I did following:
Increased 'Read Time Out' and 'Connection Time Out' to 3000 by going into Help --> Settings in workbench
Increased time out variable of my data server
Increased response time out in my SQL query action block
Added ExecutionTimeout global variable
All these things were of no help to my issue.
Need inputs to get this resolved.
Thanks & Regards,
AnujHi Anushree,
The package connects to different systems internally, that is why it takes a long time for its execution and as of now we don't see any possibility of optimizing the interface.
I will ask my basis team to go through the link you have given and update parameters accordingly and will update here.
Thanks & Regards,
Anuj -
Getting timeout error while updating a record from c#
Hi,
I have around 30k records in a tables. When I update that record inside the Transaction (Enterprise Data Library, c#) , it takes long time and throws timeout error.
But I am able to update the same record via Toad.
In the morning I tried same updating the record, it works without any change in the code or script.+
is it due table lock or db related issue? please adivse, how to resolve if occurs again.
anandCode:
private static void Save()
using (DBTransactionManager dbTransactionManager = new DBTransactionManager())
try
DataTableDAL.Instance.ExecuteDML("Update Voyage SET BallastBonus = 30000 WHERE ID = 'AE53B610BEA743EC8AFBAED0C8349BF8';");
//commit database
dbTransactionManager.Commit();
catch
dbTransactionManager.RollBack();
throw;
Table
Column Name ID Pk Null? Data Type Default Histogram Encryption Alg Salt
ID 1 1 N NVARCHAR2 (32) None
CALCNUMBER 2 N NUMBER (10) None
CURRENCYID 3 N NVARCHAR2 (32) Frequency
CALCTYPE 4 N NUMBER (5) Frequency
ESTIMATEDESCRIPTION 5 Y NVARCHAR2 (200) None
ESTIMATEGROUPDESCRIPTION 6 Y NVARCHAR2 (200) None
BALLASTBONUS 7 Y NUMBER (12,2) None
BALLASTBONUSCOMMPCT 8 Y NUMBER (6,3) None
ISESTIMATE 9 N NUMBER (1) None
ADDITIONALSTEAMVALUE 10 Y NUMBER (8,4) None
ISADDITIONALSTEAMPCT 11 Y NUMBER (1) None
ADDITIONALPORTVALUE 12 Y NUMBER (8,4) None
ISADDITIONALPORTPCT 13 Y NUMBER (1) None
CREATEDBY 14 N NVARCHAR2 (32) Frequency
CREATEDDATE 15 N DATE None
UPDATEDBY 16 Y NVARCHAR2 (32) None
UPDATEDDATE 17 Y DATE None
LUMPSUMCARGOCOST 18 Y NUMBER (1) None
BUNKERPRICEMETHOD 19 Y VARCHAR2 (30 Byte) None
INCCONTCALCRESULT 20 Y NUMBER (1) None
FINAL_EST 21 Y NUMBER None
SPOT_VOYAGE 22 Y NUMBER (1) None
ISRUNCOSTEDIT 23 Y NUMBER (1) None
Index
Table doesnt have any index, except primary key index.
Total Records
35,000
Hope this input might sufficient to help me. -
Transaction Timeout (BPEL v10.1.2.0.0, WebLogic 8.1 sp4)
We are attempting to process a transform on a medium sized xml doc (~4.5 MB). For the test case we are simply reading the the doc using the FileAdapter, performing a transformation, and then writing the result to a file using the FileAdapter once again. The flow works fine for smallish files (under ~4MB), however, when dropping a file greater than that size the flow fails once finished while writing entries to the BPEL audit log with a TransactionTimedOutException (see exception below).
I understand what is happening and why (it certainly takes longer than 2 mins to process the file). I have also done quite a bit of digging around for references to this issue and found several posts regarding bumping the transaction timeout value when running the OC4J container. My problem is that we are not running the OC4J container. I know how to manage the default transaction timeout value for WebLogic but it appears that the BPEL application doesn't seem to be honoring the default transaction timeout on the WL Server. I have come to this conclusion for two reasons: first, the default transaction timeout on the WL Server (before modification) is 30 seconds, not the 120 seconds that this transaction is timing out on. second, changing the transaction timeout value on the WebLogic server has no impact on this issue what so ever. I can set the transaction timeout to any value I like, the process ALWAYS times out after 120 seconds.
Is there another setting on the BPEL server that I may have missed that is overriding the default timeout, i.e. is it possible that when the BPEL server process is starting the transaction it is setting the timeout on the TransactionManager in code prior to starting the transaction?
Any pointers are greatly appreciated.
------------- START STACK TRACE ------------------
<2007-03-15 13:50:24,625> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "cube delivery": Cannot insert audit trail.
The process domain was unable to insert the current log entries for the instance "10601" to the audit trail table. The exception reported is: The transaction is no longer active - status: 'Rolled back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 120 seconds
Name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)],Xid=BEA1-0021B65431A170F9CFEF(31469464),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=120,seconds left=60,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread Group for Queue: 'default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=ended,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@154d033,re-Registered = false),SCInfo[f58_integration+orabpelServer]=(state=active),properties=({weblogic.transaction.name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)], weblogic.jdbc=t3://127.0.0.1:9700}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+, XAResources={},NonXAResources={})],CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+)]'. No further JDBC access is allowed within this transaction.
Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
sql statement: INSERT INTO audit_trail( cikey, domain_ref, count_id, block, block_csize, block_usize, log ) VALUES( ?, ?, ?, ?, ?, ?, ? )
<2007-03-15 13:50:24,643> <ERROR> <default.collaxa.cube.engine.dispatch> <BaseScheduledWorker::process> Failed to handle dispatch message ... exception ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 120 seconds
Name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)],Xid=BEA1-0021B65431A170F9CFEF(31469464),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=120,seconds left=60,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread Group for Queue: 'default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=ended,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@154d033,re-Registered = false),SCInfo[f58_integration+orabpelServer]=(state=active),properties=({weblogic.transaction.name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)], weblogic.jdbc=t3://127.0.0.1:9700}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+, XAResources={},NonXAResources={})],CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+)
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1614)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1117)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1881)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1034)
at weblogic.transaction.internal.WLSTimer.trigger(WLSTimer.java:31)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
; nested exception is: weblogic.transaction.internal.TimedOutException: Transaction timed out after 120 seconds
Name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)],Xid=BEA1-0021B65431A170F9CFEF(31469464),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=120,seconds left=60,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread Group for Queue: 'default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=ended,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@154d033,re-Registered = false),SCInfo[f58_integration+orabpelServer]=(state=active),properties=({weblogic.transaction.name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)], weblogic.jdbc=t3://127.0.0.1:9700}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+, XAResources={},NonXAResources={})],CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+)
------------- END STACK TRACE ------------------Hi
i am facing a similar problem..did u find the solution for this problem?
Please pass the solution/workaround u performed for solving this...
Thanks & Regards
Subramanian -
Redelivery limit not working for transaction timeout?
hi,
we have a redelivery limit on a queue that works, except for when there is a transaction timeout. in this case, the message seems to be redelivered infinitely. Is this a bug? a feature?
we are using Weblogic Server 8.1 SP4. we don't have the source code, so i am not sure how the error handling is done or what exceptions are thrown.
------------------ejb-jar.xml------------
<message-driven>
<ejb-name>ImporFileReceiver</ejb-name>
<ejb-class>au.com.auspost.pcms.common.integration.ejb.mdb.ImporFileReceiverMdb</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
<subscription-durability>NonDurable</subscription-durability>
</message-driven-destination>
</message-driven>
<container-transaction>
<method>
<ejb-name>ImporFileReceiver</ejb-name>
<method-intf>Local</method-intf>
<method-name>onMessage</method-name>
<method-params>
<method-param>javax.jms.Message</method-param>
</method-params>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>ImporFileReceiver</ejb-name>
<method-intf>Remote</method-intf>
<method-name>onMessage</method-name>
<method-params>
<method-param>javax.jms.Message</method-param>
</method-params>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
------------------------ weblogic-ejb-jar.xml ---------
<weblogic-enterprise-bean>
<ejb-name>ImporFileReceiver</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>10</max-beans-in-free-pool>
<initial-beans-in-free-pool>10</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>jms/pcmsImportFileQueue</destination-jndi-name>
<connection-factory-jndi-name>jms/pcmsConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>3600</trans-timeout-seconds>
</transaction-descriptor>
<reference-descriptor>
</reference-descriptor>
<dispatch-policy>pcms.execute.queue.mdb.internal</dispatch-policy>
<remote-client-timeout>0</remote-client-timeout>
</weblogic-enterprise-bean>
------------------------ config.xml -----------------
<JMSServer Name="eParcel JMS server"
Store="eParcel JMS Server File Store" Targets="wls_pcms_prod1">
<JMSQueue CreationTime="1190981682976"
ErrorDestination="PCMS Import File Error Queue"
JNDIName="jms/pcmsImportFileQueue"
Name="PCMS Import File Queue" RedeliveryLimit="2"/>
<JMSQueue CreationTime="1208347415759"
JNDIName="jms/pcmsImportFileErrorQueue" Name="PCMS Import File Error Queue"/>
</JMSServer>
<JMSConnectionFactory JNDIName="jms/pcmsConnectionFactory"
Name="eParcel JMS Connection Factory" Targets="wlc_pcms_prod"/>
<JMSConnectionFactory JNDIName="jms/pcmsXAConnectionFactory"
Name="eParcel JMS XA Connection Factory" Targets="wlc_pcms_prod" XAConnectionFactoryEnabled="true"/>
-------------- weblogic log ---------------
####<24/04/2008 01:53:58 PM EST> <Warning> <EJB> <HX415> <wls_pcms_prod1> <ExecuteThread: '12' for queue: 'weblogic.kernel.Default'> <project_admin> <> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was:
javax.ejb.EJBException: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 3599 seconds
Name=[EJB au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBean.handleMessage(org.apache.xmlbeans.XmlObject)],Xid=BEA1-696C9947A48195BA18DC(68926234),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=3599,seconds left=60,activeThread=Thread[ExecuteThread: '12' for queue: 'weblogic.kernel.Default',5,Thread Group for Queue: 'weblogic.kernel.Default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=ended,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@447373e,re-Registered = false),SCInfo[wlsd_auspost_prod+wls_pcms_prod1]=(state=active),properties=({weblogic.transaction.name=[EJB au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBean.handleMessage(org.apache.xmlbeans.XmlObject)], weblogic.jdbc=t3://10.3.2.35:7003}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=wls_pcms_prod1+10.3.2.35:7003+wlsd_auspost_prod+t3+, XAResources={JMS_eParcel JMS Server File Store, weblogic, wlsd_auspost_prod, com},NonXAResources={})],CoordinatorURL=wls_pcms_prod1+10.3.2.35:7003+wlsd_auspost_prod+t3+)
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(I)V(ServerTransactionImpl.java:1614)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(Ljava/util/List;I)V(ServerTransactionManagerImpl.java:1117)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp()V(TransactionManagerImpl.java:1881)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp()V(ServerTransactionManagerImpl.java:1034)
at weblogic.transaction.internal.WLSTimer.trigger(Lweblogic/time/common/Schedulable;)V(WLSTimer.java:31)
at weblogic.time.common.internal.ScheduledTrigger.run()Ljava/lang/Object;(Optimized Method)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;(Optimized Method)
at weblogic.security.service.SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;(SecurityManager.java:121)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally()V(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(Lweblogic/kernel/ExecuteThread;)V(ScheduledTrigger.java:223)
at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(Optimized Method)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)
; nested exception is: weblogic.transaction.internal.TimedOutException: Transaction timed out after 3599 seconds
Name=[EJB au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBean.handleMessage(org.apache.xmlbeans.XmlObject)],Xid=BEA1-696C9947A48195BA18DC(68926234),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=3599,seconds left=60,activeThread=Thread[ExecuteThread: '12' for queue: 'weblogic.kernel.Default',5,Thread Group for Queue: 'weblogic.kernel.Default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=ended,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@447373e,re-Registered = false),SCInfo[wlsd_auspost_prod+wls_pcms_prod1]=(state=active),properties=({weblogic.transaction.name=[EJB au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBean.handleMessage(org.apache.xmlbeans.XmlObject)], weblogic.jdbc=t3://10.3.2.35:7003}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=wls_pcms_prod1+10.3.2.35:7003+wlsd_auspost_prod+t3+, XAResources={JMS_eParcel JMS Server File Store, weblogic, wlsd_auspost_prod, com},NonXAResources={})],CoordinatorURL=wls_pcms_prod1+10.3.2.35:7003+wlsd_auspost_prod+t3+).Thanks Tom,
Good point. The timeout exception is on ImportFileHandlerBean.handleMessage()....which is a session bean. The MDB must call this session bean, which also has a 3600 second timeout. It is confusing since the descriptor for the MDB has the transaction-timeout set, but i assume this is ignored for 'not-supported').
I guess you would need to look at the code, but is there anyway a message go back on the queue, and not get the redelivery incremented?
(I just had an evil thought...maybe the code could be physically sending the message onto the queue again when there is a timeout on the session bean.....hence would not get the redelivery incremented.....)
-------------- ejb-jar.xml ----------------
<session>
<ejb-name>ImportFileHandler</ejb-name>
<local-home>au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerLocalHome</local-home>
<local>au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerLocal</local>
<ejb-class>au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
----------- weblogic-ejb.jar.xml -----------
<weblogic-enterprise-bean>
<ejb-name>ImportFileHandler</ejb-name>
<stateless-session-descriptor>
</stateless-session-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>3600</trans-timeout-seconds>
</transaction-descriptor>
<reference-descriptor>
</reference-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<local-jndi-name>ejb/ImportFileHandlerLocal</local-jndi-name>
<remote-client-timeout>0</remote-client-timeout>
</weblogic-enterprise-bean> -
Unreported Transaction timeout on commit (Oracle)
I'm expecting an Oracle error upon commit using "deferred constraints" and
executing an INSERT that should result in a constraint violation. I am not
seeing an error but the transaction hangs for 30seconds (JTA timeout
setting) and then continues without an exception. The session bean client
has no indication that the transaction has failed.
I've tried implicit and explicit transations from the client and the session
bean is marked as required.
Weblogic: 8.1 sp1
DB: Oracle 8.1.6
Driver: Oracle Thin XA
How is it possible that Oracle fails upon commit but the JDBC connection
waits for a timeout, and ALSO how is it possible that I'm not seeing a
transaction timeout exception?
(i've changed the JTA timeout setting to verify that this is the timeout
that is occuring and sure enough if i make it 20 seconds it returns after
20, 60, etc...)
M
Settings in Domain_name-JTA and Services-JTA are essentially the same settings. At least this is what I see - my changes to Services-JTA are reflected in Domain_name-JTA.
Edited by: Valery_Cherepanov on 11.08.2012 14:32 -
Weblogic 7 SP5 SQL Exceptions follow a JTA transaction timeout
I have a problem in Weblogic 7 SP5 that was not happening in SP2. I'm using the
Weblogic jDriver (weblogic.jdbc.mssqlserver4.Driver)
I have a transaction that times out due to JTA transaction timeout, and then gets
marked for rollback. For several minutes after the timeout, I get many SQL Exceptions
with bogus messages like "invalid column name" when the column name is, in fact,
correct.
Then the weblogic log file shows "Exception during rollback of transaction" (javax.transaction.SystemException:
Heuristic hazard). Next, the connection is tested on reserve, this test fails,
and the connection is refreshed. As soon as the connection is refreshed, I stop
getting SQL exceptions and everything starts working correctly again.
It seems like the transaction timeout is making the connection go bad, and somehow
other requests are using this bad connection before the transaction finishes rolling
back. What could the problem be? Some excerpts from my app log and weblogic log
are below.
com.workpoint.server.ejb.WorkPointEJBException: The transaction is no longer active
- status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException:
Transaction timed out after 901 seconds
Name=[EJB com.storeperform.taskmgr.ejb.procrelease.ProcReleaseBean.distributeToOrgUnit(com.storeperform.taskmgr.values.DistributionUnit)],Xid=17109:68c10765ba68aaaa(12114044),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=901,seconds left=60,activeThread=Thread[WorkQueueThread[q=1, qName=ProcReleaseTaskWorkers,
id=6],5,WorkQueueGroup[id=1, name=ProcReleaseTaskWorkers]],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assigned=none,xar=weblogic.jdbc.jts.Connection@18cd616,re-Registered
= false),SCInfo[DomainManager+edwards-s1]=(state=active),properties=({weblogic.transaction.name=[EJB
com.storeperform.taskmgr.ejb.procrelease.ProcReleaseBean.distributeToOrgUnit(com.storeperform.taskmgr.values.DistributionUnit)],
weblogic.jdbc=t3://10.10.3.17:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=edwards-s1+10.10.3.17:7001+DomainManager+t3+,
Resources={})],CoordinatorURL=edwards-s1+10.10.3.17:7001+DomainManager+t3+)]'.
No further JDBC access is allowed within this transaction.SQL Command = INSERT
INTO WP_PROCI_NODE_HIST (NODE_HIST_ID, NODE_HIST_DB, PROCI_ID, PROCI_DB, PROCI_NODE_ID,
PROCI_NODE_DB, NODE_ITERATION, NODE_STATE_ID, ROW_VERSION, LU_ID, LU_DATE) VALUES
weblogic.jdbc.mssqlserver4.TdsException: Invalid column name 'user_fname'.
[from weblogic log]
####<Jun 17, 2004 8:14:16 AM MDT> <Error> <EJB> <EDWARDS> <edwards-s1> <WorkQueueThread[q=1,
qName=ProcReleaseTaskWorkers, id=7]> <kernel identity> <> <010025> <Exception
during rollback of transaction Name=[EJB com.storeperform.taskmgr.ejb.procrelease.ProcReleaseBean.distributeToOrgUnit(com.storeperform.taskmgr.values.DistributionUnit)],Xid=17439:68c10765ba68aaaa(31878774),Status=Rolled
back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=3,seconds left=57,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=rolledback,assigned=edwards-s1,xar=weblogic.jdbc.jts.Connection@15e1b7e,re-Registered
= false),SCInfo[DomainManager+edwards-s1]=(state=rolledback),properties=({weblogic.transaction.name=[EJB
com.storeperform.taskmgr.ejb.procrelease.ProcReleaseBean.distributeToOrgUnit(com.storeperform.taskmgr.values.DistributionUnit)],
weblogic.jdbc=t3://10.10.3.17:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=edwards-s1+10.10.3.17:7001+DomainManager+t3+,
Resources={})],CoordinatorURL=edwards-s1+10.10.3.17:7001+DomainManager+t3+): javax.transaction.SystemException:
Heuristic hazard: (weblogic.jdbc.jts.Connection, HeuristicHazard, (javax.transaction.xa.XAException:
I/O exception while talking to the server, java.io.EOFException))
####<Jun 17, 2004 8:14:17 AM MDT> <Warning> <JDBC> <EDWARDS> <edwards-s1> <ExecuteThread:
'8' for queue: 'default'> <kernel identity> <> <001094> <A connection from pool
"sp_connection_pool" was tested during reserve with the SQL "select 1" and failed:
weblogic.jdbc.mssqlserver4.TdsException: I/O exception while talking to the server,
java.io.EOFException
...[stack trace omitted]...
This connection will now be refreshed.>Brad Swanson wrote:
According to BEA's documentation, the jDriver is deprecated (no longer supported)
in WLS 7 SP5. Not sure when they stopped supporting it, but sometime after SP2,
apparently. Our solution, unfortunately, was to stay with SP2. Using the newer,
supported JDBC driver would presumably fix the problem, but we didn't have time
to do a full regression test with a different driver.Hi, no. The jDriver is deprecated, not unsupported. For WLS releases that contain
the jDriver it will be supported for as long as we support the WLS release!
Deprecation just means that we may choose to not supply that driver in any future
release, and will not support it in that or any subsequent release.
Practically, much depends on which jDriver you're using. In decreasing order
of practical support we have: The weblogic.jdbc.oci.Driver to Oracle: We do actively
continue to fix bugs in it. The weblogic.jdbc.mssqlserver4.Driver: Very unlikely that
we will fix any new problem with it. The weblogic.jdbc.ifmx.Driver: Even less
likely that we will do anything with it...
I hope that makes it better for you.
Joe -
Timeout error in accessing CR 2008 with dynamic prompts from SAP Portal
Hi
We are using Business Objects XI 3.0 with Integration Kit for SAP
Solutions on Windows 2003 Server with Weblogic 10.0 server.we have
created a report (13 parameters) using Crystal Reports 2008 and
deployed on the BOE.Crystal Reports are created using opensql driver
and using tables.The prompts/parameters are created using Business
views.After deploying the report under the database configuration under
When viewing report the option selected is "Use SSO context for
database logon".
Later an iview is created on SAP Portal pointing to Crystal Report
using Business Objects iview template.The SSO is working fine and we
are able to select the parameters and when clicked ok we get an
error.we have pasted the error below when we try to view source :
<form action="../PlatformServices/service/app/error.do" method='post'>
<input type='hidden' name="errMsg" value="A timeout error has occurred"><input type='hidden' name="loc" value="en_GB">
<input type='hidden' name="pvl" value="en_GB">
<input type='hidden' name="errStack"
value="com.businessobjects.webutil.websessiontimeout.WebSessionTimeoutFilter.doFilter(WebSessionTimeoutFilter.java:142)
weblogic.servlet.internal.FilterChainImpl.doFilter
(FilterChainImpl.java:42)
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3368)
weblogic.security.acl.internal.AuthenticatedSubject.doAs
(AuthenticatedSubject.java:321)
weblogic.security.service.SecurityManager.runAs
(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)
Ljava.lang.Object;(Unknown Source)
weblogic.servlet.internal.WebAppServletContext.securedExecute
(WebAppServletContext.java:2117)
weblogic.servlet.internal.WebAppServletContext.execute
(WebAppServletContext.java:2023)
Thanks
KamalHello,
1)How do I assign my user ID to the organisational unit? Please advise me step by step as I am new to SRMu2026
2) Regarding error u201CThe following error text was processed in the system SR3 : Attribute for user USER18 contains errors. Inform system admin.
The error occurred on the application server eccserver1_SR3_01 and in the work process 0 . u201C
Using transaction SM21, I have discovered multiple errors for SAP instance eccserver1_SR3_01 like BBP_PU 245 transaction canceled, HTTP/RFC session has been deleted following timeout...
3) How do I run report BBP_CHECK_CONSISTENCY? With transaction SE38? What do I choose next from the options available?
This is too technical for me right now..maybe not in the future, but at this moment, I need more guidance...
Thank you,
Iuliana -
Oracle post failover transaction commit error
I have a problem on trasaction after database failover.
Solaris 8, WLS 6.1 sp3, Oracle 8.1.7 (2 Oracle instances, one is primary and
another is standby), JDK 1.3.1
We found this problem in Oracle (Net 8 connection time) failover test.
Here is what we did.
During the load, we shut down the primary Oracle server (box).
All in-flight transactions were wrong, this is ok.
When new requests came in, WebLogic begin to refresh the connections.
Because the primary Oracle server was down, it took about 70 seconds to
refresh a connection (due to the socket timeout value) and redirect to the
standby Oracle. This is fine.
After a while, all connections were refreshed and all connected to the
standby serever.
When I opened WebLogic console to monitor the in-flight transaction, I found
some transactions are doing committing and never finished.
At this time most of the transaction can go through but few of them through
an exception (attached at the end). This error could never gone although the
frequency was not high. The strange thing is I checked the database, the
data was committed.
I've tried Oracle OCI driver and thin driver, both had this problem. Is
there anyone can help me on that?
Thanks,
Wenji
<Jan 28, 2003 1:49:57 PM EST> <Error> <EJB> <Exception during commit of
transaction Name=[EJB
com.bankframe.bp.retail.solutionset.impl.customersearch.CustomerSearchSessio
nBean.processDataPacket(com.bankframe.bo.DataPacket)],Xid=28502:685f84a9ba5b
1ed8(192232),Status=Committing,numRepliesOwedMe=0,numRepliesOwedOthers=0,sec
onds since begin=122,seconds
left=60,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assign
ed=prod-srv2),SCInfo[prod+prod-srv2]=(state=pre-prepared),properties=({weblo
gic.transaction.name=[EJB
com.bankframe.bp.retail.solutionset.impl.customersearch.CustomerSearchSessio
nBean.processDataPacket(com.bankframe.bo.DataPacket)],
weblogic.jdbc=t3://10.161.46.31:7101}),OwnerTransactionManager=ServerTM[Serv
erCoordinatorDescriptor=(CoordinatorURL=prod-srv2+10.161.46.31:7101+prod+, R
esources={})],CoordinatorURL=prod-srv2+10.161.46.31:7101+prod+):
javax.transaction.SystemException: Timeout during commit processing
at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
nsactionImpl.java:243)
at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
Impl.java:189)
at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:272)
atWenji Tong wrote:
Thanks, Joe!
Things could be more complicate. I did some tests to find the details of the
problem. Here are the results.Hi,
This is developing into a bigger problem than I can solve informally in newsgroups,
so I suggest that you open an official support case with this information.
Joe
>
>
1. I've done a test. In this test, I shut down the Oracle and also stop the
load. After all threads and connection returned to the pool and all
transactions done (roll back or abandoned), I started load again. I still
could find this error. That means this error is not related to any in-flight
transactions.
2. After all connectioin failed over, this error was still not gone. The
frequency was not high, but it was always there.
3. In WebLogic console, monitor in-flight transaction, I saw some
transactions were doing committing, but never finished if there was no load.
When I saw an error printed in log, one of the committing transaction gone
but there came out another transaction doing the commit and can't be
finished. I'm not sure if it was related to WebLogic console's bug.
4. Increase the transaction timeout can fix this problem. Unfortunately, we
can't increase the transaction timeout anymore due to our business
requirements.
I hope those information will be helpful.
Thanks,
Wenji
"Joseph Weinstein" <[email protected]> wrote in message
news:[email protected]...
Wenji Tong wrote:
I have a problem on trasaction after database failover.
Solaris 8, WLS 6.1 sp3, Oracle 8.1.7 (2 Oracle instances, one is primary
and
another is standby), JDK 1.3.1
We found this problem in Oracle (Net 8 connection time) failover test.
Here is what we did.
During the load, we shut down the primary Oracle server (box).
All in-flight transactions were wrong, this is ok.
When new requests came in, WebLogic begin to refresh the connections.
Because the primary Oracle server was down, it took about 70 seconds to
refresh a connection (due to the socket timeout value) and redirect tothe
standby Oracle. This is fine.
After a while, all connections were refreshed and all connected to the
standby serever.
When I opened WebLogic console to monitor the in-flight transaction, Ifound
some transactions are doing committing and never finished.
At this time most of the transaction can go through but few of themthrough
an exception (attached at the end). This error could never gone althoughthe
frequency was not high. The strange thing is I checked the database, the
data was committed.
I've tried Oracle OCI driver and thin driver, both had this problem. Is
there anyone can help me on that?
Thanks,
WenjiHi. It seems that Oracle failover is not perfect. Our transactioncoordinator
is supposed to have control of the transaction. If a failover occurs while
a transaction is pending, the coordinator should still have the ability toroll
back the tx. Apparently there are cases where the failover causes an open
transaction to be committed, in such a way that even if the coordinatorhas
decided to roll it back, it can't. These may be when the failover occurswhile
we are waiting for the commit call to return. We either get an exceptionor
we get no return from the commit() call so we try to roll back and fail.The
actual commit succeeded, but we never knew.
Joe
<Jan 28, 2003 1:49:57 PM EST> <Error> <EJB> <Exception during commit of
transaction Name=[EJB
com.bankframe.bp.retail.solutionset.impl.customersearch.CustomerSearchSessio
>nBean.processDataPacket(com.bankframe.bo.DataPacket)],Xid=28502:685f84a9ba5b
>1ed8(192232),Status=Committing,numRepliesOwedMe=0,numRepliesOwedOthers=0,sec
onds since begin=122,seconds
left=60,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assign
>ed=prod-srv2),SCInfo[prod+prod-srv2]=(state=pre-prepared),properties=({weblo
gic.transaction.name=[EJB
com.bankframe.bp.retail.solutionset.impl.customersearch.CustomerSearchSessio
nBean.processDataPacket(com.bankframe.bo.DataPacket)],
weblogic.jdbc=t3://10.161.46.31:7101}),OwnerTransactionManager=ServerTM[Serv
>erCoordinatorDescriptor=(CoordinatorURL=prod-srv2+10.161.46.31:7101+prod+, R
esources={})],CoordinatorURL=prod-srv2+10.161.46.31:7101+prod+):
javax.transaction.SystemException: Timeout during commit processing
at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
nsactionImpl.java:243)
at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
Impl.java:189)
atweblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:272)
at -
Timeout error when trying to create repository
Hello,
I'm instaling ovm 3.2.3 and when I try to crete the storage repository from ovm manager I get a timeout error and it stops the creation. I've tried several times, I've reinstalled ovm and manager, but the error is always the same.
I've look into the log but I didn't find anything related to this error. Can somebody help me please?
The content of log is this one:
Job Construction Phase
Job ID: 1370010128786
begin()
Appended operation 'File System Construct' to object '0004fb0000050000d62f8093d31671e2 (fs_repositorio1)'.
Appended operation 'Repository Construct' to object '0004fb00000300005e7bb4e2447294b9 (3600508b1001c5a240ed9f472dfdbb60a)'.
commit()
Completed Step: COMMIT
Objects and Operations
Object (CREATED): [Repository] 0004fb00000300005e7bb4e2447294b9 (repositorio1)
Operation: Repository Construct
Object (CREATED): [LocalFileSystem] 0004fb0000050000d62f8093d31671e2 (fs_repositorio1)
Operation: File System Construct
Object (IN_USE): [StorageElement] 0004fb00001800006d86283bfc68236e (3600508b1001c5a240ed9f472dfdbb60a)
Object (IN_USE): [LocalFileServer] 0004fb0000090000d9ecb1e8a6707a5b (Local FS ovm)
Job Running Phase at 2013-05-31 15:22:08,786
Job Participants: [33:31:39:34:34:32:5a:43:32:31:30:33:30:36:51:34 (ovm)]
Actioner
15:22:09,461: Starting operation 'Repository Construct' on object '0004fb00000300005e7bb4e2447294b9 (repositorio1)'
15:22:09,465: Completed operation 'Repository Construct' with direction ==> LATER
15:22:09,478: Starting operation 'File System Construct' on object '0004fb0000050000d62f8093d31671e2 (fs_repositorio1)'
Job: 1370010128785/1370010128786, aborted post-commit by user: admin
Write Methods Invoked
15:22:08,960 class="InternalJobDbImpl" vessel_id=2960 method=addTransactionIdentifier accessLevel=6 owningTx=1370010128959
15:22:08,992 class="LocalFileServerDbImpl" vessel_id=1364 method=createFileSystem accessLevel=6 owningTx=1370010128959
15:22:09,023 class="LocalFileSystemDbImpl" vessel_id=2969 method=setName accessLevel=6 owningTx=1370010128959
15:22:09,047 class="LocalFileSystemDbImpl" vessel_id=2969 method=setFoundryContext accessLevel=6 owningTx=1370010128959
15:22:09,047 class="LocalFileSystemDbImpl" vessel_id=2969 method=onPersistableCreate accessLevel=6 owningTx=1370010128959
15:22:09,047 class="LocalFileSystemDbImpl" vessel_id=2969 method=setLifecycleState accessLevel=6 owningTx=1370010128959
15:22:09,048 class="LocalFileSystemDbImpl" vessel_id=2969 method=setRollbackLifecycleState accessLevel=6 owningTx=1370010128959
15:22:09,087 class="LocalFileSystemDbImpl" vessel_id=2969 method=setRefreshed accessLevel=6 owningTx=1370010128959
15:22:09,090 class="LocalFileSystemDbImpl" vessel_id=2969 method=setBackingDevices accessLevel=6 owningTx=1370010128959
15:22:09,090 class="LocalFileSystemDbImpl" vessel_id=2969 method=setUuid accessLevel=6 owningTx=1370010128959
15:22:09,090 class="LocalFileSystemDbImpl" vessel_id=2969 method=setPath accessLevel=6 owningTx=1370010128959
15:22:09,090 class="LocalFileSystemDbImpl" vessel_id=2969 method=setSimpleName accessLevel=6 owningTx=1370010128959
15:22:09,091 class="LocalFileSystemDbImpl" vessel_id=2969 method=addFileServer accessLevel=6 owningTx=1370010128959
15:22:09,091 class="LocalFileSystemDbImpl" vessel_id=2969 method=setStorageDevice accessLevel=6 owningTx=1370010128959
15:22:09,092 class="StorageElementDbImpl" vessel_id=1383 method=addLayeredFileSystem accessLevel=6 owningTx=1370010128959
15:22:09,094 class="LocalFileSystemDbImpl" vessel_id=2969 method=setSimpleName accessLevel=6 owningTx=1370010128959
15:22:09,094 class="LocalFileSystemDbImpl" vessel_id=2969 method=addJobOperation accessLevel=6 owningTx=1370010128959
15:22:09,110 class="LocalFileSystemDbImpl" vessel_id=2969 method=createRepository accessLevel=6 owningTx=1370010128959
15:22:09,132 class="RepositoryDbImpl" vessel_id=2975 method=setName accessLevel=6 owningTx=1370010128959
15:22:09,170 class="RepositoryDbImpl" vessel_id=2975 method=setFoundryContext accessLevel=6 owningTx=1370010128959
15:22:09,171 class="RepositoryDbImpl" vessel_id=2975 method=onPersistableCreate accessLevel=6 owningTx=1370010128959
15:22:09,171 class="RepositoryDbImpl" vessel_id=2975 method=setLifecycleState accessLevel=6 owningTx=1370010128959
15:22:09,171 class="RepositoryDbImpl" vessel_id=2975 method=setRollbackLifecycleState accessLevel=6 owningTx=1370010128959
15:22:09,213 class="RepositoryDbImpl" vessel_id=2975 method=setRefreshed accessLevel=6 owningTx=1370010128959
15:22:09,213 class="RepositoryDbImpl" vessel_id=2975 method=setDom0Uuid accessLevel=6 owningTx=1370010128959
15:22:09,213 class="RepositoryDbImpl" vessel_id=2975 method=setSharePath accessLevel=6 owningTx=1370010128959
15:22:09,213 class="RepositoryDbImpl" vessel_id=2975 method=setSimpleName accessLevel=6 owningTx=1370010128959
15:22:09,214 class="RepositoryDbImpl" vessel_id=2975 method=setFileSystem accessLevel=6 owningTx=1370010128959
15:22:09,214 class="LocalFileSystemDbImpl" vessel_id=2969 method=addRepository accessLevel=6 owningTx=1370010128959
15:22:09,215 class="RepositoryDbImpl" vessel_id=2975 method=setManagerUuid accessLevel=6 owningTx=1370010128959
15:22:09,215 class="RepositoryDbImpl" vessel_id=2975 method=setVersion accessLevel=6 owningTx=1370010128959
15:22:09,216 class="RepositoryDbImpl" vessel_id=2975 method=addJobOperation accessLevel=6 owningTx=1370010128959
15:22:09,233 class="RepositoryDbImpl" vessel_id=2975 method=setSimpleName accessLevel=6 owningTx=1370010128959
15:22:09,234 class="RepositoryDbImpl" vessel_id=2975 method=setDescription accessLevel=6 owningTx=1370010128959
15:22:09,248 class="InternalJobDbImpl" vessel_id=2960 method=setCompletedStep accessLevel=6 owningTx=1370010128959
15:22:09,253 class="InternalJobDbImpl" vessel_id=2960 method=setAssociatedHandles accessLevel=6 owningTx=1370010128959
15:22:09,475 class="InternalJobDbImpl" vessel_id=2960 method=setTuringMachineFlag accessLevel=6 owningTx=1370010128959
Job Aborted (Operation)com.oracle.ovm.mgr.api.exception.JobAbortException: OVMAPI_5000E Job: 1,370,010,128,786/1370010128785/Create Repository repositorio1, was aborted [Fri May 31 15:37:11 WEST 2013]
at com.oracle.ovm.mgr.api.job.JobEngine.checkJobStatus(JobEngine.java:642)
at com.oracle.ovm.mgr.api.job.JobEngine.objectAsyncStart(JobEngine.java:626)
at com.oracle.ovm.mgr.op.physical.storage.FileSystemConstruct.action(FileSystemConstruct.java:57)
at com.oracle.ovm.mgr.api.collectable.ManagedObjectDbImpl.executeCurrentJobOperationAction(ManagedObjectDbImpl.java:1156)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:356)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:333)
at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:865)
at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:244)
at com.oracle.ovm.mgr.api.physical.storage.LocalFileSystemProxy.executeCurrentJobOperationAction(Unknown Source)
at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:230)
at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:322)
at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1340)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:356)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:333)
at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:106)
at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:92)
at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:752)
at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:467)
at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:525)
at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
at java.lang.Thread.run(Thread.java:662)
15:22:09,476 class="RepositoryDbImpl" vessel_id=2975 method=setCurrentOperationToLater accessLevel=6 owningTx=1370010128959
15:22:09,477 class="InternalJobDbImpl" vessel_id=2960 method=setTuringMachineFlag accessLevel=6 owningTx=1370010128959
FailedOperationCleanup
Starting failed operation 'File System Construct' cleanup on object 'fs_repositorio1'
Complete rollback operation 'File System Construct' cleanup on object 'fs_repositorio1'
Rollbacker
15:37:11,587: Starting rollbacker...
Executing rollback operation 'File System Construct' on object '0004fb0000050000d62f8093d31671e2 (fs_repositorio1)'
Complete rollback operation 'File System Construct' completed with direction=DONE
15:37:11,600: Rollbacker completed...
Objects To Be Rolled Back
Object (CREATED): [Repository] 0004fb00000300005e7bb4e2447294b9 (repositorio1)
Object (CREATED): [LocalFileSystem] 0004fb0000050000d62f8093d31671e2 (fs_repositorio1)
Object (IN_USE): [LocalFileServer] 0004fb0000090000d9ecb1e8a6707a5b (Local FS ovm)
Object (IN_USE): [StorageElement] 0004fb00001800006d86283bfc68236e (3600508b1001c5a240ed9f472dfdbb60a)
Write Methods Invoked
15:22:08,960 class="InternalJobDbImpl" vessel_id=2960 method=addTransactionIdentifier accessLevel=6 owningTx=1370010128959
15:22:08,992 class="LocalFileServerDbImpl" vessel_id=1364 method=createFileSystem accessLevel=6 owningTx=1370010128959
15:22:09,023 class="LocalFileSystemDbImpl" vessel_id=2969 method=setName accessLevel=6 owningTx=1370010128959
15:22:09,047 class="LocalFileSystemDbImpl" vessel_id=2969 method=setFoundryContext accessLevel=6 owningTx=1370010128959
15:22:09,047 class="LocalFileSystemDbImpl" vessel_id=2969 method=onPersistableCreate accessLevel=6 owningTx=1370010128959
15:22:09,047 class="LocalFileSystemDbImpl" vessel_id=2969 method=setLifecycleState accessLevel=6 owningTx=1370010128959
15:22:09,048 class="LocalFileSystemDbImpl" vessel_id=2969 method=setRollbackLifecycleState accessLevel=6 owningTx=1370010128959
15:22:09,087 class="LocalFileSystemDbImpl" vessel_id=2969 method=setRefreshed accessLevel=6 owningTx=1370010128959
15:22:09,090 class="LocalFileSystemDbImpl" vessel_id=2969 method=setBackingDevices accessLevel=6 owningTx=1370010128959
15:22:09,090 class="LocalFileSystemDbImpl" vessel_id=2969 method=setUuid accessLevel=6 owningTx=1370010128959
15:22:09,090 class="LocalFileSystemDbImpl" vessel_id=2969 method=setPath accessLevel=6 owningTx=1370010128959
15:22:09,090 class="LocalFileSystemDbImpl" vessel_id=2969 method=setSimpleName accessLevel=6 owningTx=1370010128959
15:22:09,091 class="LocalFileSystemDbImpl" vessel_id=2969 method=addFileServer accessLevel=6 owningTx=1370010128959
15:22:09,091 class="LocalFileSystemDbImpl" vessel_id=2969 method=setStorageDevice accessLevel=6 owningTx=1370010128959
15:22:09,092 class="StorageElementDbImpl" vessel_id=1383 method=addLayeredFileSystem accessLevel=6 owningTx=1370010128959
15:22:09,094 class="LocalFileSystemDbImpl" vessel_id=2969 method=setSimpleName accessLevel=6 owningTx=1370010128959
15:22:09,094 class="LocalFileSystemDbImpl" vessel_id=2969 method=addJobOperation accessLevel=6 owningTx=1370010128959
15:22:09,110 class="LocalFileSystemDbImpl" vessel_id=2969 method=createRepository accessLevel=6 owningTx=1370010128959
15:22:09,132 class="RepositoryDbImpl" vessel_id=2975 method=setName accessLevel=6 owningTx=1370010128959
15:22:09,170 class="RepositoryDbImpl" vessel_id=2975 method=setFoundryContext accessLevel=6 owningTx=1370010128959
15:22:09,171 class="RepositoryDbImpl" vessel_id=2975 method=onPersistableCreate accessLevel=6 owningTx=1370010128959
15:22:09,171 class="RepositoryDbImpl" vessel_id=2975 method=setLifecycleState accessLevel=6 owningTx=1370010128959
15:22:09,171 class="RepositoryDbImpl" vessel_id=2975 method=setRollbackLifecycleState accessLevel=6 owningTx=1370010128959
15:22:09,213 class="RepositoryDbImpl" vessel_id=2975 method=setRefreshed accessLevel=6 owningTx=1370010128959
15:22:09,213 class="RepositoryDbImpl" vessel_id=2975 method=setDom0Uuid accessLevel=6 owningTx=1370010128959
15:22:09,213 class="RepositoryDbImpl" vessel_id=2975 method=setSharePath accessLevel=6 owningTx=1370010128959
15:22:09,213 class="RepositoryDbImpl" vessel_id=2975 method=setSimpleName accessLevel=6 owningTx=1370010128959
15:22:09,214 class="RepositoryDbImpl" vessel_id=2975 method=setFileSystem accessLevel=6 owningTx=1370010128959
15:22:09,214 class="LocalFileSystemDbImpl" vessel_id=2969 method=addRepository accessLevel=6 owningTx=1370010128959
15:22:09,215 class="RepositoryDbImpl" vessel_id=2975 method=setManagerUuid accessLevel=6 owningTx=1370010128959
15:22:09,215 class="RepositoryDbImpl" vessel_id=2975 method=setVersion accessLevel=6 owningTx=1370010128959
15:22:09,216 class="RepositoryDbImpl" vessel_id=2975 method=addJobOperation accessLevel=6 owningTx=1370010128959
15:22:09,233 class="RepositoryDbImpl" vessel_id=2975 method=setSimpleName accessLevel=6 owningTx=1370010128959
15:22:09,234 class="RepositoryDbImpl" vessel_id=2975 method=setDescription accessLevel=6 owningTx=1370010128959
15:22:09,248 class="InternalJobDbImpl" vessel_id=2960 method=setCompletedStep accessLevel=6 owningTx=1370010128959
15:22:09,253 class="InternalJobDbImpl" vessel_id=2960 method=setAssociatedHandles accessLevel=6 owningTx=1370010128959
15:22:09,475 class="InternalJobDbImpl" vessel_id=2960 method=setTuringMachineFlag accessLevel=6 owningTx=1370010128959
15:22:09,476 class="RepositoryDbImpl" vessel_id=2975 method=setCurrentOperationToLater accessLevel=6 owningTx=1370010128959
15:22:09,477 class="InternalJobDbImpl" vessel_id=2960 method=setTuringMachineFlag accessLevel=6 owningTx=1370010128959
15:37:11,488 class="LocalFileSystemDbImpl" vessel_id=2969 method=nextJobOperation accessLevel=6 owningTx=1370010128959
15:37:11,488 class="InternalJobDbImpl" vessel_id=2960 method=setFailedOperation accessLevel=6 owningTx=1370010128959
15:37:11,590 class="RepositoryDbImpl" vessel_id=2975 method=nextJobOperation accessLevel=6 owningTx=1370010128959
15:37:11,591 class="LocalFileSystemDbImpl" vessel_id=2969 method=nextJobOperation accessLevel=6 owningTx=1370010128959
15:37:11,591 class="StorageElementDbImpl" vessel_id=1383 method=nextJobOperation accessLevel=6 owningTx=1370010128959
15:37:11,591 class="LocalFileServerDbImpl" vessel_id=1364 method=nextJobOperation accessLevel=6 owningTx=1370010128959
15:37:11,600 class="LocalFileSystemDbImpl" vessel_id=2969 method=nextJobOperation accessLevel=6 owningTx=1370010128959
Completed Step: ROLLBACK
Job Aborted due to OVMAPI_5000E Job: 1,370,010,128,786/1370010128785/Create Repository repositorio1, was aborted [Fri May 31 15:37:11 WEST 2013]
com.oracle.ovm.mgr.api.exception.JobAbortException: OVMAPI_5000E Job: 1,370,010,128,786/1370010128785/Create Repository repositorio1, was aborted [Fri May 31 15:37:11 WEST 2013]
at com.oracle.ovm.mgr.api.job.JobEngine.checkJobStatus(JobEngine.java:642)
at com.oracle.ovm.mgr.api.job.JobEngine.objectAsyncStart(JobEngine.java:626)
at com.oracle.ovm.mgr.op.physical.storage.FileSystemConstruct.action(FileSystemConstruct.java:57)
at com.oracle.ovm.mgr.api.collectable.ManagedObjectDbImpl.executeCurrentJobOperationAction(ManagedObjectDbImpl.java:1156)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:356)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:333)
at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:865)
at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:244)
at com.oracle.ovm.mgr.api.physical.storage.LocalFileSystemProxy.executeCurrentJobOperationAction(Unknown Source)
at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:230)
at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:322)
at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1340)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:356)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:333)
at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:106)
at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:92)
at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:752)
at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:467)
at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:525)
at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
at java.lang.Thread.run(Thread.java:662)
End of JobHi,
To create a repository with Oracle VM Manager with NFS share, so the NFS share should have the write privilege.
if the repository with iSCSI so verify your configuration (give it all privilege).
after you verify your configuration and if this solved so good and if still the same error so
thinks to tell us the output of the files /var/log/ovs-agent.log and /var/log/messages
I hope this can help you
Best Regards -
Transaction timeout in BPEL for webservice invocation
[ERROR] [] [oracle.soa.bpel.engine.dispatch] [tid: orabpel.invoke.pool-4.thread-3] [userId: <anonymous>] [ecid: e8538d226bae7c2a:1914e8c0:148c67a5f26:-8000-00000000000031a2,1:27459] [APP: soa-infra] failed to handle message[[
weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds
BEA1-166C02569896A59BE380
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1788)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1676)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1988)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1586)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds
BEA1-166C02569896A59BE380
This is happening when invoking a webservices from BPEL and if it takes more than 5 minutes we are getting above Error
we have tried out SyncMaxWaitTime Property in BPEL configurations through SOA administration menu of EM. Also tried by increasing JTA timeout seconds in Service--JTA @ weblogic console.
Any suggestion or pointers..Hi,
Could help set the following...
The timeouts should be configured based on the below condition
SyncMaxWaitTime < BPEL EJB's transaction timeout < Global Transaction Timeout
The values could be: SyncMaxWaitTime (3600) ; BPEL EJB's transaction timeout (3600); Global Transaction Timeout JTA (7200)
Setting the SyncMaxWaitTime :
This is the maximum time a synchronous BPEL process waits before it times out to get the response from another BPEL or a web service
Login to EM console
Expand SOA and right click on "soa-infra"
From context menu, select SOA Administration –> BPEL properties
Click on "More BPEL Configuration properties"
Enter the appropriate value for the SyncMaxWaitTime
Setting the global transaction timeout at Weblogic Domain Level:
This property controls the transaction timeout seconds for active transactions. If the transaction is still in the "active" state after this time, it is automatically rolled back.
Log into Oracle Weblogic Administration Console.
Click Services -> JTA.
Change the value of Timeout Seconds to the required value (the default is 30)
Click Save.
Restart Oracle Weblogic Server.
Overriding the transaction timeout setting for BPEL EJB's:
The timeout properties for the EJB's control the particular timeout setting for the SOA application, overriding the global setting specified by the JTA timeout
Log into Oracle Weblogic Administration Console.
Click Deployments.
Expand soa-infra -> EJBs.
Click on the configuration tab for the timeout setting for each of EJB’s listed below and the change the time out values as required.
Following EJBs need to be updated:
BPELActivityManagerBean
BPELDeliveryBean
BPELDispatcherBean
BPELEngineBean
BPELFinderBean
BPELInstanceManagerBean
BPELProcessManagerBean
BPELSensorValuesBean
BPELServerManagerBean
Click Save.
Restart Oracle Weblogic Server.
I hope you find it useful!
hugs! -
Wls 10.3 weblogic-webservices.xml transaction-timeout attribute not working
Hi, need some urgent need.
I have a stateless ejb webservice and I'm trying to set the transaction timeout for some of the methods. Right now my webservice transaction is timing out to the default of 30 secs. I've tried setting in the admin console the JTA transaction timeout option, didn't work (file a case with bea support #81233). And after days of researching and searching I came across that you can setup the weblogic webservice transaction-timeout thru the weblogic-webservices.xml deployment descriptor. Tried setting the transaction-timeout attribute to 120 secs. and that didn't work. Here is the snippet of the xml file.
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-webservices xmlns="http://www.bea.com/ns/weblogic/weblogic-webservices" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-webservices http://www.bea.com/ns/weblogic/weblogic-webservices/1.0/weblogic-webservices.xsd">
<webservice-description>
<webservice-description-name>com.starcomsoft.pp.system.jws.SystemWSImpl</webservice-description-name>
<webservice-type>JAXRPC</webservice-type>
<port-component>
<port-component-name>SystemWSSoapPort</port-component-name>
<service-endpoint-address>
<webservice-contextpath>starcomsoft_ws</webservice-contextpath>
<webservice-serviceuri>/SystemWSImpl</webservice-serviceuri>
</service-endpoint-address>
<transaction-timeout>120</transaction-timeout>
<reliability-config>
<inactivity-timeout>P0DT600S</inactivity-timeout>
</reliability-config>
</port-component>
</webservice-description>
</weblogic-webservice>
Does anybody have any clue to solve my urgent need.
Thanks in advance for your help or suggestion.Unhandled exception
Type=Segmentation error vmState=0x00040000
J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000033
Handler1=F144C588 Handler2=F1446A9C
Module=/app/oracle/product/Middleware/wlserver_10.3/server/native/aix/ppc/libmuxer.so
Module_base_address=D8457000
Target=2_40_20091214_049398 (AIX 5.3)
CPU=ppc (4 logical CPUs) (0x600000000 RAM)
----------- Stack Backtrace -----------
(0xD696E748 [libj9vm24.so+0x48748])
(0xD8383EDC [libjclscar_24.so+0x10edc])
(0xD8384514 [libjclscar_24.so+0x11514])
(0xD6967718 [libj9vm24.so+0x41718])
(0xD6967158 [libj9vm24.so+0x41158])
(0xD69640D0 [libj9vm24.so+0x3e0d0])
(0xD6932C9C [libj9vm24.so+0xcc9c])
(0xD69BBA18 [libj9prt24.so+0x3a18])
(0xD6932BB8 [libj9vm24.so+0xcbb8])
(0xD69A77CC [libj9thr24.so+0x27cc])
pthreadbody+0x118 (0xD010D784 [libpthreads.a+0x3784]) -
Lock timeout error trying to create a partition
I'm getting a lock timeout error attempting to partition a large BSEG table. I have done this before successfully on other tables but for some reason this keeps failing with the following error:
Could not execute 'ALTER TABLE "OURSCHEMA"."BSEG" PARTITION BY RANGE (GJAHR) (PARTITION 1 <= VALUES < 1999, PARTITION ...' in 2:30:35.927 hours . SAP DBTech JDBC: [131]: transaction rolled back by lock wait timeout: Lock timeout occurs while waiting TABLE_LOCK of mode EXCLUSIVE(TRANSACTION_ID=128, UPDATE_TRANSACTION_ID=2123074)
NOTE: We have SUSPENDED the replication of BSEG while this partition is happening.
Anybody experience this problem?
Thanks,
-PatrickHi,
Try partitoning the BSEG table from SLT using the t-code IUUC_REPL_CONTENT - Maintaining the replication settings.
Select the schema, select BSEG, go to 'Edit settings' and enter the script in the 'Partition Command' of BSED.
eg,: PARTITION BY HASH(GJAHR) PARTITIONS 5
Try replicating now from Data Prov.
Hope it works...
Regards,
Papil -
Transaction timeout when two system communicate by web service.
Currently, our application run under WLS 10, and exchange data with another system build on WLS 10 also by web service.
These two system both set global transaction timeout through Console: Server-->Configuration-->JTA-->Timeout Seconds, set number is 1800s.
Long time operation within one system is ok, never meet tracation timeout exception. But, when one system call another system via web service, always meet below exception(same operation run under wls 8.1 is ok):
15-02-2008@17:35:56 ERROR leave : [[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'] [CTLeaveWebService@PSA] [B2E_CTLeave.Get_Leave_Info] Exception Occured, Failure creating new instance of RowMapper, org.apache.beehive.controls.api.ControlException: RowToObjectMapper: SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 30 seconds
BEA1-067F39AED8C5E04484B3
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1419)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1331)
at weblogic.jdbc.wrapper.JTAConnection.getXAConn(JTAConnection.java:189)
at weblogic.jdbc.wrapper.JTAConnection.checkConnection(JTAConnection.java:64)
at weblogic.jdbc.wrapper.ResultSetMetaData.preInvocationHandler(ResultSetMetaData.java:37)
at weblogic.jdbc.wrapper.ResultSetMetaData_oracle_jdbc_driver_OracleResultSetMetaData.getColumnCount(Unknown Source)
at org.apache.beehive.controls.system.jdbc.RowToObjectMapper.<init>(RowToObjectMapper.java:63)
at sun.reflect.GeneratedConstructorAccessor136.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at org.apache.beehive.controls.system.jdbc.RowMapperFactory.getMapper(RowMapperFactory.java:160)
at org.apache.beehive.controls.system.jdbc.RowMapperFactory.getRowMapper(RowMapperFactory.java:85)
at org.apache.beehive.controls.system.jdbc.DefaultObjectResultSetMapper.arrayFromResultSet(DefaultObjectResultSetMapper.java:93)
at org.apache.beehive.controls.system.jdbc.DefaultObjectResultSetMapper.mapToResultType(DefaultObjectResultSetMapper.java:61)
at org.apache.beehive.controls.system.jdbc.JdbcControlImpl.execPreparedStatement(JdbcControlImpl.java:370)
at org.apache.beehive.controls.system.jdbc.JdbcControlImpl.invoke(JdbcControlImpl.java:228)
at com.psa.citos.rms.leave.services.resouces.StaffLeaveDBBean.getLeaveDetailsByLvEmpIdStDtEndDtStatusInArray(StaffLeaveDBBean.java:198)
at com.psa.citos.rms.leave.services.bizlogic.StaffLeaveServiceImpl.getLeaveDetailsByLvEmpIdStDtEndDt(StaffLeaveServiceImpl.java:276)
at com.psa.citos.rms.leave.services.bizlogic.StaffLeaveServiceBean.getLeaveDetailsByLvEmpIdStDtEndDt(StaffLeaveServiceBean.java:1112)
at com.psa.citos.rms.leave.services.bizlogic.LeaveServiceImpl.getLeaveDetailsByLvEmpIdStDtEndDt(LeaveServiceImpl.java:337)
at com.psa.citos.rms.leave.services.bizlogic.LeaveServiceBean.getLeaveDetailsByLvEmpIdStDtEndDt(LeaveServiceBean.java:596)
at com.psa.citos.rms.leave.facades.WebServiceFacadesImpl.getStaffLeaveInfoForRoster(WebServiceFacadesImpl.java:254)
at com.psa.citos.rms.leave.facades.WebServiceFacadesBean.getStaffLeaveInfoForRoster(WebServiceFacadesBean.java:250)
at com.psa.citos.rms.leave.webservice.CTLeaveWebService.getLeaveInfo(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at weblogic.wsee.component.pojo.JavaClassComponent.invoke(JavaClassComponent.java:99)
at weblogic.wsee.ws.dispatch.server.ComponentHandler.handleRequest(ComponentHandler.java:64)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:123)
at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:85)
at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:257)
at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3392)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
[java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 30 seconds
Data Sourse config:
URL: jdbc:oracle:thin:@xxxxxx:1521:xxxxxx
Driver Class Name: oracle.jdbc.xa.client.OracleXADataSource
Can help to advise what this exception cause and how to resolve?
thanks and best regards.
Edited by rendlut at 02/17/2008 7:29 PM
Edited by rendlut at 02/17/2008 7:38 PMr c wrote:
> Currently, our application run under WLS 10, and exchange data with another system build on WLS 10 also by web service.
> These two system both set global transaction timeout through Console: Server-->Configuration-->JTA-->Timeout Seconds, set number is 1800s.
>
> Long time operation within one system is ok, never meet tracation timeout exception. But, when one system call another system via web service, always meet below exception(same operation run under wls 8.1 is ok):
>
> 15-02-2008@17:35:56 ERROR leave : [[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'] [CTLeaveWebService@PSA] [B2E_CTLeave.Get_Leave_Info] Exception Occured, Failure creating new instance of RowMapper, org.apache.beehive.controls.api.ControlException: RowToObjectMapper: SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 30 seconds
> BEA1-067F39AED8C5E04484B3
> at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1419)
> at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1331)
> at weblogic.jdbc.wrapper.JTAConnection.getXAConn(JTAConnection.java:189)
> at weblogic.jdbc.wrapper.JTAConnection.checkConnection(JTAConnection.java:64)
> at weblogic.jdbc.wrapper.ResultSetMetaData.preInvocationHandler(ResultSetMetaData.java:37)
> at weblogic.jdbc.wrapper.ResultSetMetaData_oracle_jdbc_driver_OracleResultSetMetaData.getColumnCount(Unknown Source)
> at org.apache.beehive.controls.system.jdbc.RowToObjectMapper.<init>(RowToObjectMapper.java:63)
> at sun.reflect.GeneratedConstructorAccessor136.newInstance(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> at org.apache.beehive.controls.system.jdbc.RowMapperFactory.getMapper(RowMapperFactory.java:160)
> at org.apache.beehive.controls.system.jdbc.RowMapperFactory.getRowMapper(RowMapperFactory.java:85)
> at org.apache.beehive.controls.system.jdbc.DefaultObjectResultSetMapper.arrayFromResultSet(DefaultObjectResultSetMapper.java:93)
> at org.apache.beehive.controls.system.jdbc.DefaultObjectResultSetMapper.mapToResultType(DefaultObjectResultSetMapper.java:61)
> at org.apache.beehive.controls.system.jdbc.JdbcControlImpl.execPreparedStatement(JdbcControlImpl.java:370)
> at org.apache.beehive.controls.system.jdbc.JdbcControlImpl.invoke(JdbcControlImpl.java:228)
> at com.psa.citos.rms.leave.services.resouces.StaffLeaveDBBean.getLeaveDetailsByLvEmpIdStDtEndDtStatusInArray(StaffLeaveDBBean.java:198)
> at com.psa.citos.rms.leave.services.bizlogic.StaffLeaveServiceImpl.getLeaveDetailsByLvEmpIdStDtEndDt(StaffLeaveServiceImpl.java:276)
> at com.psa.citos.rms.leave.services.bizlogic.StaffLeaveServiceBean.getLeaveDetailsByLvEmpIdStDtEndDt(StaffLeaveServiceBean.java:1112)
> at com.psa.citos.rms.leave.services.bizlogic.LeaveServiceImpl.getLeaveDetailsByLvEmpIdStDtEndDt(LeaveServiceImpl.java:337)
> at com.psa.citos.rms.leave.services.bizlogic.LeaveServiceBean.getLeaveDetailsByLvEmpIdStDtEndDt(LeaveServiceBean.java:596)
> at com.psa.citos.rms.leave.facades.WebServiceFacadesImpl.getStaffLeaveInfoForRoster(WebServiceFacadesImpl.java:254)
> at com.psa.citos.rms.leave.facades.WebServiceFacadesBean.getStaffLeaveInfoForRoster(WebServiceFacadesBean.java:250)
> at com.psa.citos.rms.leave.webservice.CTLeaveWebService.getLeaveInfo(Unknown Source)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at weblogic.wsee.component.pojo.JavaClassComponent.invoke(JavaClassComponent.java:99)
> at weblogic.wsee.ws.dispatch.server.ComponentHandler.handleRequest(ComponentHandler.java:64)
> at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:123)
> at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:85)
> at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
> at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
> at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
> at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:257)
> at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:156)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
> at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
> at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
> at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
> at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3392)
> at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
> at weblogic.security.service.SecurityManager.runAs(Unknown Source)
> at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
> at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
> at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
> at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
> at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
> [java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 30 seconds
>
> Data Sourse config:
> URL: jdbc:oracle:thin:@xxxxxx:1521:xxxxxx
> Driver Class Name: oracle.jdbc.xa.client.OracleXADataSource
>
>
> Can help to advise what this exception cause and how to resolve?
>
> thanks and best regards.
>
> --
> Edited by rendlut at 02/17/2008 7:29 PM
>
> --
> Edited by rendlut at 02/17/2008 7:38 PM
In the console, you can set the JTA timeout to
something more appropriate for your needs than
the default 30 seconds.
Joe -
Full Deployment failing with Transaction timeout
Hi
I am trying to do a full deployment(ATG 10.0.2) and its failing with the same transaction timeout on all environments (local, dev, stage)
I have tried to reduce the maxThreads to 1 in DeploymentManager but still i get the same exception.
Incremental deployments seems to be running fine if i deploy anything, like category, products, skus.
Even the catalog feed runs and deploys fine.
I have a total of around 1500 products and 7000 skus.
In BCC screen i see it gives timeout while deploying skus
Error Deployment Failed 1051226:sku 2011-08-27 20:04:02.798
Message Detail:
CONTAINER:atg.deployment.DistributedDeploymentException; SOURCE:CONTAINER:atg.repository.RepositoryException; SOURCE:org.jboss.util.NestedSQLException: Transaction is not active: tx=TransactionImple < ac, BasicAction: ada0e22:4593:4e59847c:5e57e8 status: ActionStatus.ABORTING >; - nested throwable: (javax.resource.ResourceException: Transaction is not active: tx=TransactionImple < ac, BasicAction: ada0e22:4593:4e59847c:5e57e8 status: ActionStatus.ABORTING >) at atg.deployment.repository.RepositoryWorkerThread.processMarkerForReferenceUpdatePhase(RepositoryWorkerThread.java:346) at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:540) at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:307)
In the logs i see the following exceptions::
20:03:54,827 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id ada0e22:4593:4e59847c:5e57e8 invoked while multiple threads a
ctive within it.
20:03:54,827 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action ada0e22:4593:4e59847c:5e57e8 aborting with
1 threads active!
20:03:55,329 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TransactionReaper_18] - TransactionReaper::check timeout for TX ada0e22:4593:4e59847c:5e57e8 in st
ate CANCEL
20:03:55,831 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TransactionReaper_18] - TransactionReaper::check timeout for TX ada0e22:4593:4e59847c:5e57e8 in st
ate CANCEL_INTERRUPTED
20:03:55,831 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TransactionReaper_6] - TransactionReaper::check worker Thread[Thread-138,5,jboss] not responding t
o interrupt when cancelling TX ada0e22:4593:4e59847c:5e57e8 -- worker marked as zombie and TX scheduled for mark-as-rollback
20:03:55,831 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TransactionReaper_11] - TransactionReaper::check failed to mark TX ada0e22:4593:4e59847c:5e57e8 a
s rollback only
20:04:01,934 INFO [DeploymentManager] DEBUG RepositoryWorkerThread-1(Reference Update Phase) Rolling Back Current Transaction
20:04:02,021 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_40] - Abort called on already aborted atomic action ada0e22:4593:4e59847c:5e57e8
20:04:02,022 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TransactionReaper_13] - TransactionReaper::doCancellations worker Thread[Thread-138,5,jboss] misse
d interrupt when cancelling TX ada0e22:4593:4e59847c:5e57e8 -- exiting as zombie (zombie count decremented to 0)
20:04:02,023 INFO [DeploymentManager] DEBUG RepositoryWorkerThread-1(Reference Update Phase) Committing 237 markers, 1 failed markers
20:04:02,798 ERROR [DeploymentManager] item = repositoryMarker:mark876015 cause = CONTAINER:atg.deployment.DistributedDeploymentException; SOURCE:CONTAINER:atg.reposit
ory.RepositoryException; SOURCE:org.jboss.util.NestedSQLException: Transaction is not active: tx=TransactionImple < ac, BasicAction: ada0e22:4593:4e59847c:5e57e8 status
: ActionStatus.ABORTING >; - nested throwable: (javax.resource.ResourceException: Transaction is not active: tx=TransactionImple < ac, BasicAction: ada0e22:4593:4e59847
c:5e57e8 status: ActionStatus.ABORTING >)
at atg.deployment.repository.RepositoryWorkerThread.processMarkerForReferenceUpdatePhase(RepositoryWorkerThread.java:346)
at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:540)
at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:307)
message = Deployment Failed time = Sat Aug 27 20:04:02 MDT 2011 atg.deployment.DeploymentFailure@2be5134e
CAUGHT AT:
CONTAINER:atg.deployment.DistributedDeploymentException; SOURCE:CONTAINER:atg.repository.RepositoryException; SOURCE:org.jboss.util.NestedSQLException: Transaction is n
ot active: tx=TransactionImple < ac, BasicAction: ada0e22:4593:4e59847c:5e57e8 status: ActionStatus.ABORTING >; - nested throwable: (javax.resource.ResourceException: T
ransaction is not active: tx=TransactionImple < ac, BasicAction: ada0e22:4593:4e59847c:5e57e8 status: ActionStatus.ABORTING >)
at atg.deployment.repository.RepositoryWorkerThread.processMarkerForReferenceUpdatePhase(RepositoryWorkerThread.java:346)
20:04:02,992 INFO [DeploymentManager] DEBUG RepositoryWorkerThread-1(Reference Update Phase) Failure count was: 0. New failure count is: 1.
20:04:02,995 INFO [DeploymentManager] DEBUG RepositoryWorkerThread-1(Reference Update Phase) Rolling Back Current Transaction
20:04:02,995 INFO [DeploymentManager] DEBUG RepositoryWorkerThread-1(Reference Update Phase) Committing 0 markers, 0 failed markers
20:04:03,152 INFO [DeploymentManager] DEBUG RepositoryWorkerThread-1(Reference Update Phase) Exiting normally
20:04:03,153 ERROR [DeploymentManager] Unexpected error occurred. DeploymentWorkerThread terminated prematurely.
atg.deployment.DistributedDeploymentException: Exceeded allowable error count (0)
at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:652)
at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:307)
20:04:07,724 INFO [DeploymentServer] DEBUG 1500007:Production:atg.deployment.adapter.DistributedDeploymentAdapter.displayDeploymentFailures(DistributedDeploymentAdapte
r.java:2652) found 1 failure messages
20:04:07,747 INFO [DeploymentServer] DEBUG 1500007:Production:atg.deployment.adapter.DistributedDeploymentAdapter.displayDeploymentFailures(DistributedDeploymentAdapte
r.java:2683) adding failure message Deployment Failed with severity Error
20:04:11,211 INFO [DeploymentManager] DEBUG Main deployment thread: No waiting deployments to start
20:04:11,240 INFO [DeploymentServer] DEBUG 1500007:Production:atg.deployment.adapter.DistributedDeploymentAdapter.deploymentFailed(DistributedDeploymentAdapter.java:31
86) DeploymentListener.deploymentFailed called for deployment with ID: 1500007
20:04:11,240 INFO [DeploymentServer] DEBUG 1500007:Production:atg.deployment.adapter.DistributedDeploymentAdapter.deploymentFailed(DistributedDeploymentAdapter.java:31
94) DAFDeploymentID: 1500007 matches DeploymmentID: 1500007
20:04:11,240 INFO [DeploymentServer] DEBUG 1500007:Production:atg.deployment.adapter.DistributedDeploymentAdapter.deploymentFailed(DistributedDeploymentAdapter.java:31
98) DeploymentListener.deploymentFailed
20:04:11,241 INFO [DeploymentServer] DEBUG 1500007:Production:atg.deployment.adapter.DistributedDeploymentAdapter.displayDeploymentFailures(DistributedDeploymentAdapte
r.java:2652) found 1 failure messages
20:04:11,259 INFO [DeploymentServer] DEBUG 1500007:Production:atg.deployment.adapter.DistributedDeploymentAdapter.displayDeploymentFailures(DistributedDeploymentAdapte
r.java:2683) adding failure message Deployment Failed with severity Error
20:04:11,261 INFO [DeploymentServer] DEBUG 1500007:Production:atg.deployment.adapter.DistributedDeploymentAdapter.deployData(DistributedDeploymentAdapter.java:2197)
deployment failed
20:04:11,386 ERROR [DeploymentServer]
atg.deployment.common.DeploymentException: Deployment '1500007' to target 'Production' encountered a system level deployment error during data transfer.
at atg.deployment.common.ResourceUtil.exception(ResourceUtil.java:306)
at atg.deployment.adapter.DistributedDeploymentAdapter.deployData(DistributedDeploymentAdapter.java:2238)
at atg.deployment.adapter.DistributedDeploymentAdapter.transferData(DistributedDeploymentAdapter.java:305)
at atg.deployment.server.Deployment.run(Deployment.java:1688)I am using ATG10.0.2 with jboss-5.1-eap
I have tried increasing the timeout on jboss, but it only stops the timeout from happening, but the full deployment takes forever and takes more than 12 hours.
The catalog itself is too small and shouldnt be taking that much at all.
I just checked one thing:
I have a one to many relation with my sku and sale price(custom table) which has 11000 rows. If i delete the data in this table the deployment happens fine and takes about 30 mins.
The relationship it self seems correct.
this is on sku descriptor
<table name="my_sku_saleprice" type="multi" id-column-name="sku_id">
<property name="salePrices" column-name="sale_prices" data-type="set" component-item-type="salePrices" display-name-resource="salePrices"
writable="true" category-resource="categoryPresentation">
<attribute name="resourceBundle" value="atg.projects.store.StoreCatalogTemplateResources"/>
</property>
</table>
And this is the salePrices descriptor
<item-descriptor name="salePrices" display-name-resource="itemDescriptorSalePrices"
item-cache-size="100000" query-cache-size="100000">
<attribute name="resourceBundle" value="atg.projects.store.StoreCatalogTemplateResources"/>
<table name="my_sku_saleprices" type="primary" id-column-name="sale_prices">
<property name="salesPrice" data-type="double" column-name="sales_price" required="true" display-name-resource="salesPrice"/>
<property name="saleType" data-type="string" column-name="sale_type" required="true" display-name-resource="saleType"/>
<property name="startDate" data-type="Date" column-name="start_date" display-name-resource="startDate"/>
<property name="endDate" data-type="Date" column-name="end_date" display-name-resource="endDate"/>
</table>
</item-descriptor>
The only thing i m not able to understand is why its taking forever to get the full deployment.
Incremental deployment in catalog happens quickly, if i deploy any sku,product or anything.
Is it something to do with ATG or jboss?
Any pointers will help
Thanks
Maybe you are looking for
-
Windows 8.1 On-Screen Keyboard shows comma in numeric layout
Even changing my regional settings to use the full stop "." I still get the comma in the numeric layout of the On-Screen Keyboard. Changed the location/region to South Africa as well, still not helping. Is there any way to change this?
-
I have made a slideshow in FCPX and exported it as a quicktime movie. I then imported that into iDVD 7.1 and when i am testing, the menu and movie look great. Whe i burn the DVD the menu screen looks terrible. bith the image and the titles are very p
-
Hi, I just got the new MacBook Pro about 4 months ago for graduation. I used it for a little bit and it was fine and then I went out. Just a few hours later I had to use it again and the screen wouldn't come on. There was no power at all. So I took i
-
How do I re-install my Photoshop 9 on my repaired and upgraded computer, as the software says my installation quota is used?
-
S P R E A D type settings (created in FH, not editable in AI)
I am converting a batch of old maps from FreeHand to Illustrator, with spread type for the state names: C A L I F O R N I A In FreeHand, letter spacing can be spread out by dragging the right edge of the type box, or numerically by typing a