[jboss-jira] [JBoss JIRA] (WFLY-1560) PartialObjectActivationJarTestCase fails if ran after any of InflowFlatTestCase or TwoModulesOfDifferentTypeTestCase

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790000#comment-12790000 ] 

RH Bugzilla Integration commented on WFLY-1560:
-----------------------------------------------

Ivo Studensky <istudens at redhat.com> changed the Status of [bug 985003|https://bugzilla.redhat.com/show_bug.cgi?id=985003] from NEW to ASSIGNED
                
> PartialObjectActivationJarTestCase fails if ran after any of InflowFlatTestCase or TwoModulesOfDifferentTypeTestCase
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-1560
>                 URL: https://issues.jboss.org/browse/WFLY-1560
>             Project: WildFly
>          Issue Type: Bug
>          Components: Test Suite
>    Affects Versions: 8.0.0.Alpha1
>            Reporter: Ivo Studensky
>            Assignee: Ivo Studensky
>         Attachments: server_log_snippet.txt
>
>
> PartialObjectActivationJarTestCase fails if it runs after InflowFlatTestCase.  It seems that the {{inflow2}} resource adapter is not fully unregistered by InflowFlatTestCase before PartialObjectActivationJarTestCase begins to start its own RA.
> Here is the server log snippet (DEBUG level):
> http://pastebin.test.redhat.com/147968
> Line 10 of this snippet corresponds to the invocation of {{setConfiguration("basic.xml");}} in PartialObjectActivationJarTestCase. Then, the server is apparently trying to activate {{MultipleConnectionFactory2Impl}} and {{MultipleAdminObject2Impl}} even though these are not involved in {{basic.xml}} of PartialObjectActivationJarTestCase at all. A suspicious exception is on line 19 there. 
> I tried to put some delay between {{remove(address);}} and {{removeModule(defaultPath);}} in {{AbstractModuleDeploymentTestCaseSetup#tearDown()}} but it did not help. I also tried to put {{@Ignore}} to both test methods in the InflowFlatTestCase which also did not help, so it is evidently related only to the RA deployment/undeployment.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira