ibm-mq

I'm building a java application that connects to a MQQueueManager and extracts information about queues. I'm able to get data like QueueType , MaximumMessageLength and more. However, I also want the name of the cluster the queue might be in. There is no function that comes with the MQQueue that gives me this information. After searching the internet I found several things pointing in this direction, but no examples. A part of my function that gives me the MaximumDepth is: queueManager = makeConnection(host, portNo, qMgr, channelName); queue = queueManager.accessQueue(queueName, CMQC.MQOO

Closed . This question needs to be more focused . It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post . Closed 3 years ago . I just need to know some basic information or the procedure that is followed when migrating from IBM MQ server to ActiveMQ. We are planning to migrate our messaging systems from IBM MQ to Active MQ. To be specific the migration is from MQ V7.0 to ActiveMQ V5.7.0. What would be the object movement from IBM MQ to ActiveMQ i.e., to know the comparison or the relation between MQ

We are trying to connect to IBMMQ using CCDT file and JMS configuration. We are able to connect to it but we have an issue here: since we are using spring to set connection factory with CCDT file, this is initialized once at the start of the application, but unfortunately it picks only one queue manager at a time,i.e it sends all the messages to same queue manager and it does not load balance. Though i observed, if i manually set the CCDT file before every request then its able to load balance the Queue Managers, ideally it looks to me Queue Manager is decided whenever i set the URL to CCDT

Update It was my mistake I forget the ssl debugging running, it is super fast now and working like magic I have a Spring Boot application that connects to IBM MQ using spring JMS. I realized that the jmsTemplate is super slow compared to not using Spring at all. I am sure I have something not configured correctly. Hope Someone can help. I create a connection factory using IBM MQ 8 jar files. @Bean public ConnectionFactory connectionFactory() { properties.getCipherSpec()); MQConnectionFactory factory = new MQConnectionFactory(); try { factory.setHostName(properties.getHost()); factory.setPort

Two separate processes are communicating via JMS over MQ. The writer sets a string property: new MessageAction() { public void actOn(Message message) throws JMSException { logger.debug("Setting message property (GmmThreadId, CASHFLOW-1234)"); message.setStringProperty("GmmThreadId", "CASHFLOW-1234"); } }); This MessageAction is executed, as shown in the logs: Setting message property (GmmThreadId, CASHFLOW-1234) The reader uses a message selector to obtain this message. (using Spring's JmsTemplate v1 - an old version I know, but it's baked into our vendor's framework and we're compelled to use

We are using spring integration to connect to IBM MQ V7.5 to read messages from queue. We occasionally get large messages to read. SI jms adapter fails to read to large message, but it works for smaller messages. Below is the exception we are getting 23:18:35,470 WARN DefaultMessageListenerContainer:839 - Setup of JMS message listener invoker failed for destination 'queue:///Cis.Orders' - trying to recover. Cause: JMSWMQ2002: Failed to get a message from destination 'XXX'.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '1' ('MQCC_WARNING')

We need to execute SET AUTHREC PROFILE($cname) OBJTYPE(CHANNEL) GROUP('mq-user') AUTHADD(...) so that the channels show up WMQ Explorer, it that correct? Current the access is prevented. Yes. With the AUTHREC profiles defined in this and previous questions you have authorized the user to connect to the QMgr, put requests to the command queue and receive replies on a model queue. The command server needs to know what operations on other objects the group is authorized for. As an example, it won't display or let members of the group control channels until you authorize them. A quick way to see