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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.0.0.Alpha5
    • Fix Version/s: None
    • Component/s: GlassFish Containers
    • Labels:
      None
    • Environment:

      arquillian-glassfish-embedded-3.1, arquillian-junit-1.0.0.Alpha5

    • Steps to Reproduce:
      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 ?

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                kabhal Hugo de Paix de Coeur
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: