Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-9229

EJB 2.1 compliant MDBs don't consume messages

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • EAP_EWP 5.1.2
    • HornetQ
    • HornetQ-2.2.10-B2-JBPAPP-8396 (HQ_2_2_10_EAP_GA_JBPAPP-8396-v4, 12) , JBoss-EAP-5.1.2

    • Hide
      • Please prepare a system which runs Windows 7
      • Install JBoss-EAP-5.1.2, integrate HornetQ and apply JBPAPP-8396 patch
      • Please select the "production" server profile
      • Set in "security-enabled" attribute to "false" in deploy\hornetq\hornetq-configuration.xml file :
        <security-enabled>false</security-enabled>
      • Delete the "data" directory
      • Create a destination "queue/A" :
        <queue name="A">
        <entry name="/queue/A"/>
        </queue>
      • Deploy the EJB 2.1 compliant MDB
      • Start the server
      • Send a couple of text messages to the configured destination "queue/A"
      • The MDB won't consume any messages
      Show
      Please prepare a system which runs Windows 7 Install JBoss-EAP-5.1.2, integrate HornetQ and apply JBPAPP-8396 patch Please select the "production" server profile Set in "security-enabled" attribute to "false" in deploy\hornetq\hornetq-configuration.xml file : <security-enabled>false</security-enabled> Delete the "data" directory Create a destination "queue/A" : <queue name="A"> <entry name="/queue/A"/> </queue> Deploy the EJB 2.1 compliant MDB Start the server Send a couple of text messages to the configured destination "queue/A" The MDB won't consume any messages
    • Compatibility/Configuration
    • NEW

      The EJB-2.1 spec compliant MDBs don't consume messages although they're successfully deployed

            csuconic@redhat.com Clebert Suconic
            rhn-support-tywickra Tyronne Wickramarathne
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: