Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-11670

Intermittent failures in EJBClientXidTransactionTestCase.testServerSuspension

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 16.0.0.Beta1, 16.0.0.Final
    • None
    • EJB
    • None

    Description

      Test started failing fairly frequently on Jan 11:

      https://ci.wildfly.org/project.html?projectId=WildFlyCore_PullRequest&buildTypeId=&tab=testDetails&testNameId=671487653311897791&order=TEST_STATUS_DESC&branch_WildFlyCore_PullRequest=__all_branches__&itemsCount=50

      https://ci.wildfly.org/project.html?projectId=WF&buildTypeId=&tab=testDetails&testNameId=671487653311897791&order=TEST_STATUS_DESC&branch_WF=__all_branches__&itemsCount=50

      Perhaps that was related to https://github.com/wildfly/wildfly/pull/11913 which at a glance was the PR being tested in the first failure and may have been merged that day. So, yborgess1@redhat.com I'm assigning to you to have a quick look.

      I'll @Ignore the test.

      For the record, this is the relevant error trace logged by the failed tests:

      multinode.transaction.ClientEjb.testSameTransactionEachCall() throws java.rmi.RemoteException,javax.transaction.SystemException,javax.transaction.NotSupportedException,javax.naming.NamingException: javax.ejb.EJBException: EJBCLIENT000082: Cannot outflow the remote transaction "Local transaction (delegate=TransactionImple < ac, BasicAction: 0:ffff7f000101:-39b44114:5c59a6ad:10 status: ActionStatus.RUNNING >, owner=Local transaction context for provider JBoss JTA transaction provider)" as its timeout elapsed
	at org.jboss.ejb.protocol.remote.EJBClientChannel.processInvocation(EJBClientChannel.java:471)
	at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.lambda$handleDone$0(RemoteEJBReceiver.java:91)
	at org.xnio.FinishedIoFuture.addNotifier(FinishedIoFuture.java:79)
	at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.handleDone(RemoteEJBReceiver.java:76)
	at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.handleDone(RemoteEJBReceiver.java:74)
	at org.xnio.IoFuture$HandlingNotifier.notify(IoFuture.java:208)
	at org.xnio.AbstractIoFuture$NotifierRunnable.run(AbstractIoFuture.java:720)
	at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:949)
	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
	at java.lang.Thread.run(Thread.java:748)
Caused by: javax.transaction.SystemException: EJBCLIENT000082: Cannot outflow the remote transaction "Local transaction (delegate=TransactionImple < ac, BasicAction: 0:ffff7f000101:-39b44114:5c59a6ad:10 status: ActionStatus.RUNNING >, owner=Local transaction context for provider JBoss JTA transaction provider)" as its timeout elapsed
	at org.jboss.ejb.protocol.remote.EJBClientChannel.writeTransaction(EJBClientChannel.java:581)
	at org.jboss.ejb.protocol.remote.EJBClientChannel.processInvocation(EJBClientChannel.java:367)
	... 12 more

      Attachments

        Issue Links

          is blocked by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-11570 Upgrade wildfly-transaction-client from 1.1.2.Final to 1.1.3.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.
          • Closed
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. WFTC-60 SubordinateXAResource#getRemainingTime is not calculating the remaining time correctly

          • 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

              yborgess1@redhat.com Yeray Borges Santana
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: