Uploaded image for project: 'Arquillian'
  1. Arquillian
  2. ARQ-1964

OperateOnDeployment not honored when using the JMX Protocol

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 1.1.8.Final
    • None
    • None
    • Hide

      The test org.hibernate.search.test.integration.jms.transaction.TransactionalJmsMasterSlaveUsingModulesIT in https://github.com/hibernate/hibernate-search/ is able to reproduce this - just switch the protocol back to jmx-as7 and it will fail.

      Show
      The test org.hibernate.search.test.integration.jms.transaction.TransactionalJmsMasterSlaveUsingModulesIT in https://github.com/hibernate/hibernate-search/ is able to reproduce this - just switch the protocol back to jmx-as7 and it will fail.

      I was using protocol type jmx-as7 to run tests on WildFly 9.0.0.Final, using
      1.1.8.Final of Arquillian, and having the wildfly components aligned with the same versions I've found in WildFly 9's source code.

      It seems like a random deployed is chosen, and all tests in the same class are run on that same deployment rather than on the ones I'm specifying with @OperateOnDeployment.

      Switching to protocol Servlet 3.0 seems to workaround the problem.

              Unassigned Unassigned
              sgrinove Sanne Grinovero (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: