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

Arquillian test with asynchronous components (Asynchonous EJB or JMS) in glassfish -embedded

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 1.0.0.Alpha5
    • None
    • GlassFish Containers
    • None
    • Hide

      Inject in the test and EJB which call another one asynchronously.
      In the async EJB, call still another one EJB : it fails because container is stopped or undeployed.

      Show
      Inject in the test and EJB which call another one asynchronously. In the async EJB, call still another one EJB : it fails because container is stopped or undeployed.

    Description

      When we use Asynchronous EJB or MDB with JMS in our tests, the test leave and it seems the container is undeployed or something ...
      It results in async always running code complaining about undeployed or stopped container for subsequents EJB calls and so on ...
      Am I wrong ?

      Attachments

        Activity

          People

            Unassigned Unassigned
            kabhal_jira Hugo de Paix de Coeur (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: