JTA Error
Hi All,
I'm trying to use JTA Custom Action Blocks in MII 12.1 and SQL Server 2005. MSSQLSERVER.jarmsbase.jarmsutil.jar as JDBC driver.
I have a data source up and running at Netweaver and a data server in MII as an alias to this data source (data server of type datasource and "jdbc/datasourcename")
When I try to insert just 1 row using JTA, everything goes right. If I try to insert 2 or more rows, I got this error:
[ERROR] [JTA_Command_MaterialInsert]Error invoking Transaction Command action: JTATransactionCommand - A SQL Command Exception occured against FactoryMIINW with the following command INSERT INTO UNIT_MEASURE (ID_UOM, DS_UOM, CD_ISO) VALUES ('ASA','ASA','ASA'). The message was: [Microsoft][SQLServer 2000 Driver for JDBC]Can't start a cloned connection while in manual transaction mode.
After some research I found a thread at Webdympro's forum telling me to add "selectMethod=cursor" to the connection string.
After doing this, the JTA works very well but all query templates that uses the MII Data Server (select statements for example) stop working and return this error:
[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter 1 (""): Data type 0x38 is unknown.
Any ideas?
Thank you all!
You have an XA heuristic hazard. You'll have to provide some more info
about your transactions for anyone to help you. I would suggest posting
in the transaction newsgroup.
-- Rob
Rajasekhar wrote:
I am seeing this error intermittently on my weblogic console. Any idea what this
means?
<Jan 24, 2003 10:05:32 AM EST> <Error> <JTA> <Transaction = Xid=4:9b0fc0ce803e1b
f8(2803248),Status=Committed,HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,nu
mRepliesOwedOthers=0,seconds since begin=0,seconds left=150,ServerResourceInfo[J
MS_WPE_NotDurable]=(state=committed,assigned=wpeserver),ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=committed,assigned=wpeserver),SCInfo[mydomain+myserver]=(state=committed))
completed heuristically:
null>
Similar Messages
-
Getting JTA Error Messages in MII Transaction
Hi ,
I am using a JTA action block to insert the data in a table. In case this insert statments throws any error (such as primary key violation or column length issue) I would like to display that error message to the user. Can any one know how can I get the database error messages? I have checked the properties of JTACommand action and I can see only 3 properties which are JTATransactionStartSource, SQLCommand and CommandDatasource
There is not property to display the error message
Any help on this much appreciated
Thanks in advance
ShajiHi Shaji,
Please refer below thread
http://forums.sdn.sap.com/thread.jspa?threadID=1952105
Regards,
Manoj Bilthare -
Hi,
I have J2EE application which runs on weblogic 10.1 & oracle 11g database. I am getting the below error.
####<Oct 21, 2011 9:53:38 AM EDT> <Error> <JTA> <skate> <server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1319205218046> <BEA-110412> <Xid=BEA1-00025F72C1C750A777B6(1743335989),Status=Committed,HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=30,XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=committed,assigned=server),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@1da2eb14,re-Registered = false),SCInfo[Infinys+server]=(state=committed)) completed heuristically: (weblogic.jdbc.wrapper.JTSXAResourceImpl, HeuristicHazard, (javax.transaction.xa.XAException: No connection associated with xid = BEA1-00025F72C1C750A777B6-7765626C6F6769632E6A6462632E777261707065722E4A545358415265736F75726365496D706C)) >
I have data source configuration which has Supports Global Trasactions & Emulate Two-phase Commit settings and used type 4 driver (oracle.jdbc.driver.OracleDriver) while configuring the connection pool in the weblogic.
I am not sure about the exact cause of this error. Can anyone help me in finding out the root cause of this issue?I think you're issue may actually be a memory issue and the Warning about the MBean attribute retrieval issue is simply a symptom of another issue and not your actual problem.
I would encourage a support case and reviewing the content available on:
My Oracle Support
http://support.oracle.com
Document ID 877172.1
Oracle WebLogic Server Core Server / JVM / Memory Issues Support Patterns - Investigating Out of Memory / Memory Leak Problems
IBM also has some tools for looking at memory usage and you may need to investigate those as well.
In one of my blog posts I link to IBM's tooling for java:
http://blogs.oracle.com/jamesbayer/2009/12/open_the_black_box_-oraclejr.html
http://www.ibm.com/developerworks/java/jdk/tools/index.html?S_TACT=105AGX02&S_CMP=HP -
Internal JTA transaction rollback errors
Hello,
I seem to be having an issue where WLS 9.1 is swallowing JTA errors. Our application is using container-managed transactions to perform some database and JMS work inside various MDBs. We are running in a cluster with two managed servers, and we are using the Microsoft SQL Server 2005 Beta 2 JDBC drivers. We have been running the application in development for quite a while and we thought it was working fine, with the exception of an occasional message that reaches its redelivery limit due to database locking issues. However, I was just digging around in our server logs for information related to a different problem and I noticed that the error message below is littered throughout our logs on a fairly regular basis. What does this error mean, and how can it be resolved? Are we losing data and/or JMS messages without knowing it?
Regards,
Sabrina
<Feb 6, 2006 8:46:50 AM EST> <Notice> <EJB> <BEA-010017> <Exception occurred during rollback of transaction Xid=BEA1-61E52279C065F462EB9B(12892320),Status=Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=3,seconds left=60,XAServerResourceInfo[WLStore_our_domain_our_filestore]=(ServerResourceInfo[WLStore_our_domain_our_filestore]=(state=new,assigned=none),xar=null,re-Registered = false),XAServerResourceInfo[OurXADataSource]=(ServerResourceInfo[OurXADataSource]=(state=rolledback,assigned=managed_server_2),xar=OurXADataSource,re-Registered = true),SCInfo[our_domain+managed_server_2]=(state=rolledback),SCInfo[our_domain+managed_server_1]=(state=rolledback),properties=({}),local properties=({weblogic.jdbc.jta.OurXADataSource=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=managed_server_2+ouripaddress:8002+our_domain+t3+, XAResources={SecondXADataSource, ThirdXADataSource},NonXAResources={})],CoordinatorURL=managed_server_1+ouripaddress:8001+our_domain+t3+): javax.transaction.SystemException: Heuristic hazard: (OurXADataSource, HeuristicHazard, (javax.transaction.xa.XAException: java.sql.SQLException: ROLLBACK:Status:0 msg:*** SQLJDBC_XA DTC_ERROR Context: xa_rollback, state=1, StatusCode:-4 (0xFFFFFFFC) ***))
at weblogic.transaction.internal.ServerTransactionImpl.internalRollback(ServerTransactionImpl.java:405)
at weblogic.transaction.internal.ServerTransactionImpl.rollback(ServerTransactionImpl.java:371)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:485)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:289)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:3786)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
.>Thanks so much for your response, Joe. Here is a detailed stack trace from one of these occurrences since I turned on the debug flags. If you'd still like me to post our config.xml, let me know - I thought I'd post this much to begin with since it's pretty lengthy.
Regards,
Sabrina
####<Feb 7, 2006 12:04:46 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331886688> <000000> <ResourceDescriptor[OurXADataSource]: getOrCreate gets rd: name = OurXADataSource
resourceType = 2
registered = true
scUrls = managed_server_2+ouripaddress:8002+our_domain+t3+
xar = OurXADataSource
healthy = true
lastAliveTimeMillis = 1139331886656
numActiveRequests = 0
>
####<Feb 7, 2006 12:04:46 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331886688> <000000> <BEA1-0ED82BD605F5F462EB9B: null: XA.start(rm=OurXADataSource, xar=OurXADataSource, flags=TMNOFLAGS)>
####<Feb 7, 2006 12:04:46 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331886688> <000000> <Resource 'OurXADataSource' setTransactionTimeout(120) not called. callSetTransactionTimeout=false, supportsSetTransactionTimeout=true>
####<Feb 7, 2006 12:04:46 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331886688> <000000> <startResourceUse, Number of active requests:3, last alive time:32 ms ago.>
####<Feb 7, 2006 12:04:46 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331886688> <000000> <BEA1-0ED82BD605F5F462EB9B: null: XA.start DONE (rm=OurXADataSource, xar=OurXADataSource>
####<Feb 7, 2006 12:04:46 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331886688> <000000> <endResourceUse, Number of active requests:0>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331888391> <000000> <BEA1-0ED82BD605F5F462EB9B: null: XA.end(rm=OurXADataSource, xar=OurXADataSource, flags=TMFAIL)>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331888391> <000000> <startResourceUse, Number of active requests:1, last alive time:0 ms ago.>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331888391> <000000> <XA.end DONE (rm=OurXADataSource, xar=OurXADataSource>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331888391> <000000> <endResourceUse, Number of active requests:0>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331888391> <000000> <BEA1-0ED82BD605F5F462EB9B: null: XAResource[OurXADataSource].rollback()>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331888391> <000000> <startResourceUse, Number of active requests:1, last alive time:0 ms ago.>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331888391> <000000> <BEA1-0ED82BD605F5F462EB9B: null: XAResource[OurXADataSource].rollback: FAILED , error code: XA_OK, message: java.sql.SQLException: ROLLBACK:Status:0 msg:*** SQLJDBC_XA DTC_ERROR Context: xa_rollback, state=1, StatusCode:-4 (0xFFFFFFFC) ***
javax.transaction.xa.XAException: java.sql.SQLException: ROLLBACK:Status:0 msg:*** SQLJDBC_XA DTC_ERROR Context: xa_rollback, state=1, StatusCode:-4 (0xFFFFFFFC) ***
at com.microsoft.sqlserver.jdbc.SQLServerXAResource.rollback(Ljavax.transaction.xa.Xid;)V(Unknown Source)
at weblogic.jdbc.jta.DataSource.rollback(DataSource.java:1005)
at weblogic.transaction.internal.XAServerResourceInfo.rollback(XAServerResourceInfo.java:1378)
at weblogic.transaction.internal.XAServerResourceInfo.rollback(XAServerResourceInfo.java:727)
at weblogic.transaction.internal.ServerSCInfo.startRollback(ServerSCInfo.java:740)
at weblogic.transaction.internal.ServerTransactionImpl.localRollback(ServerTransactionImpl.java:2013)
at weblogic.transaction.internal.ServerTransactionImpl.globalRollback(ServerTransactionImpl.java:2721)
at weblogic.transaction.internal.ServerTransactionImpl.internalRollback(ServerTransactionImpl.java:392)
at weblogic.transaction.internal.ServerTransactionImpl.rollback(ServerTransactionImpl.java:371)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:485)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:289)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:3786)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331888391> <000000> <endResourceUse, Number of active requests:0>
####<Feb 7, 2006 12:04:48 PM EST> <Error> <JTA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331888391> <BEA-110412> <Xid=BEA1-0ED82BD605F5F462EB9B(15099934),Status=Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=1,seconds left=60,activeThread=Thread[[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads],XAServerResourceInfo[WLStore_our_domain_our_filestore]=(ServerResourceInfo[WLStore_our_domain_our_filestore]=(state=new,assigned=none),xar=null,re-Registered = false),XAServerResourceInfo[OurXADataSource]=(ServerResourceInfo[OurXADataSource]=(state=rolledback,assigned=managed_server_2),xar=OurXADataSource,re-Registered = false),SCInfo[our_domain+managed_server_2]=(state=rolledback),SCInfo[our_domain+managed_server_1]=(state=rolledback),properties=({}),local properties=({weblogic.jdbc.jta.OurXADataSource=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=managed_server_2+ouripaddress:8002+our_domain+t3+, XAResources={ThirdXADataSource, SecondXADataSource},NonXAResources={})],CoordinatorURL=managed_server_1+ouripaddress:8001+our_domain+t3+) completed heuristically: (OurXADataSource, HeuristicHazard, (javax.transaction.xa.XAException: java.sql.SQLException: ROLLBACK:Status:0 msg:*** SQLJDBC_XA DTC_ERROR Context: xa_rollback, state=1, StatusCode:-4 (0xFFFFFFFC) ***)) >
####<Feb 7, 2006 12:04:48 PM EST> <Notice> <EJB> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331888453> <BEA-010017> <Exception occurred during rollback of transaction Xid=BEA1-0ED82BD605F5F462EB9B(15099934),Status=Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=1,seconds left=60,XAServerResourceInfo[WLStore_our_domain_our_filestore]=(ServerResourceInfo[WLStore_our_domain_our_filestore]=(state=new,assigned=none),xar=null,re-Registered = false),XAServerResourceInfo[OurXADataSource]=(ServerResourceInfo[OurXADataSource]=(state=rolledback,assigned=managed_server_2),xar=OurXADataSource,re-Registered = false),SCInfo[our_domain+managed_server_2]=(state=rolledback),SCInfo[our_domain+managed_server_1]=(state=rolledback),properties=({}),local properties=({weblogic.jdbc.jta.OurXADataSource=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=managed_server_2+ouripaddress:8002+our_domain+t3+, XAResources={ThirdXADataSource, SecondXADataSource},NonXAResources={})],CoordinatorURL=managed_server_1+ouripaddress:8001+our_domain+t3+): javax.transaction.SystemException: Heuristic hazard: (OurXADataSource, HeuristicHazard, (javax.transaction.xa.XAException: java.sql.SQLException: ROLLBACK:Status:0 msg:*** SQLJDBC_XA DTC_ERROR Context: xa_rollback, state=1, StatusCode:-4 (0xFFFFFFFC) ***))
at weblogic.transaction.internal.ServerTransactionImpl.internalRollback(ServerTransactionImpl.java:405)
at weblogic.transaction.internal.ServerTransactionImpl.rollback(ServerTransactionImpl.java:371)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:485)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:289)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:3786)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
.>
####<Feb 7, 2006 12:04:48 PM EST> <Info> <EJB> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331888516> <BEA-010213> <Message-Driven EJB: OurMDB's transaction was rolledback. The transaction details are: Xid=BEA1-0ED82BD605F5F462EB9B(15099934),Status=Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=1,seconds left=60,XAServerResourceInfo[WLStore_our_domain_our_filestore]=(ServerResourceInfo[WLStore_our_domain_our_filestore]=(state=new,assigned=none),xar=null,re-Registered = false),XAServerResourceInfo[OurXADataSource]=(ServerResourceInfo[OurXADataSource]=(state=rolledback,assigned=managed_server_2),xar=OurXADataSource,re-Registered = false),SCInfo[our_domain+managed_server_2]=(state=rolledback),SCInfo[our_domain+managed_server_1]=(state=rolledback),properties=({}),local properties=({weblogic.jdbc.jta.OurXADataSource=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=managed_server_2+ouripaddress:8002+our_domain+t3+, XAResources={ThirdXADataSource, SecondXADataSource},NonXAResources={})],CoordinatorURL=managed_server_1+ouripaddress:8001+our_domain+t3+).>
####<Feb 7, 2006 12:04:48 PM EST> <Error> <JDBC> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0EEC2BD605F5F462EB9B> <> <1139331888594> <BEA-001112> <Test "select count(*) from DUAL" set up for pool "OurXADataSource" failed with exception: "com.microsoft.sqlserver.jdbc.SQLServerException: Connection is Closed".>
####<Feb 7, 2006 12:04:48 PM EST> <Info> <JDBC> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0EEC2BD605F5F462EB9B> <> <1139331888594> <BEA-001128> <Connection for pool "OurXADataSource" closed.>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0EEC2BD605F5F462EB9B> <> <1139331888594> <000000> <java.lang.Exception: DEBUG: unregister
at weblogic.transaction.internal.TxDebug.debugStack(TxDebug.java:60)
at weblogic.transaction.internal.XAResourceDescriptor.unregister(XAResourceDescriptor.java:764)
at weblogic.transaction.internal.ResourceDescriptor.unregister(ResourceDescriptor.java:335)
at weblogic.transaction.internal.ResourceDescriptor.unregister(ResourceDescriptor.java:297)
at weblogic.transaction.internal.ServerTransactionManagerImpl.unregisterResource(ServerTransactionManagerImpl.java:684)
at weblogic.jdbc.common.internal.XAConnectionEnvFactory.refreshResource(XAConnectionEnvFactory.java:222)
at weblogic.jdbc.common.internal.XAConnectionEnvFactory.refreshResource(XAConnectionEnvFactory.java:173)
at weblogic.common.resourcepool.ResourcePoolImpl.refreshResource(ResourcePoolImpl.java:1554)
at weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1462)
at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1373)
at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1363)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:323)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:295)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:457)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:346)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:83)
at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1438)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1256)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:462)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
at ourpackage.OurDataSourceUtil.openConnection(OurDataSourceUtil.java:125)
at ourpackage.OurMDB.onMessage(OurMDB.java:171)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:289)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:3786)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
> -
Hi guys,
I have few questions on understanding of JMSState & JMSStore table. Firstly when
I am testing a JMS Based applications , whatever messages I am sending , I am
able to recieve it. But at the end of test the weblogic server continues with
some JTA error stating transactions being abandened.(Error trace attached below)
I am unable to understand as to what kind of transactions does it refers to.I
am not using any user managed transactions in the code. It is all container managed
transactions. I am sending the messages using JMS API to JMS Server.
When I refer to JMSStore table , I am having lot of rows with RECORDSTATE as '0'.
In case somebody can throw some light on this , it will be of great help.
Thanks,
Kumar
*****************************Error Trace **********************
<May 7, 2003 11:58:17 AM IST> <Error> <JTA> <Abandoning transaction after 88824
seconds
Xid=10:d9b7d987c4bc34e1(5858042),Status=Committing,numRepliesOwedMe=0,numReplies
OwedOthers=0,seconds since begin=88822,seconds left=0,ServerResourceInfo[weblogi
c.jdbc.jts.Connection]=(state=new,assigned=none),ServerResourceInfo[JMS_HNSJMSJD
BCStore]=(state=new,assigned=none),SCInfo[rdmdomain+rdmServer]=(state=active),SC
Info[jms+jmsServer]=(state=active),properties=({weblogic.jdbc=t3://139.85.249.78
:7011}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(Coordinato
rURL=rdmServer+139.85.249.78:7011+rdmdomain+, Resources={})],CoordinatorURL=rdmS
erver+139.85.249.78:7011+rdmdomain+)>
*****************************Error Trace **********************
Abandoned transactions likely have nothing to do with the
store per-se. Transactions are not propagated to the
database. JMS statistics will give you a much better
view of the current state of JMS. Look for
"pending" messages. "Pending" messages
are messages that are in a pending state, such as
uncommitted send, uncommitted receive, and timed-
delivery.
Note that it takes 24 hours for a transaction to get
abandoned. It may be helpful to check your transaction
statistics. Also, look for other error's in
your error log to look for a root cause.
Post to the jta newsgroup for info on abandoned transactions,
and related configurables. I think transactions are
abandoned if they are not committed within 24 hours
and they have timeout more than 24 hours,
of if the transaction monitor fails to reconnect to a JMS
server that failed mid-transaction for 24 hours.
Tom
Kumar Raman wrote:
> Hi guys,
>
> I have few questions on understanding of JMSState & JMSStore table. Firstly when
> I am testing a JMS Based applications , whatever messages I am sending , I am
> able to recieve it. But at the end of test the weblogic server continues with
> some JTA error stating transactions being abandened.(Error trace attached below)
> I am unable to understand as to what kind of transactions does it refers to.I
> am not using any user managed transactions in the code. It is all container managed
> transactions. I am sending the messages using JMS API to JMS Server.
> When I refer to JMSStore table , I am having lot of rows with RECORDSTATE as '0'.
>
> In case somebody can throw some light on this , it will be of great help.
>
> Thanks,
> Kumar
> *****************************Error Trace **********************
>
> <May 7, 2003 11:58:17 AM IST> <Error> <JTA> <Abandoning transaction after 88824
> seconds
> Xid=10:d9b7d987c4bc34e1(5858042),Status=Committing,numRepliesOwedMe=0,numReplies
> OwedOthers=0,seconds since begin=88822,seconds left=0,ServerResourceInfo[weblogi
> c.jdbc.jts.Connection]=(state=new,assigned=none),ServerResourceInfo[JMS_HNSJMSJD
> BCStore]=(state=new,assigned=none),SCInfo[rdmdomain+rdmServer]=(state=active),SC
> Info[jms+jmsServer]=(state=active),properties=({weblogic.jdbc=t3://139.85.249.78
> :7011}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(Coordinato
> rURL=rdmServer+139.85.249.78:7011+rdmdomain+, Resources={})],CoordinatorURL=rdmS
> erver+139.85.249.78:7011+rdmdomain+)>
>
> *****************************Error Trace **********************
>
-
Getting "JTA transaction is not present" error while updating db table.
Hi All,
In one of my BPEL process, In a loop, I am updating value of database column Flag from 0 to 1. It was working fine in dev environment, but failed in Prod with below errors, Can Any one suggest on this.
There is a system exception while performing the BPEL instance, the reason is "JTA transaction is not present or the transaction is not in active state. The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.. Please consult your administrator regarding this error. ". Please check the error log file for more infromation. Please try to use bpel fault handlers to catch the faults in your bpel process. If this is a system exception, please report this to your system administrator. Administrator could perform manual recovery of the instance from last non-idempotent activity or dehydration point.
OPMN logs:
<2010-05-05 01:56:49,395> <ERROR> <gemptp.collaxa.cube.engine> The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.
The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
Thanks in advance.I can envisage this happening only in a case where the update is taking a longer time than the value of JTA transaction timeout.
Is this happening for all BPEL instances or some of them get thru succesfully ?
Are you EVER updating that particular row of your table ( before/after) ?
-Shishir -
ORABPEL- 0803 JTA Rollback - ESB Error
My scenario is as follows - I have an ESB service that is inserting data into a target database. I am pasing data into the ESB from an ochestration BPEL process. When the database is down the ESB DBadaptor fails and the ESB returns the following error to the BPEL process invoke activity and the process hangs with the invoke highlighted in red. Wen I drill into the code I can see the following return element.
<fault>
ORABPEL-08034
JTA Rollback requested.
The current JTA transaction has been aborted due to rollback request received from partner invocation.
</fault>
Firstly this is causing me problems because it is not throwing an error in BPEL so my catch is not catching the error even though it is being passed in a fault element. (I would have expected it to get caught in the catch all branch of my process)
Secondly why is the root error from the DbAdaptor in the ESB not being sent back?
Is this a fundamental issue with ESB error handling?
I would be happy if the Fault above was thrown and the fault was caught in the catch all and my process would handle this but it just hangs when the invoke activity fails.Hi,
I applied the patch MLR6 and now has following scenario.
ESB is not even returning any fault when database adapter operation fails. I have been through the documentation available in Metalink and as per that the problem ESB Does Not Return Faults to BPEL (doc id 728491.1) should have been solved after applying MLR6.
This is referenced with bug no 5997936 which has been solved even before that in 10.1.3.4 Patchset for Oracle Application Server 10g Release 3.
Now I am confused. Please help. Following is the error log for reference
An unhandled exception has been thrown in the ESB system. The exception reported is: "org.collaxa.thirdparty.apache.wsif.WSIFException: esb:///ESB_Projects/TestESBServices_TestDBAdapters/PersonDetailsDBService1.wsdl [ PersonDetailsDBService1_ptt::insert(PersonDetailsCollection) ] - WSIF JCA Execute of operation 'insert' failed due to: DBWriteInteractionSpec Execute Failed Exception. insert failed. Descriptor name: [PersonDetailsDBService1.PersonDetails]. [Caused by: ORA-01400: cannot insert NULL into ("ESBADMIN"."PERSON_DETAILS"."LOGICAL_DELETE") ] ; nested exception is: ORABPEL-11616 DBWriteInteractionSpec Execute Failed Exception. insert failed. Descriptor name: [PersonDetailsDBService1.PersonDetails]. [Caused by: ORA-01400: cannot insert NULL into ("ESBADMIN"."PERSON_DETAILS"."LOGICAL_DELETE") ] Caused by Exception [TOPLINK-4002] (Oracle TopLink - 10g Release 3 (10.1.3.4.0) (Build 080602)): oracle.toplink.exceptions.DatabaseException Internal Exception: java.sql.BatchUpdateException: ORA-01400: cannot insert NULL into ("ESBADMIN"."PERSON_DETAILS"."LOGICAL_DELETE") Error Code: 1400. at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:644) at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:739) at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(WSIFInvoker.java:927) at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:842) at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:865) at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(OutboundAdapterService.java:231) at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(OutboundAdapterService.java:138) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(InitialEventDispatcher.java:411) at oracle.tip.esb.server.dispatch.InitialEventDispatch -
Error handling via CatchAll and JTA transaction error.
Hi
soa 10.1.3.5.0
I have created a test BPEL process where i am updating already completed Human task. I know it's wrong and i am doing it purposely to test error handling mechanism.
In the same BPEL I added a Catch all handler hoping that this will catch the error and will let me complete the process.
However BPEL is failing in the Catch All scope with lovely error: JTA transaction is not present or the transaction is not in active state.
Does anybody know how and why humantask update activity suddenly changes jta transaction state? Any thoughts of how i can catch the error in the situation i described and process it gracefully?
Thanks for your help!
piece from domain.log starting from the place where task service failing to update already completed human task.
<2013-10-10 17:01:00,520> <ERROR> <services.collaxa.cube.services> <*::*> Invalid action on workflow task.
<2013-10-10 17:01:00,520> <ERROR> <services.collaxa.cube.services> <*::*> Action OUTCOME_UPDATE on task 11d1def534ea1be0:65540537:141a4173a84:-7fa1 is not valid because of .
<2013-10-10 17:01:00,520> <ERROR> <services.collaxa.cube.services> <*::*> Contact oracle support if error is not fixable.
<2013-10-10 17:01:00,520> <ERROR> <services.collaxa.cube.services> <*::*>
<2013-10-10 17:01:00,520> <ERROR> <services.collaxa.cube.services> <*::*> at oracle.bpel.services.workflow.task.impl.TaskService.performPreActionValidation(TaskService.java:3600)
<2013-10-10 17:01:00,520> <ERROR> <services.collaxa.cube.services> <*::*> at oracle.bpel.services.workflow.task.impl.TaskService.performPreActionValidation(TaskService.java:3557)
<2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*> at oracle.bpel.services.workflow.task.impl.TaskService.updateTaskOutcomeAndEvaluateRoutingSlip(TaskService.java:1139)
<2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*> at oracle.bpel.services.workflow.task.impl.TaskService.updateTaskOutcome(TaskService.java:1006)
<2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*> at oracle.bpel.services.workflow.task.impl.TaskService.updateTaskOutcome(TaskService.java:985)
<2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*> at oracle.bpel.services.workflow.task.ejb.TaskServiceBean.updateTaskOutcome(TaskServiceBean.java:409)
<2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
<2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
<2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
<2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*> at java.lang.reflect.Method.invoke(Method.java:597)
<2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
<2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
<2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
<2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
<2013-10-10 17:01:00,522> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
<2013-10-10 17:01:00,522> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ThreadState.runAs(ThreadState.java:705)
<2013-10-10 17:01:00,522> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
<2013-10-10 17:01:00,522> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
<2013-10-10 17:01:00,522> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
<2013-10-10 17:01:00,522> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
<2013-10-10 17:01:00,522> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
<2013-10-10 17:01:00,522> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
<2013-10-10 17:01:00,522> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
<2013-10-10 17:01:00,522> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
<2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*> at TaskServiceBean_LocalProxy_68d4144.updateTaskOutcome(Unknown Source)
<2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*> at oracle.bpel.services.workflow.task.client.TaskServiceLocalClient.updateTaskOutcome(TaskServiceLocalClient.java:678)
<2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*> at oracle.bpel.services.workflow.task.impl.TaskServiceWSIF.updateTaskOutcome(TaskServiceWSIF.java:580)
<2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
<2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
<2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
<2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*> at java.lang.reflect.Method.invoke(Method.java:597)
<2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*> at com.collaxa.cube.ws.wsif.providers.java.WSIFOperation_Java.executeRequestResponseOperation(WSIFOperation_Java.java:1019)
<2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*> at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:480)
<2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*> at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:538)
<2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*> at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:286)
<2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*> at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:832)
<2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*> at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:413)
<2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*> at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:200)
<2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*> at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:4326)
<2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*> at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1839)
<2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*> at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:77)
<2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*> at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:240)
<2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*> at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:345)
<2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*> at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:6460)
<2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*> at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:2267)
<2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*> at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:185)
<2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*> at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:156)
<2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
<2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
<2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
<2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*> at java.lang.reflect.Method.invoke(Method.java:597)
<2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
<2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
<2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
<2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
<2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
<2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ThreadState.runAs(ThreadState.java:705)
<2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
<2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
<2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
<2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
<2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
<2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
<2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
<2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
<2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> at ActivityManagerBean_LocalProxy_4bin6i8.expireActivity(Unknown Source)
<2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> at com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessageHandler.handle(ExpirationMessageHandler.java:43)
<2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:150)
<2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:58)
<2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
<2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
<2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> at java.lang.Thread.run(Thread.java:662)
<2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> Caused by: ORABPEL-30036
<2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*>
<2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> Invalid action on workflow task.
<2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> Action OUTCOME_UPDATE on task 11d1def534ea1be0:65540537:141a4173a84:-7fa1 is not valid because of The task has been completed..
<2013-10-10 17:01:00,527> <ERROR> <services.collaxa.cube.services> <*::*> Contact oracle support if error is not fixable.
<2013-10-10 17:01:00,527> <ERROR> <services.collaxa.cube.services> <*::*>
<2013-10-10 17:01:00,527> <ERROR> <services.collaxa.cube.services> <*::*> at oracle.bpel.services.workflow.task.impl.TaskService.performPreActionValidation(TaskService.java:3592)
<2013-10-10 17:01:00,527> <ERROR> <services.collaxa.cube.services> <*::*> ... 71 more
<2013-10-10 17:01:00,562> <ERROR> <services.collaxa.cube.engine> The execution of this instance "390003" for process "MY_BPEL_PROCESS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.
<2013-10-10 17:01:00,571> <WARN> <services.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "activity manager": Failed due to unhandled bpel fault.
<2013-10-10 17:01:00,584> <ERROR> <services.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> failed to handle message
ORABPEL-02182
JTA transaction is not present or the transaction is not in active state.
The current JTA transaction is not present or it is not in active state when processing activity or instance "390,003". The reason is The execution of this instance "390003" for process "MY_BPEL_PROCESS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
Please consult your administrator regarding this error.
at com.collaxa.cube.engine.CubeEngine.store(CubeEngine.java:6176)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:6482)
at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:2267)
at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:185)
at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:156)
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.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
at com.evermind.server.ThreadState.runAs(ThreadState.java:705)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
at ActivityManagerBean_LocalProxy_4bin6i8.expireActivity(Unknown Source)
at com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessageHandler.handle(ExpirationMessageHandler.java:43)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:150)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:58)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
<2013-10-10 17:01:00,585> <ERROR> <services.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> Not fatal connection error ... not retrying: class com.collaxa.cube.engine.UnhandledFaultException: Failed due to unhandled bpel fault.
<2013-10-10 17:01:00,593> <ERROR> <services.collaxa.cube.engine.dispatch> <BaseDispatchTask::run> 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.instance.ExpirationMessage"; the exception is: JTA transaction is not present or the transaction is not in active state.
The current JTA transaction is not present or it is not in active state when processing activity or instance "390,003". The reason is The execution of this instance "390003" for process "MY_BPEL_PROCESS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
Please consult your administrator regarding this error.
ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessage"; the exception is: JTA transaction is not present or the transaction is not in active state.
The current JTA transaction is not present or it is not in active state when processing activity or instance "390,003". The reason is The execution of this instance "390003" for process "MY_BPEL_PROCESS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
Please consult your administrator regarding this error.
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:226)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:58)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)If you look at the error, it suggests that the action you are performing is invalid.That is you cannot update human task which has been already completed. Thats why you are getting that "JTA transaction not active error". Since your human task has already been completed, it is not able to update it again.
<2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> Caused by: ORABPEL-30036
<2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*>
<2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> Invalid action on workflow task.
<2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> Action OUTCOME_UPDATE on task 11d1def534ea1be0:65540537:141a4173a84:-7fa1 is not valid because of The task has been completed..
<2013-10-10 17:01:00,527> <ERROR> <services.collaxa.cube.services> <*::*> Contact oracle support if error is not fixable.
<2013-10-10 17:01:00,527> <ERROR> <services.collaxa.cube.services> <*::*>
May be you can try some other usecase ? Also could you let me know whether you are getting this error in logs only or in your composite instance as well. I mean whether the instance gets successfully terminated or completed ??
Regards,
Karan -
Error while comitting a transaction in oSB. The following is the error stack
Error while comitting a transaction in OSB. The following is the error stack
<Apr 20, 2015 12:00:15 AM MDT> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-1AE41F1CAE45F2B146FD(296700848),Status=Rolled back. [Reason=Unknown],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=2,seconds left=120,XAServerResourceInfo[WLStore_SOA_PRDKS_DOMAIN_FileStore_SOA_MS2]=(ServerResourceInfo[WLStore_SOA_PRDKS_DOMAIN_FileStore_SOA_MS2]=(state=new,assigned=none),xar=null,re-Registered = false),XAServerResourceInfo[WLStore_OSB_PRDKS_DOMAIN_FileStore_auto_1]=(ServerResourceInfo[WLStore_OSB_PRDKS_DOMAIN_FileStore_auto_1]=(state=rolledback,assigned=OSB_MS1),xar=WLStore_OSB_PRDKS_DOMAIN_FileStore_auto_11603460297,re-Registered = false),XAServerResourceInfo[weblogic.jdbc.jta.DataSource]=(ServerResourceInfo[weblogic.jdbc.jta.DataSource]=(state=ended,assigned=none),xar=CMSDS,re-Registered = false),SCInfo[OSB_PRDKS_DOMAIN+OSB_MS1]=(state=rolledback),SCInfo[SOA_PRDKS_DOMAIN+SOA_MS2]=(state=pre-prepared),properties=({}),local properties=({weblogic.jdbc.jta.CMSDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=OSB_MS1+soaprd-vip-osb-ms1.cos.is.keysight.com:8001+OSB_PRDKS_DOMAIN+t3+, XAResources={eis/wls/Queue, WEDB_EVEREST_OSB_PRDKS_DOMAIN, XREFDS_OSB_PRDKS_DOMAIN, eis/activemq/Queue, CustomSchemaDS_OSB_PRDKS_DOMAIN, MobileApps_CIA_DS1_OSB_PRDKS_DOMAIN, eis/tibjmsDirect/Queue, eis/jbossmq/Queue, eis/Apps/Apps, MobileApps_AOS_MDS_OSB_PRDKS_DOMAIN, MobileApps_AOS_DRDS_OSB_PRDKS_DOMAIN, WSATGatewayRM_OSB_MS1_OSB_PRDKS_DOMAIN, eis/webspheremq/Queue, eis/AQ/aqSample, SBLPROD_OSB_PRDKS_DOMAIN, wlsbjmsrpDataSource_OSB_PRDKS_DOMAIN, eis/aqjms/Queue, CMSDS_OSB_PRDKS_DOMAIN, WLStore_OSB_PRDKS_DOMAIN_WseeFileStore_auto_1, FAP_OSB_PRDKS_DOMAIN, eis/sunmq/Queue, eis/pramati/Queue, FMWAPPDS_OSB_PRDKS_DOMAIN, weblogic.jdbc.jta.DataSource, GSDC_OSB_PRDKS_DOMAIN, eis/tibjms/Topic, eis/fioranomq/Topic, WLStore_OSB_PRDKS_DOMAIN_FileStore_MS1, PresidioOracleAppsDS_OSB_PRDKS_DOMAIN, GSDCDS_OSB_PRDKS_DOMAIN, eis/aqjms/Topic, CustOutDS_OSB_PRDKS_DOMAIN, OFMW/Logging/BAM, MobileAppsDS_OSB_PRDKS_DOMAIN, FIDDS_OSB_PRDKS_DOMAIN, WLStore_OSB_PRDKS_DOMAIN__WLS_OSB_MS1, HRMSDS_OSB_PRDKS_DOMAIN, WEDB_OSB_PRDKS_DOMAIN, OracleAppsDS_OSB_PRDKS_DOMAIN, eis/wls/Topic, eis/tibjms/Queue, eis/tibjmsDirect/Topic, IntrastatDS_OSB_PRDKS_DOMAIN, MobileApps_AOS_COSDS_OSB_PRDKS_DOMAIN, MobileApps_CIA_DS2_OSB_PRDKS_DOMAIN, EVEREST_WEDB_OSB_PRDKS_DOMAIN, WLStore_OSB_PRDKS_DOMAIN_FileStore_auto_1, Everest_OSB_PRDKS_DOMAIN},NonXAResources={})],CoordinatorURL=SOA_MS2+soaprd-vip-soa-ms2.cos.is.keysight.com:8002+SOA_PRDKS_DOMAIN+t3+): javax.transaction.SystemException: Lost connection to server while commit was in progress, ignoring because initiating server is not coordinating server. Remote Exception received=weblogic.rjvm.PeerGoneException: ; nested exception is:
java.rmi.UnmarshalException: Incoming message header or abbreviation processing failed ; nested exception is:
java.io.InvalidClassException: oracle.jdbc.xa.OracleXAException; local class incompatible: stream classdesc serialVersionUID = -2542408691177300269, local class serialVersionUID = -4551795881821760665
at weblogic.transaction.internal.TransactionImpl.commit(TransactionImpl.java:376)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:237)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:224)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:552)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:423)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:325)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)Hi,
Have you tried Cancelling the release before adding the version?
Select the active version of the IDOC Segment and cancel its release first. Only then you will be able to add a version.
Please let me know if it worked!
Vijay -
Error while deploying a war file in Oracle Weblogic 10gr3 server
Hi
I am trying to deploy a web application which uses Hibernate 3 in Oracle weblogic 10gr3.But I am getting following exception.The same application gets deployed in tomcat without any problem.
urce [WEB-INF/servicesContext.xml]: Cannot resolve reference to bean 'genericDao' while setting bean property 'genericDao'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'genericDao' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'saasHibernateSessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'saasHibernateSessionFactory' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Errors in named queries: Tenant.byUserName, slaUsageOfTenant.bySlaCriterion, ServiceUsage.byCriterion, SLA.getSlaList, ServiceUsage.byTenantId.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'autoMeteringInterceptor' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'validator' while setting bean property 'validator'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'validator' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'tenant.tenantService' while setting bean property 'tenantService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'tenant.tenantService' defined in ServletContext resource [WEB-INF/servicesContext.xml]: Cannot resolve reference to bean 'genericDao' while setting bean property 'genericDao'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'genericDao' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'saasHibernateSessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'saasHibernateSessionFactory' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Errors in named queries: Tenant.byUserName, slaUsageOfTenant.bySlaCriterion, ServiceUsage.byCriterion, SLA.getSlaList, ServiceUsage.byTenantId
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:256)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:128)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:950)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:740)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:417)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:140)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:156)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:273)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:346)
at org.springframework.web.context.support.AbstractRefreshableWebApplicationContext.refresh(AbstractRefreshableWebApplicationContext.java:156)
at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:246)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:184)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:49)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:465)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:175)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1784)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'validator' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'tenant.tenantService' while setting bean property 'tenantService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'tenant.tenantService' defined in ServletContext resource [WEB-INF/servicesContext.xml]: Cannot resolve reference to bean 'genericDao' while setting bean property 'genericDao'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'genericDao' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'saasHibernateSessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'saasHibernateSessionFactory' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Errors in named queries: Tenant.byUserName, slaUsageOfTenant.bySlaCriterion, ServiceUsage.byCriterion, SLA.getSlaList, ServiceUsage.byTenantId
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:256)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:128)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:950)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:740)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:417)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:140)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:156)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:248)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:128)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:950)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:740)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:417)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:140)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:156)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:273)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:346)
at org.springframework.web.context.support.AbstractRefreshableWebApplicationContext.refresh(AbstractRefreshableWebApplicationContext.java:156)
at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:246)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:184)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:49)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:465)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:175)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1784)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Initially this application was giving me absolute path related errors.But when I made changes to applicationContext.xml as follows,giviing absolute path for Hibernate mapping files
<property name="mappingDirectoryLocations">
<list>
*<value>file:D:\saas-mappings</value>*
</list>
</property>
I have extrached all the *.hbm.xml file to above location that is D:\saas-mappings.But now the application is giving me above mentioned error.The error says that it is related to Named queries.I am pasting the contents of a sample *.hbm.xml file having named query as a sample
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<hibernate-mapping package="com.psl.saas.domain">
<class name="TenantSlaUsage" table="tenantslausage_v2">
<id name="tenantId" column="tenantId">
</id>
<property name="maxValue">
<column name="maxValue"></column>
</property>
<property name="thresholdValue">
<column name="thresholdValue"></column>
</property>
<property name="slaType" column="slaType" type="com.psl.saas.dataservice.SaasEnumSlaType"/>
<many-to-one name="slaCriterion" class="SLACriterion" column="slaCriterionName" lazy="false" unique="true" />
<property name="usageCount">
<column name="usageCount"></column>
</property>
</class>
*<query name="slaUsageOfTenant.bySlaCriterion">
<![CDATA[from com.psl.saas.domain.TenantSlaUsage where tenantId=:tenantId and slaCriterionName=:slaCriterionName]]>
</query>*
</hibernate-mapping>
Any help on this will be greatly appreciated
Thanks in Advance
-Sameer GijareHi,
For a tutorial with source on how to create and deploy a simple quickstart JEE5 JPA enterprise 3-tier application on your Oracle WebLogic 10.3 server - see the following example that uses the EclipseLink JPA provider. You should be able to transition all of your mapping information (the @ManyToOne and table/column overrides and named queries for example) using either JPA via entity annotations or native extensions if you do not want to implement EJB3.
see...
http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial
We also have a similar version for Tomcat 6 except the JPA entity beans run outside a container-managed JTA transaction on the web container - for reference.
http://wiki.eclipse.org/EclipseLink/Examples/JPA/Tomcat_Web_Tutorial
thank you
/michael
www.eclipselink.org -
Error while calling ejb service call from BPM service
Hi,
We are using the Oracle 11.1.1.5.0
We are calling ejb service call from BPM service to update the data to Oracle database.
We are getting the below error when we executing the ejb service call from BPM Service.
<Error> <EJB> <BEA-010026> <Exception occurred du
ring commit of transaction Name=[EJB oracle.bpm.bpmn.engine.ejb.impl.BPMNDeliver
yBean.handleCallback(java.lang.String,java.lang.String,java.lang.String,int,bool
ean)],Xid=BEA1-45B91984D57960994897(30845116),Status=Rolled back. [Reason=javax.
transaction.xa.XAException: JDBC driver does not support XA, hence cannot be a p
articipant in two-phase commit. To force this participation, set the GlobalTrans
actionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhas
eCommit for the Data Source = EBSConnection],numRepliesOwedMe=0,numRepliesOwedOt
hers=0,seconds since begin=1,seconds left=60,XAServerResourceInfo[SOADataSource_
base_domain]=(ServerResourceInfo[SOADataSource_base_domain]=(state=rolledback,as
signed=soa_server1),xar=SOADataSource,re-Registered = false),XAServerResourceInf
o[ArCnTaskForms@EBSConnection@EBSConnection_base_domain]=(ServerResourceInfo[ArC
nTaskForms@EBSConnection@EBSConnection_base_domain]=(state=rolledback,assigned=s
oa_server1),xar=weblogic.jdbc.wrapper.JTSEmulateXAResourceImpl@fa5476,re-Registe
red = false),SCInfo[base_domain+soa_server1]=(state=rolledback),properties=({web
logic.jdbc.remote.EBSConnection=t3://192.168.10.114:8001, weblogic.transaction.n
ame=[EJB oracle.bpm.bpmn.engine.ejb.impl.BPMNDeliveryBean.handleCallback(java.la
ng.String,java.lang.String,java.lang.String,int,boolean)]}),local properties=({w
eblogic.jdbc.jta.SOADataSource=[ No XAConnection is attached to this TxInfo ]}),
OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=soa
server1+192.168.10.114:8001+basedomain+t3+, XAResources={eis/tibjms/Queue, eis
/activemq/Queue, WLStore_base_domain_BPMJMSFileStore, WLStore_base_domain__WLS_s
oa_server1, eis/fioranomq/Topic, eis/jbossmq/Queue, eis/Apps/Apps, eis/websphere
mq/Queue, eis/AQ/aqSample, WLStore_base_domain_SOAJMSFileStore, eis/aqjms/Queue,
WSATGatewayRM_soa_server1_base_domain, eis/sunmq/Queue, eis/pramati/Queue, SSCo
nnectionDS_base_domain, eis/tibjms/Topic, eis/tibjmsDirect/Queue, eis/wls/Queue,
eis/tibjmsDirect/Topic, EDNDataSource_base_domain, eis/wls/Topic, eis/aqjms/Top
ic, RL3TST_base_domain, ArCnTaskForms@EBSConnection@EBSConnection_base_domain, S
OADataSource_base_domain, WLStore_base_domain_UMSJMSFileStore_auto_2},NonXAResou
rces={})],CoordinatorURL=soa_server1+192.168.10.114:8001+base_domain+t3+): weblo
gic.transaction.RollbackException: Could not prepare resource 'ArCnTaskForms@EBS
Connection@EBSConnection_base_domain
JDBC driver does not support XA, hence cannot be a participant in two-phase comm
it. To force this participation, set the GlobalTransactionsProtocol attribute to
LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source
= EBSConnection
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(
TransactionImpl.java:1881)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(Se
rverTransactionImpl.java:345)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTran
sactionImpl.java:239)
at weblogic.ejb.container.internal.BaseLocalObject.postInvoke1(BaseLocal
Object.java:622)
at weblogic.ejb.container.internal.BaseLocalObject.__WL_postInvokeTxRetr
y(BaseLocalObject.java:455)
at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(Sess
ionLocalMethodInvoker.java:52)
at oracle.bpm.bpmn.engine.ejb.impl.BPMNDeliveryBean_of8dk6_ICubeDelivery
LocalBeanImpl.handleCallback(Unknown Source)
at com.collaxa.cube.engine.dispatch.message.instance.CallbackDeliveryMes
sageHandler.handle(CallbackDeliveryMessageHandler.java:47)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(Dispatc
hHelper.java:140)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatc
hTask.java:88)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTas
k.java:64)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: javax.transaction.xa.XAException: JDBC driver does not support XA, he
nce cannot be a participant in two-phase commit. To force this participation, se
t the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended)
or EmulateTwoPhaseCommit for the Data Source = EBSConnection
at weblogic.jdbc.wrapper.JTSXAResourceImpl.prepare(JTSXAResourceImpl.jav
a:83)
at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerRe
sourceInfo.java:1327)
at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerRe
sourceInfo.java:513)
at weblogic.transaction.internal.ServerSCInfo$1.run(ServerSCInfo.java:36
8)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
gWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
.>
<12 Oct, 2012 12:34:40 PM IST> <Error> <oracle.soa.bpel.engine.dispatch> <BEA-00
0000> <failed to handle message
javax.transaction.xa.XAException: JDBC driver does not support XA, hence cannot
be a participant in two-phase commit. To force this participation, set the Globa
lTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateT
woPhaseCommit for the Data Source = EBSConnection
at weblogic.jdbc.wrapper.JTSXAResourceImpl.prepare(JTSXAResourceImpl.jav
a:83)
at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerRe
sourceInfo.java:1327)
at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerRe
sourceInfo.java:513)
at weblogic.transaction.internal.ServerSCInfo$1.run(ServerSCInfo.java:36
8)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
gWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
<12 Oct, 2012 12:34:40 PM IST> <Error> <oracle.soa.bpel.engine.dispatch> <BEA-00
0000> <Failed to handle dispatch message ... exception ORABPEL-05002
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.
message.instance.CallbackDeliveryMessage"; the reported exception is: Error comm
itting transaction:; nested exception is: javax.transaction.xa.XAException: JDBC
driver does not support XA, hence cannot be a participant in two-phase commit.
To force this participation, set the GlobalTransactionsProtocol attribute to Log
gingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = EB
SConnection
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
ORABPEL-05002
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.
message.instance.CallbackDeliveryMessage"; the reported exception is: Error comm
itting transaction:; nested exception is: javax.transaction.xa.XAException: JDBC
driver does not support XA, hence cannot be a participant in two-phase commit.
To force this participation, set the GlobalTransactionsProtocol attribute to Log
gingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = EB
SConnection
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(Dispatc
hHelper.java:207)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatc
hTask.java:88)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTas
k.java:64)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908)
at java.lang.Thread.run(Thread.java:662)
>
Could any body help on this issue.It is little bit urgent for us to resolve.
Thanks in advance.Thanks Sudipto Desmukh,
The link is helpful me to resolve this issue.
Thanks,
Narasimha E -
How to use jta in toplink and stateless session bean EJB 3.0?
I have an application with techologies jsf,stateless session bean, adf, toplink
generated by toplink workbench.
In web side ı want to use two methods in stateless session bean which are updated
different tables. I call these methods in my page backing bean.
I also want to JTA in web side. My first methods is done correctly, but second method has an error. I wanto to rollback all transaction.
How can ı do that? with using JTA in Toplink...Yuichi
Did you manage to solve this? I'm doing something similar and seeing the same problem, although they're up to 7.3 SP7.
Any help greatly appreciated.
Lewis -
Error while deploying a .war file
Hi,
I have a one Servlet class, which references two more classes for database
connection. After creating a .war file, I am trying to deploy it on iAS, and I
get the following error:
Failed to deploy web application "MBSServlet". Jar file: /var/tmp/jar61304.tmp
is missing its standard xml descriptor located at WEB-INF/web.xml
I don't know anything about /var/tmp/jar61304.tmp, I don't know where is it picking it up from. And my web.xml is as follows:
<?xml version="1.0" standalone='yes'?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN" " " target="_new">http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
<web-app>
<servlet>
<servlet-name>MBSServlet</servlet-name>
<servlet-class>MBSServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>MBSServlet</servlet-name>
<url-pattern>/MBSServlet</url-pattern>
</servlet-mapping>
</web-app>
Any help!!
thanks!!
ShaluHi,
For a tutorial with source on how to create and deploy a simple quickstart JEE5 JPA enterprise 3-tier application on your Oracle WebLogic 10.3 server - see the following example that uses the EclipseLink JPA provider. You should be able to transition all of your mapping information (the @ManyToOne and table/column overrides and named queries for example) using either JPA via entity annotations or native extensions if you do not want to implement EJB3.
see...
http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial
We also have a similar version for Tomcat 6 except the JPA entity beans run outside a container-managed JTA transaction on the web container - for reference.
http://wiki.eclipse.org/EclipseLink/Examples/JPA/Tomcat_Web_Tutorial
thank you
/michael
www.eclipselink.org -
Error while configuring kodo to lookup a datasource
We had a working application using EEPersistenceManagerFactory
I changed the kodo.properties to lookup a non XA JDBC datasource.
After that the application is working fine (it creates
,updates,deletes,finds record in the DB)
but SystemOut.log has the following error for every operation
We are using Kodo 2.5.0, Websphere 5.0 and Oracle 8
How can we avoid getting this error ?.
We tried to find any property on the Websphere datasource which can be
altered to avoid this error but no luck.
Thanks
Paresh
[10/7/03 15:30:45:467 IST] 3d8b2d1a MCWrapper E J2CA0081E: Method
destroy failed while trying to execute method destroy on ManagedConnection
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl@437f6d23 from resource
<null>. Caught exception: com.ibm.ws.exception.WsException: DSRA0080E: An
exception was received by the Data Store Adapter. See original exception
message: Cannot call 'cleanup' on a ManagedConnection while it is still in
a transaction..
at
com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.<init>(DataStoreAdapterException.java:222)
at
com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.<init>(DataStoreAdapterException.java:172)
at
com.ibm.ws.rsadapter.AdapterUtil.createDataStoreAdapterException(AdapterUtil.java:182)
at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupTransactions(WSRdbManagedConnectionImpl.java:1826)
at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.destroy(WSRdbManagedConnectionImpl.java:1389)
at com.ibm.ejs.j2c.MCWrapper.destroy(MCWrapper.java:1032)
at
com.ibm.ejs.j2c.poolmanager.FreePool.returnToFreePool(FreePool.java:259)
at com.ibm.ejs.j2c.poolmanager.PoolManager.release(PoolManager.java:777)
at com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.java:1304)
at
com.ibm.ejs.j2c.ConnectionEventListener.connectionClosed(ConnectionEventListener.java:195)
at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.processConnectionClosedEvent(WSRdbManagedConnectionImpl.java:843)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.closeWrapper(WSJdbcConnection.java:569)
at com.ibm.ws.rsadapter.jdbc.WSJdbcObject.close(WSJdbcObject.java:132)
at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.close(SQLExecutionManagerImpl.java:814)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.release(JDBCStoreManager.java(Inlined
Compiled Code))
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.load(JDBCStoreManager.java(Compiled
Code))
at
com.solarmetric.kodo.runtime.StateManagerImpl.loadFields(StateManagerImpl.java(Compiled
Code))
at
com.solarmetric.kodo.runtime.StateManagerImpl.preSerialize(StateManagerImpl.java:784)
at com.paresh.core.vo.Release.jdoPreSerialize(Release.java)
at com.paresh.core.vo.Release.writeObject(Release.java)
at java.lang.reflect.Method.invoke(Native Method)
at
com.ibm.rmi.io.IIOPOutputStream.invokeObjectWriter(IIOPOutputStream.java:703)
at com.ibm.rmi.io.IIOPOutputStream.outputObject(IIOPOutputStream.java:671)
at
com.ibm.rmi.io.IIOPOutputStream.simpleWriteObject(IIOPOutputStream.java:146)
at
com.ibm.rmi.io.ValueHandlerImpl.writeValueInternal(ValueHandlerImpl.java:217)
at com.ibm.rmi.io.ValueHandlerImpl.writeValue(ValueHandlerImpl.java:144)
at com.ibm.rmi.iiop.CDROutputStream.write_value(CDROutputStream.java:1590)
at com.ibm.rmi.iiop.CDROutputStream.write_value(CDROutputStream.java:1107)
at
com.paresh.core.interfaces._EJSRemoteStatelessValidation_da16513c_Tie.findCorrectionAction(_EJSRemoteStatelessValidation_da16513c_Tie.java:309)
at
com.paresh.core.interfaces._EJSRemoteStatelessValidation_da16513c_Tie._invoke(_EJSRemoteStatelessValidation_da16513c_Tie.java:104)
at
com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:582)
at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:437)
at com.ibm.rmi.iiop.ORB.process(ORB.java:320)
at com.ibm.CORBA.iiop.ORB.process(ORB.java:1544)
at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2063)
at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)
at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:95)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:592)
kodo.properties
com.solarmetric.kodo.LicenseKey=
#com.solarmetric.kodo.ee.ManagedRuntimeProperties=TransactionManagerName=java:/TransactionManager
com.solarmetric.kodo.ee.ManagedRuntimeProperties=TransactionManagerName=TransactionFactory
TransactionManagerMethod=com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager
#com.solarmetric.kodo.ee.ManagedRuntimeClass=com.solarmetric.kodo.ee.InvocationManagedRuntime
com.solarmetric.kodo.ee.ManagedRuntimeClass=com.solarmetric.kodo.ee.AutomaticManagedRuntime
#javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory
javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.ee.EEPersistenceManagerFactory
javax.jdo.option.ConnectionFactoryName=ds/kodo/DataSource1
javax.jdo.option.Optimistic=true
javax.jdo.option.RetainValues=true
javax.jdo.option.NontransactionalRead=true
#com.solarmetric.kodo.DataCacheClass=com.solarmetric.kodo.runtime.datacache.plugins.CacheImpl
# Changing these to a non-zero value will dramatically increase
# performance, but will cause in-memory databases such as Hypersonic
# SQL to never exit when your main() method exits, as the pooled
# connections in the in-memory database will cause a daemon thread to
# remain running.
javax.jdo.option.MinPool=5
javax.jdo.option.MaxPool=10We do have a makeTransientAll() before the object returns from Session
Bean.
We also tried the JCA path
After installing the JCA RAR and doing a lookup for
PersistenceManagetFactory the same code is not throwing any exception.
The exception is thrown only if datasource is used.
Thanks
Paresh
Marc Prud'hommeaux wrote:
Paresh-
It looks like you are returning a collection of instances from an EJB,
which will cause them to be serialized. The serialization is happening
outside the context of a transaction, and Kodo needs to obtain a
connection. Websphere seems to not like that.
You have a few options:
1. Call makeTransientAll() on all the instances before you return them
from your bean methods
2. Manually instantiate all the fields yourself before sending them
back. You could use a bogus ObjectOutputStream to do this.
3. In 3.0, you can use the new detach() API to detach the instances
before sending them back to the client.
In article <[email protected]>, Paresh wrote:
We had a working application using EEPersistenceManagerFactory
I changed the kodo.properties to lookup a non XA JDBC datasource.
After that the application is working fine (it creates
,updates,deletes,finds record in the DB)
but SystemOut.log has the following error for every operation
We are using Kodo 2.5.0, Websphere 5.0 and Oracle 8
How can we avoid getting this error ?.
We tried to find any property on the Websphere datasource which can be
altered to avoid this error but no luck.
Thanks
Paresh
[10/7/03 15:30:45:467 IST] 3d8b2d1a MCWrapper E J2CA0081E: Method
destroy failed while trying to execute method destroy on ManagedConnection
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl@437f6d23 from resource
<null>. Caught exception: com.ibm.ws.exception.WsException: DSRA0080E: An
exception was received by the Data Store Adapter. See original exception
message: Cannot call 'cleanup' on a ManagedConnection while it is still in
a transaction..
at
com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.<init>(DataStoreAdapterException.java:222)
at
com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.<init>(DataStoreAdapterException.java:172)
at
com.ibm.ws.rsadapter.AdapterUtil.createDataStoreAdapterException(AdapterUtil.java:182)
at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupTransactions(WSRdbManagedConnectionImpl.java:1826)
at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.destroy(WSRdbManagedConnectionImpl.java:1389)
at com.ibm.ejs.j2c.MCWrapper.destroy(MCWrapper.java:1032)
at
com.ibm.ejs.j2c.poolmanager.FreePool.returnToFreePool(FreePool.java:259)
at com.ibm.ejs.j2c.poolmanager.PoolManager.release(PoolManager.java:777)
at com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.java:1304)
at
com.ibm.ejs.j2c.ConnectionEventListener.connectionClosed(ConnectionEventListener.java:195)
at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.processConnectionClosedEvent(WSRdbManagedConnectionImpl.java:843)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.closeWrapper(WSJdbcConnection.java:569)
at com.ibm.ws.rsadapter.jdbc.WSJdbcObject.close(WSJdbcObject.java:132)
at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.close(SQLExecutionManagerImpl.java:814)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.release(JDBCStoreManager.java(Inlined
Compiled Code))
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.load(JDBCStoreManager.java(Compiled
Code))
at
com.solarmetric.kodo.runtime.StateManagerImpl.loadFields(StateManagerImpl.java(Compiled
Code))
at
com.solarmetric.kodo.runtime.StateManagerImpl.preSerialize(StateManagerImpl.java:784)
at com.paresh.core.vo.Release.jdoPreSerialize(Release.java)
at com.paresh.core.vo.Release.writeObject(Release.java)
at java.lang.reflect.Method.invoke(Native Method)
at
com.ibm.rmi.io.IIOPOutputStream.invokeObjectWriter(IIOPOutputStream.java:703)
at com.ibm.rmi.io.IIOPOutputStream.outputObject(IIOPOutputStream.java:671)
at
com.ibm.rmi.io.IIOPOutputStream.simpleWriteObject(IIOPOutputStream.java:146)
at
com.ibm.rmi.io.ValueHandlerImpl.writeValueInternal(ValueHandlerImpl.java:217)
at com.ibm.rmi.io.ValueHandlerImpl.writeValue(ValueHandlerImpl.java:144)
at com.ibm.rmi.iiop.CDROutputStream.write_value(CDROutputStream.java:1590)
at com.ibm.rmi.iiop.CDROutputStream.write_value(CDROutputStream.java:1107)
at
com.paresh.core.interfaces._EJSRemoteStatelessValidation_da16513c_Tie.findCorrectionAction(_EJSRemoteStatelessValidation_da16513c_Tie.java:309)
at
com.paresh.core.interfaces._EJSRemoteStatelessValidation_da16513c_Tie._invoke(_EJSRemoteStatelessValidation_da16513c_Tie.java:104)
at
com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:582)
at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:437)
at com.ibm.rmi.iiop.ORB.process(ORB.java:320)
at com.ibm.CORBA.iiop.ORB.process(ORB.java:1544)
at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2063)
at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)
at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:95)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:592)
kodo.properties
com.solarmetric.kodo.LicenseKey=
#com.solarmetric.kodo.ee.ManagedRuntimeProperties=TransactionManagerName=java:/TransactionManager
>>
>
com.solarmetric.kodo.ee.ManagedRuntimeProperties=TransactionManagerName=TransactionFactory
>>
>
TransactionManagerMethod=com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager
>>
>>
>
#com.solarmetric.kodo.ee.ManagedRuntimeClass=com.solarmetric.kodo.ee.InvocationManagedRuntime
>>
>
com.solarmetric.kodo.ee.ManagedRuntimeClass=com.solarmetric.kodo.ee.AutomaticManagedRuntime
>>
>>
>
#javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory
>>
>
javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.ee.EEPersistenceManagerFactory
>>
javax.jdo.option.ConnectionFactoryName=ds/kodo/DataSource1
javax.jdo.option.Optimistic=true
javax.jdo.option.RetainValues=true
javax.jdo.option.NontransactionalRead=true
#com.solarmetric.kodo.DataCacheClass=com.solarmetric.kodo.runtime.datacache.plugins.CacheImpl
>>
>>
# Changing these to a non-zero value will dramatically increase
# performance, but will cause in-memory databases such as Hypersonic
# SQL to never exit when your main() method exits, as the pooled
# connections in the in-memory database will cause a daemon thread to
# remain running.
javax.jdo.option.MinPool=5
javax.jdo.option.MaxPool=10
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com -
Error while deploying a war file:Urgent
Hi,
I am trying to deploy a war file and i am getting the followinig error on the emd console.
"Failed to deploy application 'xxxx'. No config data persisted for component apache, transaction ID 192.168.40.44.5789f3......"
The opmn log file in the oracle directory is showing the following exceptioin
java.net.ConnectException: Connection refused
Can any one please help me resolve this issue.
Regards
BadariHi,
For a tutorial with source on how to create and deploy a simple quickstart JEE5 JPA enterprise 3-tier application on your Oracle WebLogic 10.3 server - see the following example that uses the EclipseLink JPA provider. You should be able to transition all of your mapping information (the @ManyToOne and table/column overrides and named queries for example) using either JPA via entity annotations or native extensions if you do not want to implement EJB3.
see...
http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial
We also have a similar version for Tomcat 6 except the JPA entity beans run outside a container-managed JTA transaction on the web container - for reference.
http://wiki.eclipse.org/EclipseLink/Examples/JPA/Tomcat_Web_Tutorial
thank you
/michael
www.eclipselink.org
Maybe you are looking for
-
I just signed in to Creative Cloud for the third time today!
Ok, I love the new apps. I am good with the pricing structure. But this mess with first having an endless stream of problems with installing the CC manager, and the AAM, and reinstalling AND reinstalling until finally I was able to hunt down the prob
-
Can there Be More Than One I-Tunes Account on One Computer?
I don't know where to post this question and can't find it anywhere in the Faqs. If there are a couple of people using I-Tunes, can they use the same computer but with their own accounts? If so, how can they set up their own account? The reason I am
-
Can anyone point me in the right direction concerning Guest account that are created on the sponsor Portal. Login is not going through with the account created and after a while it say USER disabled in internal database. How do i see the location of
-
Bypassing proxy while connecting local servers
I have a proxy server 172.22.6.26 with port 80. This is set for http, https, ftp, socks, gopher in system preferences->network->ethernet->advanced->proxies. I am running apache server from eclipse on my macbook pro. Macbook pro ip is 172.22.4.33. Whe
-
Need your help with the following 3 error messages that now appear on my PDF document.
Hi all, I have been working on a PDF document for university for the last 4 months. Its a PDF document which I have been filling in as I go along and saving without any problems. Today however I try to open it for work and this is what I get in succe