Skip to content

JPA tests fail on wildfly #337

Open
Open

Description

@blabno
cd jpa/criteria
mvn test -P wildfly-embedded-arquillian
java.lang.RuntimeException: Could not create new instance of class org.jboss.arquillian.test.impl.EventTestRunnerAdaptor
        at org.jboss.arquillian.container.impl.client.container.ContainerRegistryCreator.createRegistry(ContainerRegistryCreator.java:116)

Activity

  1. bartoszmajsak commented on Dec 9, 2015

    @bartoszmajsak
    Contributor

    I'm afraid that's not the only one failing. I have a feeling the whole setup needs quite a bit of love, as it seems to me to be a bit of a shaky ground

  2. arjantijms commented on Dec 9, 2015

    @arjantijms
    Contributor

    What if you run against a remote Wildly (the project's default profile), and what if you run the tests from the root? (if needed comment out all modules except for the util and JPA in the main pom)

    I personally never got [cd somemodule/] to work to be honest.

  3. blabno commented on Dec 9, 2015

    @blabno
    ContributorAuthor

    @arjantijms default Wildfly works both from top dir and cd jpa/criteria.

  4. blabno commented on Dec 9, 2015

    @blabno
    ContributorAuthor

    Ok, so the reason for this error is lack of arquillian.xml with wildfly qualifier:

    <container qualifier="wildfly"></container>
    
  5. blabno commented on Dec 9, 2015

    @blabno
    ContributorAuthor

    This requirement was introduced in 5bb2f77

  6. blabno commented on Dec 9, 2015

    @blabno
    ContributorAuthor

    So either we add arquillian.xml with container with wildfly qualifier to each module
    or we remove this line:

    5bb2f77#diff-600376dffeb79835ede4a0b285078036R468

  7. blabno commented on Dec 9, 2015

    @blabno
    ContributorAuthor

    @johnament you've added that wildfly qualifier to global config when you were modifying jms-xa sample. I've tried running tests for it with your changes, but they fail so I have no idea how to test impact of reverting your change to global wildfly-embedded-arquillian profile.

  8. johnament commented on Dec 9, 2015

    @johnament
    Contributor

    I know the configuration is needed for the JMS stuff to work. I also know that when I made the change, it was based on some discussions we were having about trying to run a single container for the entire test suite. That proved to be not stable in both cloudbees and travis.

    I would recommend making this the default config overall (standalone-full.xml) but will leave it up to other to decide since I'm not particularly active on this project right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions