[jboss-jira] [JBoss JIRA] (WFLY-9318) Some EJB tests are ignored because they are incompatible with SLSB pooling

Jan Martiska (JIRA) issues at jboss.org
Fri Sep 8 02:34:05 EDT 2017


     [ https://issues.jboss.org/browse/WFLY-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Martiska moved JBEAP-13065 to WFLY-9318:
--------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-9318  (was: JBEAP-13065)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Test Suite
                           (was: Test Suite)
    Affects Version/s:     (was: 7.1.0.CR1)


> Some EJB tests are ignored because they are incompatible with SLSB pooling
> --------------------------------------------------------------------------
>
>                 Key: WFLY-9318
>                 URL: https://issues.jboss.org/browse/WFLY-9318
>             Project: WildFly
>          Issue Type: Task
>          Components: Test Suite
>            Reporter: Jan Martiska
>            Assignee: Jan Martiska
>            Priority: Minor
>
> This affects:
> {{EjbRemoveUnitTestCase.testEjbRemoveCalledForEveryCall}}: https://github.com/jbossas/jboss-eap7/blob/EAP_7.1.0.CR1-dev/testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/ejb/stateless/pooling/ejb2/EjbRemoveUnitTestCase.java#L126
> {{LifecycleTestCase.testStatelessBeanLifecyleCallback}}: https://github.com/jbossas/jboss-eap7/blob/EAP_7.1.0.CR1-dev/testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/ejb/security/LifecycleTestCase.java#L163
> We should decide what to do with 'em. Options:
> - fix them by applying the necessary config changes - explicitly disable SLSB pooling before the test 
> - remove them
> My vote is for removing them, for two reasons:
> - disabling SLSB pooling does not quite seem a real-world reasonable use case for me, so the benefit from having these tests is quite poor
> - the needed config change requires server reload, which slows down the TS execution and has been known to cause instabilities



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jboss-jira mailing list