Uploaded image for project: 'JBoss Remoting (3+)'
  1. JBoss Remoting (3+)
  2. REM3-333

RemoteReadListener fails to invoke handler.handleChannelClosed on SERVICE_ERROR

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 5.0.10.Final
    • 5.0.9.Final
    • None

    Description

      If the error is recurring, eventually the limit of open channels is reached and we get org.jboss.remoting3.ProtocolException: Too many channels open:

      WARN jta 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.provider.remoting.RemotingRemoteTransactionPeer.getOperationsXA(RemotingRemoteTransactionPeer.java:139)
  at org.wildfly.transaction.client.provider.remoting.RemotingRemoteTransactionPeer.recover(RemotingRemoteTransactionPeer.java:202)
  at org.wildfly.transaction.client.SubordinateXAResource.recover(SubordinateXAResource.java:201)
  at org.wildfly.transaction.client.SubordinateXAResource.recover(SubordinateXAResource.java:197)
  at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoveryFirstPass(XARecoveryModule.java:609)
  at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:201)
  at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:146)
  at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:765)
  at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377)
Caused by: org.jboss.remoting3.ProtocolException: Too many channels open
  at org.jboss.remoting3.remote.RemoteConnectionHandler.handleOutboundChannelOpen(RemoteConnectionHandler.java:194)
  at org.jboss.remoting3.remote.RemoteConnectionHandler.open(RemoteConnectionHandler.java:335)
  at org.jboss.remoting3.ConnectionImpl.openChannel(ConnectionImpl.java:109)
  at org.jboss.remoting3.ClientServiceHandle.getClientService(ClientServiceHandle.java:80)
  at org.wildfly.transaction.client.provider.remoting.TransactionClientChannel.forConnection(TransactionClientChannel.java:507)
  at org.wildfly.transaction.client.provider.remoting.RemotingRemoteTransactionPeer.getOperations(RemotingRemoteTransactionPeer.java:106)
  at org.wildfly.transaction.client.provider.remoting.RemotingRemoteTransactionPeer.getOperationsXA(RemotingRemoteTransactionPeer.java:137)
  ... 8 more

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-16782 [GSS](7.2.z) REM3-333 - XARecoveryModule.xaRecoveryFirstPass getting org.jboss.remoting3.ProtocolException: Too many channels open

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFCORE-4491 Upgrade jboss-remoting to 5.0.12.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              flaviarnn Flavia Rainone
              flaviarnn Flavia Rainone
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: