6:11 a.m.
[
https://issues.jboss.org/browse/WFLY-12090?page=com.atlassian.jira.plugin...
]
Ondrej Chaloupka edited comment on WFLY-12090 at 5/21/19 7:10 AM:
------------------------------------------------------------------
[~tomjenkinson] yes, I think both option are possible but maybe not so easy to implement.
If there is a way to define a service dependency tree then IMHO it's easier. But it
depends on if it's possible.
[~flavia.rainone] I'm searching the code a bit (the dependencies are a bit complex
thus I could be missing details) but the EJBRemotingService depends on the txn remote
service but not on the recovery service, doesn't it? I mean having the dependency tree
like
{code}
+----------+
| |
+ v
EJB service TXN Service
^ ^
| | (R.S. is depending on TXN S.)
+ +
Recovery Service
{code}
in case you appreciate it I can try to research on this a bit more?
was (Author: ochaloup):
[~tomjenkinson] yes, I think both option are possible but maybe not so easy to implement.
If there is a way to define a service dependency tree then IMHO it's easier. But it
depends on if it's possible.
[~flavia.rainone] I'm searching the code a bit (the dependencies are a bit complex
thus I could be missing details) but the EJBRemotingService depends on the txn remote
service but not on the recovery service, doesn't it? I mean having the dependency tree
like
{code}
+----------+
| |
+ v
EJB service TXN Service
^ ^
| | (R.S. depends on TXN S.)
+ +
Recovery Service
{code}
in case you appreciate it I can try to research on this a bit more?
Unknown service name jboss.ejb and txn
--------------------------------------
Key: WFLY-12090
URL: https://issues.jboss.org/browse/WFLY-12090
Project: WildFly
Issue Type: Bug
Components: EJB, Transactions
Affects Versions: 17.0.0.Alpha1
Reporter: Flavia Rainone
Assignee: Flavia Rainone
Priority: Major
Fix For: 17.0.0.Beta1
When EJBRemoting service is not started (it is LAZY), but XA recovery has, we could have
the following sort of error:
{code}
16:51:46,785 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local
XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR:
javax.transaction.xa.XAException: WFTXN0034: Failed to acquire a connection for this
operation
at
org.wildfly.transaction.client@1.1.3.Final//org.wildfly.transaction.client.provider.remoting.RemotingRemoteTransactionPeer.getOperationsXA(RemotingRemoteTransactionPeer.java:139)
at
org.wildfly.transaction.client@1.1.3.Final//org.wildfly.transaction.client.provider.remoting.RemotingRemoteTransactionPeer.recover(RemotingRemoteTransactionPeer.java:202)
at
org.wildfly.transaction.client@1.1.3.Final//org.wildfly.transaction.client.SubordinateXAResource.recover(SubordinateXAResource.java:201)
at
org.wildfly.transaction.client@1.1.3.Final//org.wildfly.transaction.client.SubordinateXAResource.recover(SubordinateXAResource.java:197)
at
org.jboss.jts//com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoveryFirstPass(XARecoveryModule.java:634)
at
org.jboss.jts//com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:226)
at
org.jboss.jts//com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:171)
at
org.jboss.jts//com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:770)
at
org.jboss.jts//com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:382)
Caused by: org.jboss.remoting3.ServiceOpenException: Unknown service name jboss.ejb
at
org.jboss.remoting@5.0.10.Final-SNAPSHOT//org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:429)
at
org.jboss.remoting@5.0.10.Final-SNAPSHOT//org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:46)
at
org.jboss.xnio@3.7.2.Final-SNAPSHOT//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
at
org.jboss.xnio@3.7.2.Final-SNAPSHOT//org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
at
org.jboss.xnio.nio@3.7.2.Final-SNAPSHOT//org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
at
org.jboss.xnio.nio@3.7.2.Final-SNAPSHOT//org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
Suppressed: org.jboss.remoting3.ServiceOpenException: Unknown service name txn
... 6 more
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
2623
days inactive
2623
days old
0 comments
1 participants
participants (1)
-
Ondrej Chaloupka (Jira)