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

Jesper Pedersen (JIRA) jira-events at lists.jboss.org
Wed Jun 19 08:11:20 EDT 2013


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

Jesper Pedersen reassigned WFLY-1560:
-------------------------------------

    Assignee: Stefano Maestri  (was: Jesper Pedersen)

    
> 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: JCA, Test Suite
>    Affects Versions: 8.0.0.Alpha1
>            Reporter: Ivo Studensky
>            Assignee: Stefano Maestri
>
> 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. Do you have any idea what it could mean?
> 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


More information about the jboss-jira mailing list