Unable to post message to IBM MQ Queue

Question

I am trying to connect to IBM MQ and post message. getting below exception but the same code works in development environment.

org.springframework.jms.connection.SingleConnectionFactory.createSession(SingleConnectionFactory.java:437)
com.ibm.mq.jms.MQQueueConnection.createSession(MQQueueConnection.java:154) ~[com.ibm.mq.allclient-9.0.4.0.jar:9.0.4.0 - p904-L171030.1
com.ibm.mq.jms.MQQueueConnection.createQueueSession(MQQueueConnection.java:130) ~[com.ibm.mq.allclient-9.0.4.0.jar:9.0.4.0 - p904-L171030.1]
com.ibm.mq.jms.MQQueueSession.<init>(MQQueueSession.java:58) ~[com.ibm.mq.allclient-9.0.4.0.jar:9.0.4.0 - p904-L171030.1]
com.ibm.mq.jms.MQSession.<init>(MQSession.java:262) ~[com.ibm.mq.allclient-9.0.4.0.jar:9.0.4.0 - p904-L171030.1]\\n\
com.ibm.mq.jms.MQSession.getTransacted(MQSession.java:876) ~[com.ibm.mq.allclient-9.0.4.0.jar:9.0.4.0 - p904-L171030.1]
Caused by: java.lang.NullPointerException

Basically, the session is becoming null in other regions when we are trying to post a message from Spring JMS Template to IBM MQ.

from java,

    public void sendNotificationsMessageToQueue(String jsonMessage) 
    { 
    jmsTemplate(Queue, new MessageCreator(){ 
    @Override public Message createMessage(Session session) throws JMSException
    { 
    return session.createTextMessage(jsonMessage); 
    } });

From XML:

    <bean id="jmsTemplate" class="org.springframework.jms.core.JmsTemplate"> <property name="connectionFactory" ref="ibmConnectionFactory" /> 
    <property name="defaultDestination" ref="exQueue" /> 
    </bean>

What is different between this and the development environment? If the code is the same, then the difference is likely to be in the configuration. — chughts, Jun 03 '21 at 10:06
is it do something with open jdk version with MQ JMS version ? — sasrra, Jun 03 '21 at 18:40

score 1 · Answer 1 · answered Jun 08 '21 at 14:00

1

It worked after removing spring jms template and written new class for obtaining IBM MQ connection.

answered Jun 08 '21 at 14:00

sasrra

77
1
3
13

chughts · Answer 2 · 2021-06-04T10:17:52.947

Read this as a comment as opposed to an answer. It's a long comment and needed a little formatting.

Your XML should also have a ibmConnectionFactory bean defined which will point at the IBM MQ Factory classes. What is in there is going to be important. You need to share that, as it looks like that that is where your deployed code is failing.

I am guessing that this is not a Spring-Boot project, and you are not making use of the mq-jms-spring-boot-starter.

If you were then that you are defining jmsTemplate and ibmConnectionFactory beans is a bit strange. If the IBM MQ classes are the only Messaging classes defined in your spring-boot project then spring will automatically bind the IBM MQ connection classes to the default jmsTemplate bean.

If you have other Messaging classes defined as dependencies in your project, then your beans are ignoring them, which indicates that they are not needed and hence shouldn't be there.

If, however, you are using Spring-Boot and mq-jms-spring-boot-starter, then I find it easier to define the beans in Java code than XML, although you only need to if you are changing the defaults.

import com.ibm.mq.jms.MQConnectionFactory;
import com.ibm.mq.samples.jms.spring.globals.handlers.OurDestinationResolver;
import com.ibm.mq.samples.jms.spring.globals.handlers.OurMessageConverter;
import com.ibm.mq.spring.boot.MQConfigurationProperties;
import com.ibm.mq.spring.boot.MQConnectionFactoryFactory;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.jms.core.JmsTemplate;


import javax.jms.JMSException;

@Configuration
public class MQConfiguration114 {
    protected final Log logger = LogFactory.getLog(getClass());

    @Bean
    public MQConnectionFactory mqConnectionFactory() throws JMSException {
        MQConfigurationProperties properties = new MQConfigurationProperties();
        // Properties will be a mix of defaults, and those found in application.properties
        // under ibm.mq
        // Here we can override any of the properties should we need to
        MQConnectionFactoryFactory mqcff = new MQConnectionFactoryFactory(properties,null);
        MQConnectionFactory mqcf = mqcff.createConnectionFactory(MQConnectionFactory.class);
        return mqcf;
    }


    @Bean("myJmsTemplate")
    public JmsTemplate myJmsTemplate() throws JMSException {
        JmsTemplate jmsTemplate = new JmsTemplate(mqConnectionFactory());
        
        // Any other customisations necessary go here.
        // ...

        return jmsTemplate;
    }

}

Thanks for commenting. I do not use spring boot, but spring including allclients.jar v8.0.04 & tracecontrol for IBM config and jmstemplate to connect. — sasrra, Jun 04 '21 at 15:50
v8 is out of support. 8.0.0.4 is also very old. Why not go with 9.2.0.2 or 9.1.0.8? — JoshMc, Jun 04 '21 at 16:22
This code works from my dev region too but on test regions & production it breaks is it due to the way we read configuration on test & prod. we use helm+yml+configmap configuration to fetch property values — sasrra, Jun 04 '21 at 16:59
If the code is working in one environment and not in another then the environment and corresponding configuration is the difference. So it is likely to be due to how you fetch configuration properties. — chughts, Jun 07 '21 at 09:06

score 0 · Answer 3 · answered Aug 05 '21 at 00:00

0

We had the same problem.

It was not related to reading configurations but to the dd-java-agent.jar. The version 0.82.0 was causing the issue. We moved to 0.84.0 and problem solved!

answered Aug 05 '21 at 00:00

Achille Guemkam

131
5

Unable to post message to IBM MQ Queue

3 Answers3