SystemException: SubCoordinator
We have the following scenario:
- EJB A method (on serverA) calls a EJB B method (on serverB) using distributed transaction (XA driver)
- server B crasched
- EJB B was deploy on a new serverC
- When EJB A method try to call EJB on serverC we get the message
javax.ejb.EJBException: BEA1-086F92A6F36C1835B17F: javax.transaction.SystemException: SubCoordinator 'manserver19012*serverB*19012+dom_wko+t3+' not available at
Weirdly the reference to serverB appears in the message!!!
Scanning the system file of serverA for the word 'serverB', 2 files were found:
1) servers/manserverA/data/store/default/_WLS_MANSERVERA000000.DAT matches
2) servers/domain_bak/config_prev/config.xml: serverA
What could be done to solve this problem?
Can I remove file 1 e change the name of the server on file 2?
Thanks for any help;
Mauro.
I found a solution:
- stopped the weblogic of serverA
- deleted the file 1 (servers/manserverA/data/store/default/_WLS_MANSERVERA000000.DAT)
- started again the weblogic of serverA
There was a reference inside this file for the old server (serverB).
Is there a better aproach? Is there a way to change the server(called) of an application, and change this file from the caller server dinamically?
Thanks.
Similar Messages
-
XA & JMS javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+' not available
Hi, I'm doing a "proof of concept" on XA transaction spanning two servers.
In order to get it as simple as possible I have configured two servers and
deployed the same MDB on both. I'm also only using JMS resources to simplify
the test.
The goal is to send a message to two different JMS servers (each deployed in
a Weblogic server) both coordinated by an XA UserTransaction started in the
client.
The deployed MDB of each server just listens to a topic and prints out the
received TextMessage.
The configuration is as follows:
* Server 1
Domain name: a
Server name: a00
config.xml (extract):
<JMSServer Name="a.a00.JMSServer" PagingStore="a.a00.JMSFileStore"
Store="a.a00.JMSFileStore" Targets="a00">
<JMSTopic JNDIName="xajms.test.Topic" Name="XA JMS Proof of Concept"
StoreEnabled="true"/>
</JMSServer>
<JMSFileStore Directory="config/a/a00.jmsfilestore"
Name="a.a00.JMSFileStore"/>
<JMSConnectionFactory JNDIName="a.a00.JMSConnectionFactory"
Name="a.a00.JMS Connection Factory" Targets="a00"
UserTransactionsEnabled="true" XAConnectionFactoryEnabled="true"/>
* Server 2
Domain name: b
Server name: b00
config.xml (extract):
<JMSServer Name="b.b00.JMSServer" PagingStore="b.b00.JMSFileStore"
Store="b.b00.JMSFileStore" Targets="b00">
<JMSTopic JNDIName="xajms.test.Topic" Name="XA JMS Proof of Concept"
StoreEnabled="true"/>
</JMSServer>
<JMSFileStore Directory="config/b/b00.jmsfilestore"
Name="b.b00.JMSFileStore"/>
<JMSConnectionFactory JNDIName="b.b00.JMSConnectionFactory"
Name="b.b00.JMS Connection Factory" Targets="b00"
UserTransactionsEnabled="true" XAConnectionFactoryEnabled="true"/>
and here is an extract of client code:
068 UserTransaction utx;
069
070 InitialContext ctx1,ctx2;
071
072 System.out.println("Retrieving initial context for server 1");
073 ctx1 = (InitialContext) getInitialContext(SERVER_1,PORT_1);
074
075 System.out.println("Retrieving initial context for server 2");
076 ctx2 = (InitialContext) getInitialContext(SERVER_2,PORT_2);
077
078 utx = (UserTransaction)
ctx1.lookup("javax.transaction.UserTransaction");
079 utx.setTransactionTimeout(30);
080
081 System.out.println("Begining transaction");
082 utx.begin();
083
084 System.out.println("Sending message to server 1");
085 ref.send(ctx1, JMS_FACTORY_1, args[0]);
086
087 System.out.println("Sending message to server 2");
088 ref.send(ctx2, JMS_FACTORY_2, args[0]);
089
090 System.out.println("Ending transaction...");
091 if (args[1].equals("commit"))
092 utx.commit();
093 else
094 utx.rollback();
end the result of executing it from a third machine:
CASE I:
Retrieving initial context for server 1
Retrieving initial context for server 2
Begining transaction
Sending message to server 1
Sending message to server 2
Ending transaction...
javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+'
not available
Start server side stack trace:
javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+'
not available
at
weblogic.transaction.internal.TransactionImpl.abort(TransactionImpl.java:965
at
weblogic.transaction.internal.ServerSCInfo.startPrepare(ServerSCInfo.java:20
0)
at
weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTran
sactionImpl.java:1619)
at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
nsactionImpl.java:217)
at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
Impl.java:189)
at
weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68
at
weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:140)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:121)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
weblogic.transaction.RollbackException: SubCoordinator
'b00+127.0.0.1:7001+b+' not available
Start server side stack trace:
javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+'
not available
at
weblogic.transaction.internal.TransactionImpl.abort(TransactionImpl.java:965
at
weblogic.transaction.internal.ServerSCInfo.startPrepare(ServerSCInfo.java:20
0)
at
weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTran
sactionImpl.java:1619)
at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
nsactionImpl.java:217)
at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
Impl.java:189)
at
weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68
at
weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:140)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:121)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: SubCoordinator
'b00+127.0.0.1:7001+b+' not available - with nested exception:
[javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+'
not available]
at
weblogic.transaction.internal.TransactionImpl.throwRollbackException(Transac
tionImpl.java:1524)
at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
nsactionImpl.java:265)
at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
Impl.java:189)
at
weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68
at
weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:140)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:121)
End server side stack trace
- with nested exception:
[javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+'
not available
Start server side stack trace:
javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+'
not available
at
weblogic.transaction.internal.TransactionImpl.abort(TransactionImpl.java:965
at
weblogic.transaction.internal.ServerSCInfo.startPrepare(ServerSCInfo.java:20
0)
at
weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTran
sactionImpl.java:1619)
at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
nsactionImpl.java:217)
at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
Impl.java:189)
at
weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68
at
weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:140)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:121)
End server side stack trace
at
weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
java:85)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:136)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy3.commit(Unknown Source)
at
weblogic.transaction.internal.TransactionImpl.commit(TransactionImpl.java:29
4)
at
weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManag
erImpl.java:247)
at
weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManag
erImpl.java:240)
at xajms.client.Send2BothTopics.main(Send2BothTopics.java:110)
real 1m6.530s
user 0m1.380s
sys 0m0.050s
If I swap message sending order the output changes to:
CASE II:
Retrieving initial context for server 1
Retrieving initial context for server 2
Begining transaction
Sending message to server 2
Sending message to server 1
Ending transaction...
weblogic.transaction.internal.TimedOutException: Timed out
tx=0:8c9a9deee02fe21e after 30 seconds
Start server side stack trace:
weblogic.transaction.internal.TimedOutException: Timed out
tx=0:8c9a9deee02fe21e after 30 seconds
at
weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
Impl.java:1228)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
ansactions(ServerTransactionManagerImpl.java:488)
at
weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
erImpl.java:1629)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
sactionManagerImpl.java:451)
at
weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
rImpl.java:1595)
at java.lang.Thread.run(Thread.java:479)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Timed out tx=0:8c9a9deee02fe21e
after 30 seconds
Start server side stack trace:
weblogic.transaction.internal.TimedOutException: Timed out
tx=0:8c9a9deee02fe21e after 30 seconds
at
weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
Impl.java:1228)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
ansactions(ServerTransactionManagerImpl.java:488)
at
weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
erImpl.java:1629)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
sactionManagerImpl.java:451)
at
weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
rImpl.java:1595)
at java.lang.Thread.run(Thread.java:479)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Timed out tx=0:8c9a9deee02fe21e
after 30 seconds - with nested exception:
[weblogic.transaction.internal.TimedOutException: Timed out
tx=0:8c9a9deee02fe21e after 30 seconds]
at
weblogic.transaction.internal.TransactionImpl.throwRollbackException(Transac
tionImpl.java:1524)
at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
nsactionImpl.java:265)
at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
Impl.java:189)
at
weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68
at
weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:140)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:121)
End server side stack trace
- with nested exception:
[weblogic.transaction.internal.TimedOutException: Timed out
tx=0:8c9a9deee02fe21e after 30 seconds
Start server side stack trace:
weblogic.transaction.internal.TimedOutException: Timed out
tx=0:8c9a9deee02fe21e after 30 seconds
at
weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
Impl.java:1228)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
ansactions(ServerTransactionManagerImpl.java:488)
at
weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
erImpl.java:1629)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
sactionManagerImpl.java:451)
at
weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
rImpl.java:1595)
at java.lang.Thread.run(Thread.java:479)
End server side stack trace
at
weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
java:85)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:136)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy3.commit(Unknown Source)
at
weblogic.transaction.internal.TransactionImpl.commit(TransactionImpl.java:29
4)
at
weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManag
erImpl.java:247)
at
weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManag
erImpl.java:240)
at xajms.client.Send2BothTopics.main(Send2BothTopics.java:110)
real 1m32.231s
user 0m1.390s
sys 0m0.030s
not to be said that I have "some" questions about it:
1. Why it doesn't work?
2. Why order of message sending brings two different results?
3. In CASE I:
What is the meaning of the exception "javax.transaction.SystemException:
SubCoordinator 'b00+127.0.0.1:7001+b+' not available"
Why is it using the loopback (127.0.0.1) ip? Is that code being runned
inside the server with the SERVER_2 (192.168.1.3) ip?
4. In case II:
How is that the message of the exception is
"weblogic.transaction.internal.TimedOutException: Timed out
tx=0:8c9a9deee02fe21e after 30 seconds" when it's clear the program took
more than one and a half minutes to execute?
Most of the time is spent after printing the "Ending transaction..." line.
The first part of the program is executed in a few seconds (about 2 or 3 it
depends of the time to get initial context against both servers)
I'm really puzzled with this. I don't know what to think about it. Is this
so weird nobody have tried something like this?
I have done some other test for which the results are:
a) Commenting lines related to UserTransaction (82,91-94)
It works OK. Both servers receive the message.
b) Commenting lines 85 or 88 (related to sending messages to each server)
It works OK. Both servers receive the message. I pressume there is no
"real" XA transaction as there is only one resource involved on it.
c) In CASE I launching the client with "rollback" as second parameter I
neither get any exception nor messages are delivered which would be OK
d) In CASE II launching the client with "rollback" as second parameter I get
a "javax.transaction.SystemException: Timeout during rollback processing"
and messages are not delivered.
Any idea?. I really need this to work in order to free our server for heavy
asyncronous loads and deploy new stuff on it.
PS.
I attach both servers config.xml files and both MDB and client full code. If
you are going to test it you must add a new user and group to weblogic
default file realm:
New user: subscriber
New group: xajms
of course you must add the new user to the new group in order to make it
work.
Here are the lines extracted from server's domain "fileRealm.properties"
file reflecting the new user and group (defined on ejb-jar.xml and
weblogic-ejb-jar.xml files on the "role" section):
group.xajms=subscriber
user.subscriber=0x6b9a704bebc709dd083edd61ed000236eb23987f
The client receives two parameters. The first one is a string to be sent as
message body, the second one is either "commit" or "rollback" just to test
XA transaction doing it's work as expected.
Thanks in advance.
Regards.
Ignacio.
[xajmspoc.zip]
do you connect to 10g database inside onBusinessEvent using Non-XA/XA connection??. I guess it could be bcoz of Non-XA connection (or) XA Without Global Transaction support, and this connection is listed with the transaction manager and it is trying to commit it after onMessage.
For Global Transactions options, go to your weblogic console and check the following path.
(Datasource -> Advanced Options -> Global Transactions -> Honor Global Transactions should be true)
Let me know if you need any help
Rao Kotha. -
Weblogic.tran saction.RollbackException: SubCoordinator ......
Settings:
When we try to call a remote Ejb API the below error is thrown.
xxx.xxx.xx.xx : represents ip for the localhost.
yyy.yyy.yy.yy represents ip for the remote Ejb call
<Apr 24, 2009 3:08:22 PM EDT> <Warning> <JTA> <BEA-110486> <Transaction BEA1-015A5D3211663154D65A cannot complete commit processing beca
use resource [weblogic.jdbc.wrapper.JTSXAResourceImpl] is unavailable. The transaction will be abandoned after 82,022 seconds unless all
resources acknowledge the commit decision.>
<Apr 24, 2009 3:08:50 PM EDT> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-00FFFAB936AC3154D65A(
27212457),Status=Rolling Back. [Reason=javax.transaction.SystemException: SubCoordinator 'AdminServer+yyy.yyy.yy.yyt:9002+emall
+admin+admin+9002+' not available],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=306,seconds left=4,XAServerResourceInfo
[WLStore_JMSIntegration_cgJMSStore]=(ServerResourceInfo[WLStore_JMSIntegration_cgJMSStore]=(state=rolledback,assigned=AdminServer),xar=W
LStore_JMSIntegration_cgJMSStore3903528,re-Registered = false),XAServerResourceInfo[RayEmall_XA]=(ServerResourceInfo[RayEmall_XA]=(state
=new,assigned=AdminServer),xar=null,re-Registered = false),SCInfo[emall+AdminServer]=(state=rolling-back),SCInfo[JMSIntegration+AdminSer
ver]=(state=rolledback),properties=({}),local properties=({class com.bea.wli.bpm.runtime.JpdContainer$TxnListenerxx.xx.xx.xx-69a754d.1
20d9486666.-7fc9=com.bea.wli.bpm.runtime.JpdContainer$TxnListener@13b5abd, class com.bea.wli.bpm.runtime.JpdContainer$TxnListener147.120
.51.42-69a754d.120d9486666.-7fcb=com.bea.wli.bpm.runtime.JpdContainer$TxnListener@1a930f4}),OwnerTransactionManager=ServerTM[ServerCoord
inatorDescriptor=(CoordinatorURL=AdminServer+xxx.xxx.xx.xx:8001+JMSIntegration+t3+, XAResources={WLStore_JMSIntegration_cgJMSStore, webl
ogic.jdbc.wrapper.JTSXAResourceImpl, WLStore_JMSIntegration_WseeFileStore, WLStore_JMSIntegration_gex-edaFileStore, WLStore_JMSIntegrati
on__WLS_AdminServer, LTHDatasource},NonXAResources={})],CoordinatorURL=AdminServer+xxx.xxx.xx.xx:8001+JMSIntegration+t3+): weblogic.tran
saction.RollbackException: SubCoordinator 'AdminServer+yyy.yyy.yy.yy:9002+emall+admin+admin+9002+' not available
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1809)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:331)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:227)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:463)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:335)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:291)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4072)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:3962)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4490)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
.>
<Apr 24, 2009 3:09:22 PM EDT> <Warning> <JTA> <BEA-110486> <Transaction BEA1-006AA78459E63154D65A cannot complete commit processing beca
use resource [weblogic.jdbc.wrapper.JTSXAResourceImpl] is unavailable. The transaction will be abandoned after 77,408 seconds unless all
resources acknowledge the commit decision.>
None of the transactions are recorded on the WLICONSOLE when the Remote EJB call is envoked. When i comment out the code for the Remote API Call there is no error being thrown, and the WLICONSOLE records the transactions as completed. I tried to debug the error, but the process seems to complete the execution, with the result as expected, but the error is still present despite of the process complete execution, with no other errors.
One more thing: Despite of the message "AdminServer+yyy.yyy.yy.yyt:9002+emall+admin+admin+9002+' not available" if i copy the IPaddress on the browser the server is present and its the Admin server console of the cluster.
Edmond.We have 2 domains that need to commnicate. Web domain has the webapp deployed and invokes the Integration app in the integration domain.
Web Domain DS:
URL : jdbc:oracle:thin:@xxx.xxx.xx.xx:1521:dbname
Driver Class Name: oracle.jdbc.xa.client.OracleXADataSource
DS name : lthDatasource
Integration Domain DS:
URL : jdbc:oracle:thin:@xxx.xxx.xx.xx:1521:dbname
Driver Class Name: oracle.jdbc.xa.client.OracleXADataSource
DS Name: LTHDatasource
The reason we need the DS from both domains is because we right data to the DB from both apps that are deployed in both domains.
Below is the error that continues to be thrown despite of the Server gets restarted or not, and terminating all of the Transactions from the WLI Console. A bit confusing, but due to the fact that is throwing the below error, it seems as it is an Local issue, and i don't know where the problem is.
<Apr 27, 2009 8:32:21 AM EDT> <Warning> <JTA> <BEA-110486> <Transaction BEA1-006AA78459E63154D65A cannot complete commit processing bec
ause resource [weblogic.jdbc.wrapper.JTSXAResourceImpl] is unavailable. The transaction will be abandoned after 54 seconds unless all r
esources acknowledge the commit decision.>
<Apr 27, 2009 8:33:21 AM EDT> <Error> <JTA> <BEA-110423> <Abandoning transaction after 244,431 seconds: Xid=BEA1-006AA78459E63154D65A(4
297209),Status=Committing,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=244431,seconds left=0,XAServerResourceInfo[WLSt
ore_JMSIntegration_cgJMSStore]=(ServerResourceInfo[WLStore_JMSIntegration_cgJMSStore]=(state=committed,assigned=AdminServer),xar=WLStor
e_JMSIntegration_cgJMSStore6065567,re-Registered = true),XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceI
nfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=new,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@21a87e5,re-Registere
d = true),SCInfo[JMSIntegration+AdminServer]=(state=committed),properties=({ISOLATION LEVEL=2, weblogic.jdbc=t3://XXX.xxx.xx.xx:8001}),
local properties=({weblogic.transaction.recoveredTransaction=true}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(Coord
inatorURL=AdminServer+XXX.xxx.xx.xx:8001+JMSIntegration+t3+, XAResources={WLStore_JMSIntegration_cgJMSStore, weblogic.jdbc.wrapper.JTSX
AResourceImpl, WLStore_JMSIntegration_WseeFileStore, WLStore_JMSIntegration_gex-edaFileStore, WLStore_JMSIntegration__WLS_AdminServer,
LTHDatasource},NonXAResources={})],CoordinatorURL=AdminServer+XXX.xxx.xx.xx:8001+JMSIntegration+t3+)>
<Apr 27, 2009 8:33:21 AM EDT> <Error> <JTA> <BEA-110423> <Abandoning transaction after 239,877 seconds: Xid=BEA1-015A5D3211663154D65A(4
267614),Status=Committing,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=239876,seconds left=0,XAServerResourceInfo[WLSt
ore_JMSIntegration_cgJMSStore]=(ServerResourceInfo[WLStore_JMSIntegration_cgJMSStore]=(state=committed,assigned=AdminServer),xar=WLStor
e_JMSIntegration_cgJMSStore6065567,re-Registered = true),XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceI
nfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=new,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@21a87e5,re-Registere
d = true),SCInfo[JMSIntegration+AdminServer]=(state=committed),properties=({ISOLATION LEVEL=2, weblogic.jdbc=t3://XXX.xxx.xx.xx:8001}),
local properties=({weblogic.transaction.recoveredTransaction=true}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(Coord
inatorURL=AdminServer+XXX.xxx.xx.xx:8001+JMSIntegration+t3+, XAResources={WLStore_JMSIntegration_cgJMSStore, weblogic.jdbc.wrapper.JTSX
AResourceImpl, WLStore_JMSIntegration_WseeFileStore, WLStore_JMSIntegration_gex-edaFileStore, WLStore_JMSIntegration__WLS_AdminServer,
LTHDatasource},NonXAResources={})],CoordinatorURL=AdminServer+XXX.xxx.xx.xx:8001+JMSIntegration+t3+)> -
BEA-010026 Exception occurred during commit of transaction Xid...
Srs,
Does anyone know how can i change the IP address bellow ? is there any file with this configuration ? ( i dont know so well weblogic )
This is a unkown IP (10.26.71.28) and probably for this reason, the following error appears:
<Mar 31, 2010 1:53:48 PM BRT> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-012A4C55A4FA8C6F67D0(13881631),Status=Rolling Back. [Reason=javax.transaction.SystemException: SubCoordinator 'AdminServer+*10.26.71.28*:7001+tdws_domain+t3+' not available],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=167,seconds left=55,XAServerResourceInfo[JMS_ADMLoggingStore]=(ServerResourceInfo[JMS_ADMLoggingStore]=(state=rolledback,assigned=adm_managed_server),xar=JMS_ADMLoggingStore,re-Registered = false),XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=new,assigned=AdminServer),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@15d1298,re-Registered = false),SCInfo[tdws_domain+AdminServer]=(state=rolling-back),SCInfo[adm+adm_managed_server]=(state=rolledback),properties=({weblogic.jdbc=t3://*10.26.71.28*:8080, START_AND_END_THREAD_EQUAL=false}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=adm_managed_server+146.250.132.247:7001+adm+t3+, XAResources={weblogic.jdbc.wrapper.JTSXAResourceImpl, JMS_ADMLoggingStore},NonXAResources={})],CoordinatorURL=adm_managed_server+146.250.132.247:7001+adm+t3+): javax.transaction.SystemException: SubCoordinator 'AdminServer+*10.26.71.28*:7001+tdws_domain+t3+' not available
at weblogic.transaction.internal.TransactionImpl.abort(TransactionImpl.java:1045)
at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:173)
at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:163)
at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1202)
at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:2007)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:257)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:228)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:430)
at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:333)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:298)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2698)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2610)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: SubCoordinator 'AdminServer+10.26.71.28:7001+tdws_domain+t3+' not available - with nested exception:
[javax.transaction.SystemException: SubCoordinator 'AdminServer+10.26.71.28:7001+tdws_domain+t3+' not available]
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1687)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:311)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:228)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:430)
at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:333)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:298)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2698)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2610)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Thanks,
Claudio
Edited by: user1098890 on 31/03/2010 12:35Did anyone ever find an answer to this? I have the same problem.
-
Tcp/ip unicast protocol between clustermembers
hi,
i want to understand what's happen while synchronizing the cluster members in the unicast case. anybody an idea? i captured the packages between the members,
but there are a proprietary protocol i don't understand.
regardsI am co-worker of BOD and like to specify an other aspect of the same problem. Often the transactions get cancelled with the following exception:
javax.transaction.SystemException: SubCoordinator 'managedServer_a_xx_01+a-xx-appl01:31370+a_xx+t3+' not available
at weblogic.transaction.internal.TransactionImpl.abort(TransactionImpl.java:1142)
at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:173)
at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:163)
at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1310)
at weblogic.transaction.internal.SubCoordinatorImpl.startPrePrepareAndChain(SubCoordinatorImpl.java:90)
at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
We suspect that the clusters are not synchronised like they should. Interestingly the same code ran well on weblogic 9.2.3 with multicast. Now with weblogic 10.3.1 with unicast enabled we encounter these problems. Furthermore we should mention that the replication occurs on the default channel. -
Help: jms bridge failed to put messages into target destination!
Hi all,
I created a jms bridge to transfer msgs form one domain(one cluster,hpux) to another domain(one cluster,aix),but it seems that the msg can't arrive at the target destination,below are the main log records:
####<2006-11-29 下åˆ09æ—¶19分09秒 GMT+08:00> <Info> <MessagingBridge> <billeai2> <beSrvB1> <ExecuteThread: '14' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-200033> <Bridge "BillToEaiAckBridgeB1" is obtaining connections to the two adapters.>
####<2006-11-29 下åˆ09æ—¶19分09秒 GMT+08:00> <Info> <Common> <billeai2> <beSrvB1> <ExecuteThread: '14' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-000628> <Created "1" resources for pool "Weblogic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA", out of which "1" are available and "0" are unavailable.>
####<2006-11-29 下åˆ09æ—¶19分09秒 GMT+08:00> <Info> <Common> <billeai2> <beSrvB1> <ExecuteThread: '14' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-000628> <Created "1" resources for pool "Weblogic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA", out of which "1" are available and "0" are unavailable.>
####<2006-11-29 下åˆ09æ—¶19分09秒 GMT+08:00> <Info> <MessagingBridge> <billeai2> <beSrvB1> <ExecuteThread: '14' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-200032> <Bridge "BillToEaiAckBridgeB1" is configured to disallow degradation of its quality of service in cases where the configured quality of service is unreachable.>
####<2006-11-29 下åˆ09æ—¶19分09秒 GMT+08:00> <Info> <MessagingBridge> <billeai2> <beSrvB1> <ExecuteThread: '14' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-200030> <Bridge "BillToEaiAckBridgeB1" is configured to work in "Exactly-once" mode, and it is actually working in "Exactly-once" mode.>
####<2006-11-29 下åˆ09æ—¶19分09秒 GMT+08:00> <Info> <MessagingBridge> <billeai2> <beSrvB1> <ExecuteThread: '14' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-200028> <The bridge "BillToEaiAckBridgeB1" has started transferring messages.>
####<2006-11-29 下åˆ09æ—¶20分11秒 GMT+08:00> <Error> <MessagingBridge> <billeai2> <beSrvB1> <ExecuteThread: '14' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-200015> <An error occurred in bridge "BillToEaiAckBridgeB1" during the transfer of messages (weblogic.transaction.RollbackException: SubCoordinator 'eaiServerB1+10.1.31.7:7011+eaiDomain+t3+' not available - with nested exception:
[javax.transaction.SystemException: SubCoordinator 'eaiServerB1+10.1.31.7:7011+eaiDomain+t3+' not available]).>
####<2006-11-29 下åˆ09æ—¶20分11秒 GMT+08:00> <Warning> <MessagingBridge> <billeai2> <beSrvB1> <ExecuteThread: '14' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-200026> <Bridge "BillToEaiAckBridgeB1" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was weblogic.jms.bridge.internal.MessagingBridgeException.)>
####<2006-11-29 下åˆ09æ—¶20分12秒 GMT+08:00> <Info> <MessagingBridge> <billeai2> <beSrvB1> <ExecuteThread: '14' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-200020> <Bridge "BillToEaiAckBridgeB1" is stopped.>
The logs told that the target destination is N/A,but didn't tell the detaild reason. Is there anybody who met this problem before and please give me a hand!!! thanks a lot!!the domains have to "trust" each other. Make sure to follow the instructions about the "enabled generated credential" in the following doc:
http://edocs.bea.com/wls/docs81/ConsoleHelp/messaging_bridge.html#1122172 -
Hi ,
We seem to have unpredictable results with XA in this environment
Weblogic 7.0 sp2
UDB EE 7.2 fixpack 7
IBM JDBC driver type 2
Symptoms
A Weblogic instance exits without any log messages
One of the weblogic instance in the cluster exits without log messages and
results in
javax.transaction.SystemException : SubCoordinator not available
Has anybody come across this problem before?
Thanks much
Vaidya
Only clue I have so far is this stack trace
<Jun 26, 2003 12:40:58 PM EDT> <Debug> <JTA> <110027> <java.lang.Exception: TRACE:
ResourceDescriptor[peServicingPool_UDBDriverXA06]: initXAResource(aXar=peServicingPool_UDBDriverXA06),
xar=null
####<Jun 26, 2003 12:40:58 PM EDT> <Debug> <JTA> <he2unx18> <peServicing1> <main>
<kernel identity> <> <110027> <java.lang.Exception: TRACE: ResourceDescriptor[peServicingPool_UDBDriverXA06]:
initXAResource(aXar=peServicingPool_UDBDriverXA06), xar=null
<Jun 26, 2003 12:40:58 PM EDT> <Debug> <JTA> <110027> <java.lang.Exception: TRACE:
ResourceDescriptor[peServicingPool_UDBDriverXA06]: initXAResource(aXar=peServicingPool_UDBDriverXA06)
####<Jun 26, 2003 12:40:58 PM EDT> <Debug> <JTA> <he2unx18> <peServicing1> <main>
<kernel identity> <> <110027> <java.lang.Exception: TRACE: ResourceDescriptor[peServicingPool_UDBDriverXA06]:
initXAResource(aXar=peServicingPool_UDBDriverXA06)
<Jun 26, 2003 12:40:58 PM EDT> <Debug> <JTA> <110027> <java.lang.Exception: TRACE:
ResourceDescriptor[peServicingPool_UDBDriverXA06]: register
####<Jun 26, 2003 12:40:58 PM EDT> <Debug> <JTA> <he2unx18> <peServicing1> <main>
<kernel identity> <> <110027> <java.lang.Exception: TRACE: ResourceDescriptor[peServicingPool_UDBDriverXA06]:
register
<Jun 26, 2003 12:41:07 PM EDT> <Debug> <JTA> <110027> <java.lang.Exception: TRACE:
ResourceDescriptor[JMS_peServicing1_JMS_Store]: initXAResource(aXar=JMS_peServicing1_JMS_Store),
xar=null
####<Jun 26, 2003 12:41:07 PM EDT> <Debug> <JTA> <he2unx18> <peServicing1> <main>
<kernel identity> <> <110027> <java.lang.Exception: TRACE: ResourceDescriptor[JMS_peServicing1_JMS_Store]:
initXAResource(aXar=JMS_peServicing1_JMS_Store), xar=null
<Jun 26, 2003 12:41:07 PM EDT> <Debug> <JTA> <110027> <java.lang.Exception: TRACE:
ResourceDescriptor[JMS_peServicing1_JMS_Store]: initXAResource(aXar=JMS_peServicing1_JMS_Store)
####<Jun 26, 2003 12:41:07 PM EDT> <Debug> <JTA> <he2unx18> <peServicing1> <main>
<kernel identity> <> <110027> <java.lang.Exception: TRACE: ResourceDescriptor[JMS_peServicing1_JMS_Store]:
initXAResource(aXar=JMS_peServicing1_JMS_Store)
<Jun 26, 2003 12:41:07 PM EDT> <Debug> <JTA> <110027> <java.lang.Exception: TRACE:
ResourceDescriptor[JMS_peServicing1_JMS_Store]: register
####<Jun 26, 2003 12:41:07 PM EDT> <Debug> <JTA> <he2unx18> <peServicing1> <main>
<kernel identity> <> <110027> <java.lang.Exception: TRACE: ResourceDescriptor[JMS_peServicing1_JMS_Store]:
register
I'm not sure why WLS is existing.
However, if the instance is part of a global transaction, then you might get
sub-cordiantor not available messages.
You might want to try 7.0SP3. It has a lot of fixes for JTA/JDBC/JMS.
"Vaidya Krishnamurthy" <[email protected]> wrote in message news:[email protected]...
>
> Hi ,
>
> We seem to have unpredictable results with XA in this environment
>
> Weblogic 7.0 sp2
> UDB EE 7.2 fixpack 7
> IBM JDBC driver type 2
>
> Symptoms
> A Weblogic instance exits without any log messages
> One of the weblogic instance in the cluster exits without log messages and
> results in
> javax.transaction.SystemException : SubCoordinator not available
>
> Has anybody come across this problem before?
> Thanks much
> Vaidya
>
>
> Only clue I have so far is this stack trace
>
> <Jun 26, 2003 12:40:58 PM EDT> <Debug> <JTA> <110027> <java.lang.Exception: TRACE:
> ResourceDescriptor[peServicingPool_UDBDriverXA06]: initXAResource(aXar=peServicingPool_UDBDriverXA06),
> xar=null
> ####<Jun 26, 2003 12:40:58 PM EDT> <Debug> <JTA> <he2unx18> <peServicing1> <main>
> <kernel identity> <> <110027> <java.lang.Exception: TRACE: ResourceDescriptor[peServicingPool_UDBDriverXA06]:
> initXAResource(aXar=peServicingPool_UDBDriverXA06), xar=null
> <Jun 26, 2003 12:40:58 PM EDT> <Debug> <JTA> <110027> <java.lang.Exception: TRACE:
> ResourceDescriptor[peServicingPool_UDBDriverXA06]: initXAResource(aXar=peServicingPool_UDBDriverXA06)
> ####<Jun 26, 2003 12:40:58 PM EDT> <Debug> <JTA> <he2unx18> <peServicing1> <main>
> <kernel identity> <> <110027> <java.lang.Exception: TRACE: ResourceDescriptor[peServicingPool_UDBDriverXA06]:
> initXAResource(aXar=peServicingPool_UDBDriverXA06)
> <Jun 26, 2003 12:40:58 PM EDT> <Debug> <JTA> <110027> <java.lang.Exception: TRACE:
> ResourceDescriptor[peServicingPool_UDBDriverXA06]: register
> ####<Jun 26, 2003 12:40:58 PM EDT> <Debug> <JTA> <he2unx18> <peServicing1> <main>
> <kernel identity> <> <110027> <java.lang.Exception: TRACE: ResourceDescriptor[peServicingPool_UDBDriverXA06]:
> register
> <Jun 26, 2003 12:41:07 PM EDT> <Debug> <JTA> <110027> <java.lang.Exception: TRACE:
> ResourceDescriptor[JMS_peServicing1_JMS_Store]: initXAResource(aXar=JMS_peServicing1_JMS_Store),
> xar=null
> ####<Jun 26, 2003 12:41:07 PM EDT> <Debug> <JTA> <he2unx18> <peServicing1> <main>
> <kernel identity> <> <110027> <java.lang.Exception: TRACE: ResourceDescriptor[JMS_peServicing1_JMS_Store]:
> initXAResource(aXar=JMS_peServicing1_JMS_Store), xar=null
> <Jun 26, 2003 12:41:07 PM EDT> <Debug> <JTA> <110027> <java.lang.Exception: TRACE:
> ResourceDescriptor[JMS_peServicing1_JMS_Store]: initXAResource(aXar=JMS_peServicing1_JMS_Store)
> ####<Jun 26, 2003 12:41:07 PM EDT> <Debug> <JTA> <he2unx18> <peServicing1> <main>
> <kernel identity> <> <110027> <java.lang.Exception: TRACE: ResourceDescriptor[JMS_peServicing1_JMS_Store]:
> initXAResource(aXar=JMS_peServicing1_JMS_Store)
> <Jun 26, 2003 12:41:07 PM EDT> <Debug> <JTA> <110027> <java.lang.Exception: TRACE:
> ResourceDescriptor[JMS_peServicing1_JMS_Store]: register
> ####<Jun 26, 2003 12:41:07 PM EDT> <Debug> <JTA> <he2unx18> <peServicing1> <main>
> <kernel identity> <> <110027> <java.lang.Exception: TRACE: ResourceDescriptor[JMS_peServicing1_JMS_Store]:
> register
-
Javax.transaction.SystemException: Timed out while in 'Logging' state!!!!
Hello, we have an OracleWeblogic 10.3.2 running on a Solaris OS.
In this AppServer we have a FullStack J2EE Application executing distributed transactions that involve 3 manageable resources:
TxDatasource (EJB),
NonTxDatasource with enableTwoPhaseCommit and
JMS
Some of the transactions are timing out while in 'Logging' state and I just cant figure out what the root cause is. As a defensive action I lowered the JTA Timeout seconds because I noticed the 'Logging' phase was taking too long and then timing out. Idea here was not to have too many threads hanging in Logging state and therefore use the JTA Timeout to overcome this problem and minimize impact.
Below, I'm posting a few exceptions thrown in applicaiton log. Any help is very appreciated.
####<Aug 12, 2011 11:40:11 AM EDT> <Error> <EJB> <brzfxap1> <FefxServer> <[ACTIVE] ExecuteThread: '175' for queue: 'weblogic.kernel.Default (self-tuning)'> <JG47515> <> <> <1313163611120> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB com.citicorp.fx.credit.CreditServiceBean.askCreditQuery(com.citicorp.fx.credit.data.CreditQueryRequestData)],Xid=BEA1-7DB913B4CB2B36D47CB7(1248714554),Status=Rolled back. [Reason=javax.transaction.SystemException: Timed out while in 'Logging' state],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=82,seconds left=60,XAServerResourceInfo[TWOraDS_fefx]=(ServerResourceInfo[TWOraDS_fefx]=(state=rolledback,assigned=FefxServer),xar=TWOraDS,re-Registered = false),XAServerResourceInfo[WLStore_fefx_FefxFileStore]=(ServerResourceInfo[WLStore_fefx_FefxFileStore]=(state=rolledback,assigned=FefxServer),xar=WLStore_fefx_FefxFileStore1032009487,re-Registered = false),SCInfo[fefx+FefxServer]=(state=rolledback),properties=({weblogic.transaction.name=[EJB com.citicorp.fx.credit.CreditServiceBean.askCreditQuery(com.citicorp.fx.credit.data.CreditQueryRequestData)]}),local properties=({weblogic.jdbc.jta.TWOraDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+, XAResources={WLStore_fefx_FefxFileStore, TWOraDS_fefx, WLStore_fefx__WLS_FefxServer, weblogic.jdbc.wrapper.JTSXAResourceImpl, WSATGatewayRM_FefxServer_fefx},NonXAResources={})],CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+): weblogic.transaction.RollbackException: Timed out while in 'Logging' state
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1848)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:339)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:621)
at weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:60)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvokeTxRetry(BaseRemoteObject.java:441)
at com.citicorp.fx.credit.CreditService_6w08fk_EOImpl.askCreditQuery(CreditService_6w08fk_EOImpl.java:75)
at com.citicorp.fx.client.creditquery.QueryProcessor.handleEvent(QueryProcessor.java:77)
at org.jac.creation.ProcessorAction.handleEvent(ProcessorAction.java:64)
at org.jac.runtime.AbstractAction.handleSecuredEvent(AbstractAction.java:73)
at org.jac.runtime.StateImpl.handleEvent(StateImpl.java:66)
at org.jac.runtime.ControllerImpl.handleEvent(ControllerImpl.java:123)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:55)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:78)
at org.jac.creation.JacImpl.handleEvent(JacImpl.java:53)
at org.jac.runtime.JACExecutor.handleEvent(JACExecutor.java:111)
at org.jac.runtime.JACExecutor.handleEventBySessionID(JACExecutor.java:103)
at org.jac.http.ControllerFilter.doFilter(ControllerFilter.java:63)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.fx.util.compression.CompressionFilter.doFilter(CompressionFilter.java:189)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.security.web.WebLogicSiteminderAuthenticationFilter.doFilter(WebLogicSiteminderAuthenticationFilter.java:65)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: Timed out while in 'Logging' state
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1797)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1609)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1885)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1519)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
... 2 more
.>
####<Aug 12, 2011 11:40:11 AM EDT> <Error> <EJB> <brzfxap1> <FefxServer> <[ACTIVE] ExecuteThread: '154' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1313163611119> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-7DBB13B4CB2B36D47CB7(977835896),Status=Rolled back. [Reason=javax.transaction.SystemException: Timed out while in 'Logging' state],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=60,seconds left=60,XAServerResourceInfo[WLStore_fefx_FefxFileStore]=(ServerResourceInfo[WLStore_fefx_FefxFileStore]=(state=rolledback,assigned=FefxServer),xar=WLStore_fefx_FefxFileStore1032009487,re-Registered = false),XAServerResourceInfo[TWOraDS_fefx]=(ServerResourceInfo[TWOraDS_fefx]=(state=rolledback,assigned=FefxServer),xar=TWOraDS,re-Registered = false),SCInfo[fefx+FefxServer]=(state=rolledback),local properties=({weblogic.jdbc.jta.TWOraDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+, XAResources={WLStore_fefx_FefxFileStore, TWOraDS_fefx, WLStore_fefx__WLS_FefxServer, weblogic.jdbc.wrapper.JTSXAResourceImpl, WSATGatewayRM_FefxServer_fefx},NonXAResources={})],CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+): weblogic.transaction.RollbackException: Timed out while in 'Logging' state
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1848)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:339)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:500)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4585)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4271)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3747)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5096)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: Timed out while in 'Logging' state
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1797)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1609)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1885)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1519)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
... 3 more
.>
This is the stack trace of the thread that hangs while waiting for the lock to write in the transaction file:
"[ACTIVE] ExecuteThread: '64' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=3 tid=0x000000010dea3000 nid=0x1e2 in Object.wait() [0xfffffffda03ff000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at weblogic.transaction.internal.ServerTransactionImpl.log(ServerTransactionImpl.java:2005)
- locked <0xfffffffe64964b30> (a weblogic.transaction.internal.ServerTransactionImpl)
at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:2320)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:273)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:621)
at weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:60)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvokeTxRetry(BaseRemoteObject.java:441)
at com.citicorp.fx.credit.CreditService_6w08fk_EOImpl.askCreditQuery(CreditService_6w08fk_EOImpl.java:75)
at com.citicorp.fx.client.creditquery.QueryProcessor.handleEvent(QueryProcessor.java:77)
at org.jac.creation.ProcessorAction.handleEvent(ProcessorAction.java:64)
at org.jac.runtime.AbstractAction.handleSecuredEvent(AbstractAction.java:73)
at org.jac.runtime.StateImpl.handleEvent(StateImpl.java:66)
at org.jac.runtime.ControllerImpl.handleEvent(ControllerImpl.java:123)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:55)
- locked <0xfffffffe0860e618> (a org.jac.session.SessionImpl)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:78)
- locked <0xfffffffe0860e618> (a org.jac.session.SessionImpl)
at org.jac.creation.JacImpl.handleEvent(JacImpl.java:53)
at org.jac.runtime.JACExecutor.handleEvent(JACExecutor.java:111)
at org.jac.runtime.JACExecutor.handleEventBySessionID(JACExecutor.java:103)
at org.jac.http.ControllerFilter.doFilter(ControllerFilter.java:63)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.fx.util.compression.CompressionFilter.doFilter(CompressionFilter.java:189)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.security.web.WebLogicSiteminderAuthenticationFilter.doFilter(WebLogicSiteminderAuthenticationFilter.java:65)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Edited by: user8727499 on Aug 12, 2011 11:57 AMHello, we have an OracleWeblogic 10.3.2 running on a Solaris OS.
In this AppServer we have a FullStack J2EE Application executing distributed transactions that involve 3 manageable resources:
TxDatasource (EJB),
NonTxDatasource with enableTwoPhaseCommit and
JMS
Some of the transactions are timing out while in 'Logging' state and I just cant figure out what the root cause is. As a defensive action I lowered the JTA Timeout seconds because I noticed the 'Logging' phase was taking too long and then timing out. Idea here was not to have too many threads hanging in Logging state and therefore use the JTA Timeout to overcome this problem and minimize impact.
Below, I'm posting a few exceptions thrown in applicaiton log. Any help is very appreciated.
####<Aug 12, 2011 11:40:11 AM EDT> <Error> <EJB> <brzfxap1> <FefxServer> <[ACTIVE] ExecuteThread: '175' for queue: 'weblogic.kernel.Default (self-tuning)'> <JG47515> <> <> <1313163611120> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB com.citicorp.fx.credit.CreditServiceBean.askCreditQuery(com.citicorp.fx.credit.data.CreditQueryRequestData)],Xid=BEA1-7DB913B4CB2B36D47CB7(1248714554),Status=Rolled back. [Reason=javax.transaction.SystemException: Timed out while in 'Logging' state],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=82,seconds left=60,XAServerResourceInfo[TWOraDS_fefx]=(ServerResourceInfo[TWOraDS_fefx]=(state=rolledback,assigned=FefxServer),xar=TWOraDS,re-Registered = false),XAServerResourceInfo[WLStore_fefx_FefxFileStore]=(ServerResourceInfo[WLStore_fefx_FefxFileStore]=(state=rolledback,assigned=FefxServer),xar=WLStore_fefx_FefxFileStore1032009487,re-Registered = false),SCInfo[fefx+FefxServer]=(state=rolledback),properties=({weblogic.transaction.name=[EJB com.citicorp.fx.credit.CreditServiceBean.askCreditQuery(com.citicorp.fx.credit.data.CreditQueryRequestData)]}),local properties=({weblogic.jdbc.jta.TWOraDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+, XAResources={WLStore_fefx_FefxFileStore, TWOraDS_fefx, WLStore_fefx__WLS_FefxServer, weblogic.jdbc.wrapper.JTSXAResourceImpl, WSATGatewayRM_FefxServer_fefx},NonXAResources={})],CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+): weblogic.transaction.RollbackException: Timed out while in 'Logging' state
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1848)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:339)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:621)
at weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:60)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvokeTxRetry(BaseRemoteObject.java:441)
at com.citicorp.fx.credit.CreditService_6w08fk_EOImpl.askCreditQuery(CreditService_6w08fk_EOImpl.java:75)
at com.citicorp.fx.client.creditquery.QueryProcessor.handleEvent(QueryProcessor.java:77)
at org.jac.creation.ProcessorAction.handleEvent(ProcessorAction.java:64)
at org.jac.runtime.AbstractAction.handleSecuredEvent(AbstractAction.java:73)
at org.jac.runtime.StateImpl.handleEvent(StateImpl.java:66)
at org.jac.runtime.ControllerImpl.handleEvent(ControllerImpl.java:123)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:55)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:78)
at org.jac.creation.JacImpl.handleEvent(JacImpl.java:53)
at org.jac.runtime.JACExecutor.handleEvent(JACExecutor.java:111)
at org.jac.runtime.JACExecutor.handleEventBySessionID(JACExecutor.java:103)
at org.jac.http.ControllerFilter.doFilter(ControllerFilter.java:63)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.fx.util.compression.CompressionFilter.doFilter(CompressionFilter.java:189)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.security.web.WebLogicSiteminderAuthenticationFilter.doFilter(WebLogicSiteminderAuthenticationFilter.java:65)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: Timed out while in 'Logging' state
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1797)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1609)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1885)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1519)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
... 2 more
.>
####<Aug 12, 2011 11:40:11 AM EDT> <Error> <EJB> <brzfxap1> <FefxServer> <[ACTIVE] ExecuteThread: '154' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1313163611119> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-7DBB13B4CB2B36D47CB7(977835896),Status=Rolled back. [Reason=javax.transaction.SystemException: Timed out while in 'Logging' state],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=60,seconds left=60,XAServerResourceInfo[WLStore_fefx_FefxFileStore]=(ServerResourceInfo[WLStore_fefx_FefxFileStore]=(state=rolledback,assigned=FefxServer),xar=WLStore_fefx_FefxFileStore1032009487,re-Registered = false),XAServerResourceInfo[TWOraDS_fefx]=(ServerResourceInfo[TWOraDS_fefx]=(state=rolledback,assigned=FefxServer),xar=TWOraDS,re-Registered = false),SCInfo[fefx+FefxServer]=(state=rolledback),local properties=({weblogic.jdbc.jta.TWOraDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+, XAResources={WLStore_fefx_FefxFileStore, TWOraDS_fefx, WLStore_fefx__WLS_FefxServer, weblogic.jdbc.wrapper.JTSXAResourceImpl, WSATGatewayRM_FefxServer_fefx},NonXAResources={})],CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+): weblogic.transaction.RollbackException: Timed out while in 'Logging' state
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1848)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:339)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:500)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4585)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4271)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3747)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5096)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: Timed out while in 'Logging' state
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1797)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1609)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1885)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1519)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
... 3 more
.>
This is the stack trace of the thread that hangs while waiting for the lock to write in the transaction file:
"[ACTIVE] ExecuteThread: '64' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=3 tid=0x000000010dea3000 nid=0x1e2 in Object.wait() [0xfffffffda03ff000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at weblogic.transaction.internal.ServerTransactionImpl.log(ServerTransactionImpl.java:2005)
- locked <0xfffffffe64964b30> (a weblogic.transaction.internal.ServerTransactionImpl)
at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:2320)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:273)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:621)
at weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:60)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvokeTxRetry(BaseRemoteObject.java:441)
at com.citicorp.fx.credit.CreditService_6w08fk_EOImpl.askCreditQuery(CreditService_6w08fk_EOImpl.java:75)
at com.citicorp.fx.client.creditquery.QueryProcessor.handleEvent(QueryProcessor.java:77)
at org.jac.creation.ProcessorAction.handleEvent(ProcessorAction.java:64)
at org.jac.runtime.AbstractAction.handleSecuredEvent(AbstractAction.java:73)
at org.jac.runtime.StateImpl.handleEvent(StateImpl.java:66)
at org.jac.runtime.ControllerImpl.handleEvent(ControllerImpl.java:123)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:55)
- locked <0xfffffffe0860e618> (a org.jac.session.SessionImpl)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:78)
- locked <0xfffffffe0860e618> (a org.jac.session.SessionImpl)
at org.jac.creation.JacImpl.handleEvent(JacImpl.java:53)
at org.jac.runtime.JACExecutor.handleEvent(JACExecutor.java:111)
at org.jac.runtime.JACExecutor.handleEventBySessionID(JACExecutor.java:103)
at org.jac.http.ControllerFilter.doFilter(ControllerFilter.java:63)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.fx.util.compression.CompressionFilter.doFilter(CompressionFilter.java:189)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.security.web.WebLogicSiteminderAuthenticationFilter.doFilter(WebLogicSiteminderAuthenticationFilter.java:65)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Edited by: user8727499 on Aug 12, 2011 11:57 AM -
Transaction rollback due to SystemException
"I get this exception during a batch process. I use a Message queue to gather messages and an MDB spins out multiple threads to service the messages. The transaction breaks due to a SystemException and says transaction has been rolledback. But I've no clue why the transaction is getting rolledback. This happens to most of the messages in the queue.
The following is the exception.
Exception while committing Tx : Name=[EJB com.firstapex.v4.elife.ifb.ejb.IFBControllerBean.createIFBBill(java.lang.String,java.lang.String,java.lang.String)],Xid=16:948bae057f28edb9(32534089),Status=Rolled back. [Reason=javax.transaction.SystemException: The transaction has been rolled back],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=999,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=rolledback,assigned=myserver,xar=weblogic.jdbc.jts.Connection@1d8afee),SCInfo[mydomain myserver]=(state=rolledback),properties=({weblogic.transaction.name=[EJB com.firstapex.v4.elife.ifb.ejb.IFBControllerBean.createIFBBill(java.lang.String,java.lang.String,java.lang.String)], ISOLATION LEVEL=2, weblogic.jdbc=t3://160.1.25.103:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=myserver 160.1.25.103:7001 mydomain t3 , Resources={})],CoordinatorURL=myserver 160.1.25.103:7001 mydomain t3 ): javax.transaction.SystemException: The transaction has been rolled back
at weblogic.transaction.interna
Kindly try to see this Note:391651.1 on metalink
Essam -
Javax.transaction.SystemException: Exceeded maximum allowed transactions on
Hi,
I receive the following error when restarting weblogic server instance. Same error occurs when re-deploying the package.
I had previously deployed this package OK. Nothing has changed for the jar file it is complaining about.
I have restarted all java processes and even had the unix server restarted, however the same error comes up. I have no idea what to do.
Currently I have no application deployed as it fails every time. Nobody I know has seen this error or knows how to recover.
Please help!
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application NBAPP_1_10_2B on nbste_cluster.: weblogic.management.DeploymentException:
<b>Exception:weblogic.management.ApplicationException: activate failed for mca-ejbs.jar
Module: mca-ejbs.jar Error: Exception activating module: EJBModule(mca-ejbs.jar,status=PREPARED)
Unable to deploy EJB: eontec.bankframe.TransactionMetaData from mca-ejbs.jar:
[EJB:011007]Unable to create EJB Persistence Manager.
javax.transaction.SystemException: Exceeded maximum allowed transactions on server 'nbste_app1b_1'</b>
at weblogic.transaction.internal.ServerTransactionManagerImpl.createTransaction(ServerTransactionManagerImpl.java:1395)
at weblogic.transaction.internal.TransactionManagerImpl.internalBegin(TransactionManagerImpl.java:248)
at weblogic.transaction.internal.ServerTransactionManagerImpl.internalBegin(ServerTransactionManagerImpl.java:303)
at weblogic.transaction.internal.ServerTransactionManagerImpl.begin(ServerTransactionManagerImpl.java:259)
at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:248)
at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:210)
at weblogic.ejb20.manager.DBManager.setup(DBManager.java:162)
at weblogic.ejb20.manager.ROManager.setup(ROManager.java:109)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1057)
at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1362)
at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:631)
at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3274)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2173)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2146)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2434)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2352)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2136)
at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:676)
at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application NBAPP_1_10_2B on nbste_cluster.: weblogic.management.DeploymentException:
Exception:weblogic.management.ApplicationException: activate failed for mca-ejbs.jar
Module: mca-ejbs.jar Error: Exception activating module: EJBModule(mca-ejbs.jar,status=PREPARED)
Unable to deploy EJB: eontec.bankframe.TransactionMetaData from mca-ejbs.jar:
[EJB:011007]Unable to create EJB Persistence Manager.
javax.transaction.SystemException: Exceeded maximum allowed transactions on server 'nbste_app1b_2'
at weblogic.transaction.internal.ServerTransactionManagerImpl.createTransaction(ServerTransactionManagerImpl.java:1395)
at weblogic.transaction.internal.TransactionManagerImpl.internalBegin(TransactionManagerImpl.java:248)
at weblogic.transaction.internal.ServerTransactionManagerImpl.internalBegin(ServerTransactionManagerImpl.java:303)
at weblogic.transaction.internal.ServerTransactionManagerImpl.begin(ServerTransactionManagerImpl.java:259)
at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:248)
at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:210)
at weblogic.ejb20.manager.DBManager.setup(DBManager.java:162)
at weblogic.ejb20.manager.ROManager.setup(ROManager.java:109)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1057)
at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1362)
at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:631)
at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3274)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2173)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2146)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2434)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2352)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2136)
at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:676)
at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)<pre></pre><pre></pre>Hi All,
I am facing similar problem whne I try to deploy my Web part of the Application. I have JAR'ed the EJB's and that seems to get deployed properly only the web part is not getting loaded.
The following is the error message:
Exception:weblogic.management.ApplicationException: prepare failed for myWebApp
Module: annaweb Error: Could not load myWebApp: java.lang.NullPointerException
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2467)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2379)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for myWebApp
Module: annaweb Error: Could not load myWebApp: java.lang.NullPointerException
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2396)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
Have anyone faced similar problems, please let me know about the solution or suggestions.
Thanks in Advance.
- Jayashree
Edited by jayashree_kumar at 01/17/2007 10:09 AM -
EJB CMR relationship causes SystemException
I have two CMP entities called Employee and Department. I created a one-to-many relationship between them so many employees can belong to a department. I also created
a new ejbCreate() method that accepts a value object containing the employee details and the PK of the relevant department to create them in, which is a Long.
In my ejbCreate() method I set the fields of the Employee entity
In the ejbPostCreate() method, I lookup the relevant Department local home (which works fine), but on the following line where I do a home.findByPrimaryKey() passing in the correct Long value identifiying an existing employee I get the following:
'SystemException in the resource system.' is thrown during the execution of the findByPrimaryKey method, which causes a subsequent CreateException.
I've stepped through in the debugger but can't seem to find out the cause, and there is not much information from the message to follow up on.
Can anyone suggest an answer?
I've attached the stack dump below, and you will notice I have replaced my findByPrimaryKey() with findByDepartmentName(..) to see if it affected the result, but it still fails with the same problem. I know findByDepartmentName(..) works OK as I have exposed it as a web service and it functions as expected.
[code]com.sap.engine.services.ejb.exceptions.BaseEJBException: SystemException in the resource system.
at com.axonglobal.test.ejb.DepartmentLocalHomeImpl0.findByDepartmentName(DepartmentLocalHomeImpl0.java:920)
at com.axonglobal.test.ejb.Employee2Bean.ejbPostCreate(Employee2Bean.java:110)
at com.axonglobal.test.ejb.Employee2LocalHomeImpl0.create(Employee2LocalHomeImpl0.java:608)
at com.axonglobal.test.ejb.FacadeBean.createEmployee(FacadeBean.java:130)
at com.axonglobal.test.ejb.FacadeObjectImpl0.createEmployee(FacadeObjectImpl0.java:259)
at com.axonglobal.test.ejb.Facade_Stub.createEmployee(Facade_Stub.java:154)
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:324)
at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
at $Proxy76.createEmployee(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:146)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:68)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
at SoapServlet.doPost(SoapServlet.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceContextException: The last entered method is "Persistence_manager_methods_using_transactional_connection", but exit method is "com.axonglobal.test.ejb.DepartmentLocalHomeImpl0.findByDepartmentName(java.lang.String)".
at com.sap.engine.services.connector.resource.impl.ResourceContextImpl.exitMethod(ResourceContextImpl.java:124)
at com.axonglobal.test.ejb.DepartmentLocalHomeImpl0.findByDepartmentName(DepartmentLocalHomeImpl0.java:917)
... 36 more
com.sap.engine.services.connector.exceptions.BaseResourceContextException: The last entered method is "Persistence_manager_methods_using_transactional_connection", but exit method is "com.axonglobal.test.ejb.DepartmentLocalHomeImpl0.findByDepartmentName(java.lang.String)".
at com.sap.engine.services.connector.resource.impl.ResourceContextImpl.exitMethod(ResourceContextImpl.java:124)
at com.axonglobal.test.ejb.DepartmentLocalHomeImpl0.findByDepartmentName(DepartmentLocalHomeImpl0.java:917)
at com.axonglobal.test.ejb.Employee2Bean.ejbPostCreate(Employee2Bean.java:110)
at com.axonglobal.test.ejb.Employee2LocalHomeImpl0.create(Employee2LocalHomeImpl0.java:608)
at com.axonglobal.test.ejb.FacadeBean.createEmployee(FacadeBean.java:130)
at com.axonglobal.test.ejb.FacadeObjectImpl0.createEmployee(FacadeObjectImpl0.java:259)
at com.axonglobal.test.ejb.Facade_Stub.createEmployee(Facade_Stub.java:154)
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:324)
at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
at $Proxy76.createEmployee(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:146)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:68)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
at SoapServlet.doPost(SoapServlet.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)[/code]Hi Steve,
What is the SP number (or Patch Level) of your J2EE Engine?
Just a small hint: you can lookup the DepartmentLocalHome in the setEntityContext() method of EmployeeBean - this will boost performance as it'll be invoked only once per bean instance.
Best regards,
Vladimir -
Javax.transaction.SystemException: Timeout during commit processing
In my Workshop 8.1 SP2 project I have a Custom Java Control whose methods I call
from my JPF. From that custom control I create a remote connection to a Weblogic
6.1 Application server. I execute remote methods and get the expected objects
back with no problem. The problem is that I cannot return that object from my
custom control back to my jpf. As soon as the method's return statement is executed,
the process hangs for a considerable period of time and then throws the following
Exception:
An error has occurred:
Exception while commiting Tx : Name=[EJB com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.core.request.Request)],Xid=BEA1-0005BF0F3E6E72419698(655489),Status=Unknown,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=217,seconds left=42983,XAServerResourceInfo[BMResourceManager]=(ServerResourceInfo[BMResourceManager]=(state=new,assigned=none),xar=null),SCInfo[midway+cgServer]=(state=active),SCInfo[prdsdomain+prdsserver]=(state=active),properties=({weblogic.transaction.name=[EJB
com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.core.request.Request)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=cgServer+172.23.83.174:7001+midway+t3+,
XAResources={},NonXAResources={})],CoordinatorURL=prdsserver+172.23.4.109:7041+prdsdomain+t3+);
nested exception is:
javax.transaction.SystemException: Timeout during commit processing
Start server side stack trace:
javax.transaction.SystemException: Timeout during commit processing
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:243)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:189)
at weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68)
at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
caused by: : javax.transaction.SystemException: Timeout during commit processing
Start server side stack trace:
javax.transaction.SystemException: Timeout during commit processing
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:243)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:189)
at weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68)
at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
As soon as I take out RMI calls from my custom control's code, I can return any
object I want back to my JPF. Here is the what I am thinking is happenning.
The system that runs on Weblogic 6.1 manages its own transactions and begins a
new transaction every time a session bean residing on that server is invoked.
In addition, Weblogic 8.1 starts an internal transaction when the Custom Java
Control makes a call. Could there be some kind conflict? If yes, is it possible
to disable transactions from the Java Control?
Thank you very much
Alex Mayzlin
Horst,
"aa aa" <[email protected]> wrote in message news:20701457.1093414960276.JavaMail.root@jserv5...
> we are getting the same Exception. As nobody replied to your question, it would be interesting, if you found any solution
yourself?
>
> Additional info:
> We are also getting these error messages from BEA when testing connections in pool before and after the exception:
>
> <20.08.2004 19.32 Uhr CEST> <Error> <JDBC> <BEA-001112> <Test "SELECT count(*) FROM invoice" set up for pool "ABCConnection Pool"
failed with exception: "java.sql.SQLException: ORA-01591: lock held by in-doubt distributed transaction 4.47.141655".>
Generally it's a good idea to use Oracle's system DUAL table
for testing connections on reserve. Try to change your ABCConnection
connection pool configuration to use DUAL as the test table
instead of "invoice".
Regards,
Slava Imeshev
-
BEA-040498 SubCoordinator not available
Hello
I have a weblogic 9.2 MP3 cluster with two managed servers(OSManagedServer01 & OSManagedServer02) running on two different nodes. When my application tries to send a message to a distributed topic in this cluster I am getting the following error.
Has anybody came across this issue? Please help me if you have any clue. Both the servers are up and running and serving client requests.
+####<Nov 12, 2009 3:58:49 AM EST> <Warning> <JMS> <prod-app> <OSManagedServer01> <[STANDBY] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1258016329584> <BEA-040498> <An error occurred while forwarding a message for distributed destination member JMSSystemModule!OSJMSServer02@iCargoAutoRefreshTopic: weblogic.transaction.RollbackException: SubCoordinator 'OSManagedServer02+10.192.154.44:9511+OS.coreDomain+t3+' not available+
weblogic.transaction.RollbackException: SubCoordinator 'OSManagedServer0210.192.154.44:9511+OS.coreDomain+t3+' not available+
+ at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1809)+
+ at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:331)+
+ at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:227)+
+ at weblogic.jms.backend.BEForwardingConsumer.processMessages(BEForwardingConsumer.java:511)+
+ at weblogic.jms.backend.BEForwardingConsumer.pushMessages(BEForwardingConsumer.java:300)+
+ at weblogic.messaging.util.DeliveryList.run(DeliveryList.java:256)+
+ at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)+
+ at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)+
+ at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)+
Best Regards
user4661648Hi,
I think "Subcoordinator not available" is reported when a JTA transaction server (also known as a transaction manager, or TM) is unable to establish contact with another TM that's hosted by a different WL server in the same cluster.
I think this may be an indication that your cluster is not healthy -- e.g. the cluster servers are failing to share their JNDI name space. One way to check cluster health is to use the console to view the JNDI tree of each managed server in the cluster -- and check to see if the servers are managing to see JNDI resources advertised by other managed servers in the cluster (for example, every managed server should have JNDI entries for each member of the DT). Another way is to check for other errors and warnings in your logs.
If you also suspect that the cluster is unhealthy, I suggest reviewing the two cluster troubleshooting guides in the cluster documentation doc. Your are on version 9.2, but the troubleshooting guides in the 10.3 documentation are more up-to-date, so you may want to reference the 10.3 doc instead of the 9.2 doc.
Another possibility is that the remote TM (which is acting as a "subcoordinator"), is actually somehow having problems. If so, then I would assume that the WL server log of the remote TM host may yield more information.
Tom -
SystemException during Required -- RequiresNew Transaction Attribute
I have a batch process, which runs in RequiresNew Transaction Attribute (Child Transaction). My Parent transaction attribute is Required.
Say I am processing 10 Records, My requirement is in a normal flow, i need to commit each and every record after processing and incase Application Exception arises, i will log it and proceed with next record. So by that way i don't have any problem with Application Exception.
But when a systemException is thrown after processing 5 records, i will be able to rollback only the 6th record transaction, and the above commited 5 transactions cannot be rolledback. Can somebody suggest me a good solution to rollback all the transactions incase of SystemExceptions in RequiresNew
Thanks & Regards,
PrasannaHi
ThanX for your reply. I raised the issue to the BEA support, they said that the issue is the driver that i am using. It got resolved when i tried with the BEA provided driver. They call it the BEA branded driver for SQL Server.
Regards
Muthu -
Java.transaction.SystemException
How to replicate the below exceptions:
1. java.transaction.SystemException
2. javax.transaction.xa.XAException
Thanks in advance,
JaganHow to replicate the below exceptions:
1. java.transaction.SystemException
2. javax.transaction.xa.XAException
Thanks in advance,
Jagan
Maybe you are looking for
-
List of sales order with only open qty
Hello sap gurus,I am working in a support project for a leading cement manufacturer,I am facing a issue related to list of sales order only with remaining open quantities.In va05 transaction it gives the list of open sales orders,but if none of the l
-
Is there any way to create Eloqua made landing page mobile friendly?
I tried to add some css style in landing pages but it didn't work as desire.
-
Getting the values of a form (JSP, JavaScript involved)
Hi, basically I want to read the values from one page to another one, but I have found that when call the jsp from a javascript function it does not work!!! ... if I call the page "getValues.jsp" directly from the <form action>, everything works perf
-
Help! My application uses a Single Thread !
Hi all ! I have a web application which performs some long running tasks. This can be easily simulated with: protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { System.out.pr
-
Birthdays again/Exchange sync over-the-air
Hi all, I have a problem while I sync my contacts with Exchange 2007 over-the-air. Some contacts on iPhone have incorrect birthdays (they appear off by one day). The solution described here http://support.apple.com/kb/TS2456 doesn't work for me becau