ibm-mq

2538 - MQRC_HOST_NOT_AVAILABLE

我们两清 提交于 2020-01-15 07:30:06
问题 I am new to IBM Websphere MQ I am trying add messages to a Remote websphere MQ queue manager. I am getting following error while trying to connect to it. Also, I have tried many possible solutions provided in forums like changing .net framework to 3.5 also I am getting good ping while I ping the remote machine but I am unable to connect to it using C# code. The queue manager listener is up and running, but this is the error I am getting 2538 - MQRC_HOST_NOT_AVAILABLE while trying to do this.

How do you set a message selector using Java API?

拟墨画扇 提交于 2020-01-15 02:38:06
问题 I'm trying to write a simple test case to pull messages from a queue based on a message property, hitting a 7.5.0.3 QMgr and using the 7.5.0.3 client jars. Everything I have seen online says that I need to specify the message selector when I open the queue. I'm fine with that, but I only see two ways to open it: MQQueueManager.accessQueue( String queueName, int openOptions); MQQueueManager.accessQueue( String queueName, int openOptions, String queueMgr, String dynamicQueueName, String

When disconnecting from WebSphere MQ with C# client TCP connections are still in CLOSE_WAIT status

廉价感情. 提交于 2020-01-14 15:01:34
问题 I am disconnecting from MQQueue and MQQueueManager with the following code: Queue.Close(); log.Info( "Queue IsOpen: " + Queue.IsOpen.ToString() ); Queue = null; QueueManager.Disconnect(); QueueManager.Close(); log.Info( "QM IsOpen: " + QueueManager.IsOpen.ToString() ); log.Info( "QM IsConnected: " + QueueManager.IsConnected.ToString() ); QueueManager = null; And I get the following log entries for this: Queue IsOpen: false QM IsOpen: false QM IsConnected: false But after few hours when I run

When disconnecting from WebSphere MQ with C# client TCP connections are still in CLOSE_WAIT status

删除回忆录丶 提交于 2020-01-14 15:01:28
问题 I am disconnecting from MQQueue and MQQueueManager with the following code: Queue.Close(); log.Info( "Queue IsOpen: " + Queue.IsOpen.ToString() ); Queue = null; QueueManager.Disconnect(); QueueManager.Close(); log.Info( "QM IsOpen: " + QueueManager.IsOpen.ToString() ); log.Info( "QM IsConnected: " + QueueManager.IsConnected.ToString() ); QueueManager = null; And I get the following log entries for this: Queue IsOpen: false QM IsOpen: false QM IsConnected: false But after few hours when I run

Spring Boot: Reading spring.jms.jndi-name property from application.properties file using a Java Bean class

ⅰ亾dé卋堺 提交于 2020-01-14 14:38:07
问题 I am using JNDI lookup for the getting the connection object for Websphere MQ Broker on tomcat server. I am using JmsTemplate for sending the messages to the Queue on WMQ Broker and trying to avoid the Spring Xml based configuration and for that reason i have configured the Spring boot's application.properties file to specify the JNDI look up name.below is the property from application.properties file. spring.jms.jndi-name= java:comp/env/XXXX i am using a Spring bean to define the JmsTemplate

WebSphere MQ and Atomikos - Messages Lost on process termination

China☆狼群 提交于 2020-01-14 10:30:08
问题 My app (a spring message listener) reads from a queue and writes to the database in a single transaction. I use Atomikos to provide the XA transaction behaviour. When the app is abruptly terminated with kill statements for example, I see messages are lost. Is there any specific configuration I need to use? Should the queues be persistent? Currently the queues are non-persistent. My MQ version is v7.1. Spring config for listener container looks like: <bean id="listenerContainer" class="com

AMQ9504: A protocol error was detected for channel

妖精的绣舞 提交于 2020-01-13 19:56:48
问题 I'm unable to connect remotely from WebSphere Application Server with Queue Manager at WebSphere MQ. Anyhow it get connected to Queue Manager from WAS that is installed on same machine. I'm using version 7.5 of WebSphere MQ and version 7.0 of WebSphere Application Server. While attempting to connect WAS remotely to Queue Manager following error messages were logged. Error Message from WebSphere MQ: 1/30/2013 21:12:09 - Process(3624.6) User(MUSR_MQADMIN) Program(amqrmppa.exe) Host(KHILT-269)

AMQ9504: A protocol error was detected for channel

我的未来我决定 提交于 2020-01-13 19:56:38
问题 I'm unable to connect remotely from WebSphere Application Server with Queue Manager at WebSphere MQ. Anyhow it get connected to Queue Manager from WAS that is installed on same machine. I'm using version 7.5 of WebSphere MQ and version 7.0 of WebSphere Application Server. While attempting to connect WAS remotely to Queue Manager following error messages were logged. Error Message from WebSphere MQ: 1/30/2013 21:12:09 - Process(3624.6) User(MUSR_MQADMIN) Program(amqrmppa.exe) Host(KHILT-269)

WebSphere MQ v7.1 Security User Credentials

核能气质少年 提交于 2020-01-11 03:58:07
问题 Linux Server Box running WebSphere MQ Server v7.1: I have created a user 'mq-user' that belongs to 'mq-users' group in Linux. Then I created a queue manager QM_TEST , and used MQSC to issue the following commands to create a queue and set up the security: SET AUTHREC OBJTYPE(QMGR) PRINCIPAL('mq-user') AUTHADD(ALL) SET AUTHREC PROFILE(SYSTEM.MQEXPLORER.REPLY.MODEL) OBJTYPE(QUEUE) PRINCIPAL('mq-user') AUTHADD(INQ,DSP,GET) SET SET AUTHREC PROFILE(SYSTEM.ADMIN.COMMAND.QUEUE) OBJTYPE(QUEUE)

How to improve MQ client create conncetion time?

天大地大妈咪最大 提交于 2020-01-07 02:40:28
问题 I have an app on Tomcat 7.05 that connects to a remote MQ manager, everything work fine, it just that creating a connection takes an insane amount of time ~ 13 seconds (if I put both java code and MQ server on one machine, it takes less then a second). How do I improve create connection time? My java code: import javax.jms.DeliveryMode; import javax.jms.JMSException; import javax.jms.Message; import javax.jms.Queue; import javax.jms.QueueConnection; import javax.jms.QueueConnectionFactory;