Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-5213

Injecting external context to Artemis fails

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 10.0.0.CR1
    • 10.0.0.Beta2
    • JMS
    • None
    • Hide

      1)Run standalone ActiveMQ Artemis broker with InQueue and OutQueue
      2)Send message to InQueue
      3)Create external-context in EAP and pooled CF pointing to external broker
      4)Deploy MDB which reads messages from InQueue on external broker and forwards them to OutQueue. Using external-context.
      Result: You can't make JNDI lookup due to null external-context

      Show
      1)Run standalone ActiveMQ Artemis broker with InQueue and OutQueue 2)Send message to InQueue 3)Create external-context in EAP and pooled CF pointing to external broker 4)Deploy MDB which reads messages from InQueue on external broker and forwards them to OutQueue. Using external-context. Result: You can't make JNDI lookup due to null external-context

    Description

      When external-context is defined in EAP and it's pointing to external Artemis broker, it can't be injected in to MDB via @Resource(lookup = "java:global/externalcontext"). Such injection results in null object.
      Injecting destinations from external context results in javax.ejb.EJBTransactionRolledbackException.

      Attachments

        Issue Links

          Activity

            People

              jmesnil1@redhat.com Jeff Mesnil
              okalman@redhat.com Ondřej Kalman (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: