NoClassDefFoundError (initialization failure) - Websphere and IBM MQ

Question

Im having a problem on a Spring based webapp that is being deployed to Websphere and interacts with IBM MQ.

All is fine until I try some failure tests.

While the webapp is up and running, I stop IBM MQ. I then invoke the webapp to send a JMS message out. The webapp hung at the call to JmsTemplate.convertAndSend and the following exception was found in the ffdc directory.

Note the JmsTemplate was initialised using the JNDIObjectFactoryBean where it had got the MQ Connection Factory settings from Websphere.

Can anyone explain the reason behind the "Initializaton Failure" ??

[27/01/11 14:29:39:498 GMT]     FFDC Exception:java.lang.NoClassDefFoundError SourceId:com.ibm.ws.asynchbeans.J2EEContext.run ProbeId:894 Reporter:com.ibm.ws.asynchbeans.J2EEContext@1280128
java.lang.NoClassDefFoundError: com.ibm.msg.client.wmq.common.internal.Reason (initialization failure)
        at java.lang.J9VMInternals.initialize(J9VMInternals.java:140)
        at com.ibm.msg.client.wmq.internal.WMQMessageProducer.checkJmqiCallSuccess(WMQMessageProducer.java:1024)
        at com.ibm.msg.client.wmq.internal.WMQMessageProducer.checkJmqiCallSuccess(WMQMessageProducer.java:997)
        at com.ibm.msg.client.wmq.internal.WMQMessageProducer.access$800(WMQMessageProducer.java:63)
        at com.ibm.msg.client.wmq.internal.WMQMessageProducer$SpiIdentifiedProducerShadow.initialise(WMQMessageProducer.java:758)
        at com.ibm.msg.client.wmq.internal.WMQMessageProducer.<init>(WMQMessageProducer.java:972)
        at com.ibm.msg.client.wmq.internal.WMQSession.createProducer(WMQSession.java:943)
        at com.ibm.msg.client.jms.internal.JmsSessionImpl.createProducer(JmsSessionImpl.java:1162)
        at com.ibm.msg.client.jms.internal.JmsQueueSessionImpl.createSender(JmsQueueSessionImpl.java:131)
        at com.ibm.mq.jms.MQQueueSession.createSender(MQQueueSession.java:148)
        at com.ibm.mq.jms.MQQueueSession.createProducer(MQQueueSession.java:249)
        at com.ibm.ejs.jms.JMSMessageProducerHandle.<init>(JMSMessageProducerHandle.java:132)
        at com.ibm.ejs.jms.JMSSessionHandle.createProducer(JMSSessionHandle.java:1788)
        at org.springframework.jms.core.JmsTemplate.doCreateProducer(JmsTemplate.java:968)
        at org.springframework.jms.core.JmsTemplate.createProducer(JmsTemplate.java:949)
        at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:568)
        at org.springframework.jms.core.JmsTemplate$3.doInJms(JmsTemplate.java:541)
        at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:471)
        at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:539)
        at org.springframework.jms.core.JmsTemplate.convertAndSend(JmsTemplate.java:617)

I know nothing about Spring but I'm guessing that instead of the WMQ client full install, just the WMQ jars were grabbed? If so, then you probably are missing the message catalog or some of the NLS pieces. If this sounds plausible, I'll be happy to write a fully detailed response with links to the appropriate downloads and manuals. — T.Rob, Jan 27 '11 at 17:00
Hi Rob, Im not sure who setup the machine, so dont know how WMQ was installed. How could I verify this? — Alex, Jan 27 '11 at 17:38
It would be in /usr/mqm (AIX), /opt/mqm (other UNIX/Linux) or on Windows it's usually in C:\Program Files\IBM\WebSphere MQ. Typically if it's in your path you can type dspmqver to see the version and release number. — T.Rob, Jan 28 '11 at 00:40
Version: 7.0.1.0 CMVC Level: p000-L090813 BuildType: IKAP (production) — Alex, Jan 28 '11 at 09:04
Well, glad I put this as a comment and not a response. I was on the wrong track. — T.Rob, Feb 01 '11 at 05:53

score 16 · Answer 1 · answered Jan 28 '11 at 18:40

The "(initialization failure)" means that the static initializer ("<clinit>") method of the class previously threw an unchecked exception. When this occurs, the JVM marks the class as bad, and subsequent attempts to use or access the class result in NoClassDefFoundError. Search your logs for errors that include "Reason.<clinit>" in the stack trace to find the underlying cause.

(In general, the NoClassDefFoundError should include a "Caused by" with the exception that occurred in the static initializer, but for some reason, the cause either wasn't present or you didn't include it in your stack trace.)

score 1 · Answer 2 · answered Jan 27 '11 at 18:03

1

It does look like a message catalog is missing. I'm reading the stack dump as the thrown exception (NoClassDefFound) is trying to access something in it's constructor. The missing class may be the actual cause or the missing message may be hiding the actual exception, depending on how it was thrown of course. Can you put a catch block in and manually walk the nested exceptions?

Even if this exception isn't part of a nested exception, it could also mean it was instantiated inside a catch block of an unknown exception. I wouldn't expect that issue in IBM's MQ code but you never know.

answered Jan 27 '11 at 18:03

Kelly S. French

12,198
10
63
93

Wouldnt a missing message catalog cause problems in normal running? This problem only happens in a specific failure scenario. – Alex Jan 27 '11 at 20:10
Yes, if there was only one catalog. There can be multiple catalogs. Also it could be a single message missing from a catalog that exists. – Kelly S. French Jan 27 '11 at 20:52

NoClassDefFoundError (initialization failure) - Websphere and IBM MQ

2 Answers2

Linked