Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-10655

Re-enable tests temporarily disabled in -Delytron run.

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Blocker Blocker
    • 7.1.0.ER2
    • None
    • Security, Test Suite
    • None

      The following tests are temporarily ignored: -

      Tests in error:
      ExportImportJournalTestCase.testExportImportJournal:136->sendMessage:77 » Communication
      JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to...
      JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to...
      JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to...
      JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to...
      JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to...
      JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to...
      JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to...
      JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to...
      JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to...
      JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to...
      JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to...
      JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con...
      JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con...
      JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con...
      JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con...
      JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con...
      JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con...
      JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con...
      JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con...
      JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con...
      JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con...
      JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con...
      JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con...
      JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con...
      JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con...
      PooledConnectionFactoryStatisticsTestCase.testStatistics:83 » Communication WF...
      RemoteNamingEjbTestCase.testDeploymentBinding:140 » Communication WFNAM00018: ...
      RemoteNamingEjbTestCase.testIt:99 » Communication WFNAM00018: Failed to connec...
      RemoteNamingTestCase.testNestedLookup:109 » Communication WFNAM00018: Failed t...
      RemoteNamingTestCase.testRemoteContextLookup:97 » Communication WFNAM00018: Fa...
      RemoteNamingTestCase.testRemoteLookup:85 » Communication WFNAM00018: Failed to...
      TransactionInflowTestCase.inflowTransactionCommit:138 » IllegalState EJBCLIENT...
      TransactionInflowTestCase.inflowTransactionRollback:156 » IllegalState EJBCLIE...

      Investigation needs to continue as it actually appears something running before these tests is the cause as running these tests in isolation does not cause a failure.

              jkalina@redhat.com Jan Kalina (Inactive)
              darran.lofthouse@redhat.com Darran Lofthouse
              Josef Cacek Josef Cacek (Inactive)
              Josef Cacek Josef Cacek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: