Message Driven bean not able to listen to IBM MQ

Question

Hello,
          I am trying to implement a Mesage Driven Bean on Weblogic 7.0.This MDB
          would listen on a particular queue of IBM MQ.
          I have written a Weblogic startUp class which registers the factory
          into Weblogic JNDI.Am I supposed to register the queue as well? I am
          confused about the queue part. In the deployement descriptor of the
          MDB (weblogic-ejb-jar.xml), we have the the <destination-jndi-name>
          tag which should be the Queue name (in my case the IBM MQ queue ). Am
          I supposed to register that in the Weblogic JNDI as well? I mean do I
          add the Queue part in my Weblogic start-up class as well? Else how
          will The Queue be obtained?
          I am sort of confused on this . I get the error :
          <Apr 16, 2003 3:17:14 PM EDT> <Warning> <EJB> <010061> <The
          Message-Driven EJB: SimpleMDB is unable
          to connect to the JMS destination: ivtQ. The EJB container will
          automatically attempt to re-establis
          h the connection with the JMS server. This warning may occur during
          WebLogic Cluster start-up if the
          JMS destination is located on another server. When the JMS server
          connection is re-established, the
          Message-Driven EJB will again receive JMS messages.
          The Error was:
          The JMS destination with the JNDI name: ivtQ could not be found.
          Please ensure that the JNDI name in
          the weblogic-ejb-jar.xml is correct, and the JMS destination has been
          deployed.>
          Please guide .I am trying to find out this information(which isn`t
          very difficult i think ) since quite a few days now but I have got no
          reply whatsoever.Please let me know if I am posting in the wrong group
          or should I place my query in some other group where I can get a
          better response.
          Thanks and regards,
          Milan Doshi
          

Answer 1

I'm not familiar with this stuff, but Greg is out, so
          hey, I'll give it a shot. Some random thoughts:
          It seems odd that the MDB can find the factory in JNDI but
          not the queue.
          Make sure that the startup class is actually running the code
          you think it is. Put println's before and after the queue binding
          code. And as the white-paper suggests, use the "failure is
          fatal" option for the startup class so that you know
          if the class worked or not...
          Put some trace code in the ignored "NumberFormatException" catch below.
          Carefully check you log to see if there are other warnings or errors.
          Note that you may wish to use MQ JNDI instead of createQueue
          in the startup class to look up the queue. The "createQueue()"
          will not necessarily return an object that is JNDI "capable", (vendor
          specific)... If this is the case, then you will need to
          write a "wrapper" class that implements Serializable but
          finds its wrapped factory via some sort of static lookup.
          Tom, BEA
          P.S. Note that WebLogic 8.1 provides the ability
          to "wrap" and deploy foreign JMS resources administratively
          via the console. No startup class needed...
          Milan Doshi wrote:
          > Thanks for the response.
          >
          > I have written the startUp class but I am getting the following error:
          >
          > The Error was:
          > The JMS destination with the JNDI name: MySenderQueue could not be
          > found. Please ensure that the
          > JNDI name in the weblogic-ejb-jar.xml is correct, and the JMS
          > destination has been deployed.>
          >
          > =====
          >
          > My startup class is as follows:
          >
          > String qmPort = (String)args.get(QM_PORT_PROPERTY);
          > String qmHost = (String)args.get(QM_HOST_PROPERTY);
          > String qmName = (String)args.get(QM_NAME_PROPERTY);
          >
          > MQQueueConnectionFactory factory = new MQQueueConnectionFactory();
          >
          > factory.setQueueManager(qmName);
          > factory.setHostName(qmHost);
          > if (qmPort != null)
          > {
          > try
          > {
          > int portNum = Integer.parseInt(qmPort);
          > factory.setPort(portNum);
          > }
          > catch (NumberFormatException ignore)
          > {
          >
          > }
          > }
          > if (qmHost == null)
          > {
          > factory.setTransportType(JMSC.MQJMS_TP_BINDINGS_MQ);
          >
          >
          > }
          > else
          > {
          > factory.setTransportType(JMSC.MQJMS_TP_CLIENT_MQ_TCPIP);
          > }
          >
          > InitialContext context = new InitialContext();
          > context.bind(jndiName, factory);
          >
          > QueueConnection connection = factory.createQueueConnection();
          > boolean transacted = false;
          > QueueSession session = connection.createQueueSession( transacted,
          > Session.AUTO_ACKNOWLEDGE);
          > Queue ioQueue = session.createQueue("MySenderQueue");
          >
          > context.bind("MySenderQueue",ioQueue);
          > context.close();
          >
          >
          > ===================================================
          >
          > My Weblogic-ejb-jar.xml is like this:
          >
          > <weblogic-ejb-jar>
          > <weblogic-enterprise-bean>
          > <ejb-name>SimpleMDB</ejb-name>
          > <message-driven-descriptor>
          > <pool>
          > <max-beans-in-free-pool>8</max-beans-in-free-pool>
          > <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
          > </pool>
          > <destination-jndi-name>MySenderQueue</destination-jndi-name>
          > <connection-factory-jndi-name>
          > MyQCF
          > </connection-factory-jndi-name>
          > </message-driven-descriptor>
          > </weblogic-enterprise-bean>
          > </weblogic-ejb-jar>
          >
          > ======================================================
          >
          > Can you please guide me what is wrong in registering the Queue?
          >
          > Thanks once again for the response,
          >
          > Milan Doshi
          >
          >
          > "Greg Brail" <[email protected]> wrote in message news:<[email protected]>...
          >
          >>You don't have to use a startup class to do this unless you want to. If you
          >>use IBM's "JMSAdmin" tool to register the MQ connection factory and
          >>destination objects into a JNDI provider, then you need only specify the
          >>right JNDI stuff in weblogic-ejb-jar.xml. You might want to look at the
          >>white paper for more information on exactly how to do this:
          >>
          >>http://dev2dev.bea.com/resourcelibrary/whitepapers/jmsproviders.jsp
          >>
          >>However, there might be reasons to use the startup class anyway. With the
          >>startup class, you don't have to mess with a JNDI provider for MQ. The white
          >>paper also contains a sample startup class.
          >>
          >>If you do this with a startup class, you do indeed need to bind BOTH the
          >>MQSeries ConnectionFactory and Queue objects into WebLogic JNDI. You then
          >>need to make the MDB use those particular objects (the ones you created in
          >>the startup class) for both the connection factory and the queue. The
          >>resulting weblogic-ejb-jar.xml file would look like this:
          >>
          >><weblogic-ejb-jar>
          >> <weblogic-enterprise-bean>
          >> <ejb-name>YourMDBName</ejb-name>
          >> <message-driven-descriptor>
          >> <pool>
          >> <max-beans-in-free-pool>8</max-beans-in-free-pool>
          >> <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
          >> </pool>
          >> <destination-jndi-name>
          >> YourQueueNameFromTheStartupClass
          >> </destination-jndi-name>
          >> <connection-factory-jndi-name>
          >> ConnectionFactoryNameFromTheStartupClass
          >> </connection-factory-jndi-name>
          >> </message-driven-descriptor>
          >> </weblogic-enterprise-bean>
          >></weblogic-ejb-jar>
          >>
          >>Hope this helps.
          >>
          >> greg
          >>
          >>"Milan Doshi" <[email protected]> wrote in message
          >>news:[email protected]...
          >>
          >>>Hello,
          >>>
          >>>I am trying to implement a Mesage Driven Bean on Weblogic 7.0.This MDB
          >>>would listen on a particular queue of IBM MQ.
          >>>
          >>>I have written a Weblogic startUp class which registers the factory
          >>>into Weblogic JNDI.Am I supposed to register the queue as well? I am
          >>>confused about the queue part. In the deployement descriptor of the
          >>>MDB (weblogic-ejb-jar.xml), we have the the <destination-jndi-name>
          >>>tag which should be the Queue name (in my case the IBM MQ queue ). Am
          >>>I supposed to register that in the Weblogic JNDI as well? I mean do I
          >>>add the Queue part in my Weblogic start-up class as well? Else how
          >>>will The Queue be obtained?
          >>>
          >>>I am sort of confused on this . I get the error :
          >>>
          >>><Apr 16, 2003 3:17:14 PM EDT> <Warning> <EJB> <010061> <The
          >>>Message-Driven EJB: SimpleMDB is unable
          >>>to connect to the JMS destination: ivtQ. The EJB container will
          >>>automatically attempt to re-establis
          >>>h the connection with the JMS server. This warning may occur during
          >>>WebLogic Cluster start-up if the
          >>> JMS destination is located on another server. When the JMS server
          >>>connection is re-established, the
          >>> Message-Driven EJB will again receive JMS messages.
          >>>The Error was:
          >>>The JMS destination with the JNDI name: ivtQ could not be found.
          >>>Please ensure that the JNDI name in
          >>> the weblogic-ejb-jar.xml is correct, and the JMS destination has been
          >>>deployed.>
          >>>
          >>>Please guide .I am trying to find out this information(which isn`t
          >>>very difficult i think ) since quite a few days now but I have got no
          >>>reply whatsoever.Please let me know if I am posting in the wrong group
          >>>or should I place my query in some other group where I can get a
          >>>better response.
          >>>
          >>>Thanks and regards,
          >>>
          >>>Milan Doshi
          >>