Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-830

CLONE -EJB3 testsuite failures

    XMLWordPrintable

Details

    Description

      This issue will be used to track the failures in the ejb3 testsuite.

      Intermittant issues seen in latest 4.2.0.GA_CP0x runs:
      org.jboss.ejb3.test.clusteredsession.unit.NestedBeanUnitTestCase(BR-enabled)#testStatefulPassivation
      org.jboss.ejb3.test.ejbthree994.unit.MultiBindingsTestCase#test1

      Intermittant issues seen in latest 4.3.0.GA_CP0x runs:
      org.jboss.ejb3.test.clusteredsession.unit.NestedBeanUnitTestCase(BR-enabled)#testStatefulPassivation
      org.jboss.ejb3.test.clusteredjms.unit.MDBUnitTestCase#testQueue
      org.jboss.ejb3.test.ejbthree994.unit.MultiBindingsTestCase#test1
      org.jboss.ejb3.test.bank.unit.BankDeploymentDescriptorTestCase#testStatefulTransactionTimeout
      org.jboss.ejb3.test.jbas4489.unit.BMTCleanUpUnitTestCase.testTxTimeout

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. JBPAPP-416 QE blockers for EAP4.3

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is blocked by

          Feature Request - Feature requests from customers and/or users JBPAPP-457 Allow configuration of known issues

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-456 jms server failover with tibco ems

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Support Patch - A one-off patch related to a customer support case, provided by Support and not Engineering JBPAPP-387 jms server failover with tibco ems

          • 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
          is related to

          Sub-task - The sub-task of the issue EJBTHREE-1741 Address testsuite failures

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-578 correct EJB3 regression test failures

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Activity

            People

              jpkroehling@redhat.com Juraci Paixão Kröhling (Inactive)
              rrajasek@redhat.com Rajesh Rajasekaran
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: