Upgrade to MQ 5.3 causing issues

Question

We have been using the alpha code for 'MQ Series JMS Support' for the last
          18 months or so without any issues on WLS 6.0 first and then WLS 6.1.
          The runtime is still available at
          http://dev2dev.bea.com/codelibrary/code/mqseries.jsp
          While I understand that this is Alpha code and not officially supported by
          Bea, can someone please try to help me with the below issues ?
          We are doing an upgrade from MQ Series 5.2 to 5.3 or are suddenly seeing the
          infamous 'NoClassDefFoundError' on one of the XA classes. I think I may
          know what's going on but have no way to fix the problem. The
          wlsmqseries.jar was built using the MQ Series 5.2 libraries. Since we are
          upgrading to MQ Series 5.3 the classes in wlsmqseries.zip need to be rebuilt
          using the new APIs (I am pretty sure there are no API changes). Is it
          possible that the contributor of this utility (if reading this email) build
          wlsmqseries.jar using the MQ Series 5.3 libraries and release it. Or
          alternatively, I'll be happy to do the build if the source is given. Most
          of the stuff in the dev2dev site has code included. This one seems to be
          one of the few that doesn't have code.
          Note - Upgrading to WLS 7.0 or 8.1 is not an option for another 6 months :(
          Help ! Please !
          Adarsh
          

Answer 1

Alex,
          I was wrong on the analysis. The problem vanished after I included the MQ
          libraries in my library path. I am now able to do XA transactions with the
          MQ Series 5.3 Queue Manager without any issues (ofcourse, using your
          wrappers).
          I apologize for the false alarm :)
          Thanks for your immediate response,
          Adarsh
          "Alex" <[email protected]> wrote in message
          news:[email protected]...
          > What is the XA class that gets the NoClassDefFoundError?
          >
          > Adarsh Dattani wrote:
          >
          > > Hi Alex,
          > > The error trace points to the one of the two #### lines of code. This
          > > happens after the entries in LDAP are duplicated onto WLS JNDI by the
          mapper
          > > and when I try to create a queue connection after looking up the QCF
          from
          > > the WLS JNDI.
          > > Thanks,
          > > Adarsh
          > >
          > > JNDIMapper mapper = null;
          > > Context ctx = new InitialContext();
          > > try {
          > > String wlsMqQcf = qcfName+"_WLS";
          > > String wlsMqQueue = queueName+".WLS";
          > > try {
          > > mapper = new JNDIMapper(icfName,url);
          > > } catch (javax.naming.NameAlreadyBoundException nabe) {}
          > > try {
          > >
          > > mapper.map("cn="+qcfName,wlsMqQcf,"MQSeries."+queueName);
          > > } catch (javax.naming.NameAlreadyBoundException nabe) {}
          > > mapper.map("cn="+queueName,wlsMqQueue);
          > > }
          > > #### qconFactory =
          (QueueConnectionFactory)ctx.lookup(wlsMqQcf);
          > > #### qcon = (QueueConnection)
          > > ((XAQueueConnectionFactory)qconFactory).createXAQueueConnection();
          > > XAsession =
          ((XAQueueConnection)qcon).createXAQueueSession();
          > > qsession = XAsession.getQueueSession();
          > > } catch(JMSException je) {
          > > Exception linked = je.getLinkedException();
          > > if (linked!=null) {
          > > log.error("MQ Series Linked Exception for the following JMS
          > > Exception : "+linked.toString());
          > > }
          > > throw new EbizException(je);
          > > } catch (NamingException ne) {
          > > throw new EbizException(ne);
          > > } catch (Throwable te) {
          > > throw new EbizException(te);
          > > }
          > >
          > >
          > >
          > > "Alex" <[email protected]> wrote in message
          > > news:[email protected]...
          > >
          > >>What is the offending class?
          > >>
          > >>Adarsh Dattani wrote:
          > >>
          > >>
          > >>>We have been using the alpha code for 'MQ Series JMS Support' for the
          > >>>
          > > last
          > >
          > >>>18 months or so without any issues on WLS 6.0 first and then WLS 6.1.
          > >>>The runtime is still available at
          > >>>http://dev2dev.bea.com/codelibrary/code/mqseries.jsp
          > >>>While I understand that this is Alpha code and not officially supported
          > >>>
          > > by
          > >
          > >>>Bea, can someone please try to help me with the below issues ?
          > >>>We are doing an upgrade from MQ Series 5.2 to 5.3 or are suddenly
          seeing
          > >>>
          > > the
          > >
          > >>>infamous 'NoClassDefFoundError' on one of the XA classes. I think I
          may
          > >>>know what's going on but have no way to fix the problem. The
          > >>>wlsmqseries.jar was built using the MQ Series 5.2 libraries. Since we
          > >>>
          > > are
          > >
          > >>>upgrading to MQ Series 5.3 the classes in wlsmqseries.zip need to be
          > >>>
          > > rebuilt
          > >
          > >>>using the new APIs (I am pretty sure there are no API changes). Is it
          > >>>possible that the contributor of this utility (if reading this email)
          > >>>
          > > build
          > >
          > >>>wlsmqseries.jar using the MQ Series 5.3 libraries and release it. Or
          > >>>alternatively, I'll be happy to do the build if the source is given.
          > >>>
          > > Most
          > >
          > >>>of the stuff in the dev2dev site has code included. This one seems to
          > >>>
          > > be
          > >
          > >>>one of the few that doesn't have code.
          > >>>Note - Upgrading to WLS 7.0 or 8.1 is not an option for another 6
          months
          > >>>
          > > :(
          > >
          > >>>Help ! Please !
          > >>>Adarsh
          > >>>
          > >>>
          > >>>
          > >>>
          > >
          > >
          >