| Author |
Message |
 Topic: Error while putting msg in the range of 32227 - 32270 bytes |
kingkb
Replies: 8
Views: 8009
|
 Forum: IBM MQ Java / JMS Posted: Sun Mar 21, 2010 9:58 pm Subject: Error while putting msg in the range of 32227 - 32270 bytes |
We did go through this post and were thinking that we might get some pointers in this forum as a similar problem was already identified way back in Sep'06  . |
| Topic: Error while putting msg in the range of 32227 - 32270 bytes |
kingkb
Replies: 8
Views: 8009
|
Forum: IBM MQ Java / JMS Posted: Sun Mar 21, 2010 4:25 pm Subject: Error while putting msg in the range of 32227 - 32270 bytes |
Hi Roger,
Thanks for the reply.
Do you mean that you never faced this kind of a problem with your java application for putting a message in this range using MQQueue.put() method?
The reason for ... |
| Topic: Error while putting msg in the range of 32227 - 32270 bytes |
kingkb
Replies: 8
Views: 8009
|
Forum: IBM MQ Java / JMS Posted: Tue Mar 16, 2010 6:05 pm Subject: Error while putting msg in the range of 32227 - 32270 bytes |
Hi All,
We are getting an exception while putting a message in the range of 32227 – 32270 bytes (inclusive) using put() method of MQQueue Class in com.ibm.mq.jar. The connection handle becomes in ... |
| Topic: Is MQ Event Monitoring a recommended approach? |
kingkb
Replies: 7
Views: 11260
|
Forum: IBM MQ Performance Monitoring Posted: Wed Jan 28, 2009 2:27 pm Subject: Is MQ Event Monitoring a recommended approach? |
Thanks for the replies guys.
Vitor,
I did check with the OPS team and they confirmed that there is no licensed third party monitoring tool that is currently available.
PeterPotkay,
We did thin ... |
| Topic: Is MQ Event Monitoring a recommended approach? |
kingkb
Replies: 7
Views: 11260
|
Forum: IBM MQ Performance Monitoring Posted: Wed Jan 28, 2009 11:54 am Subject: Is MQ Event Monitoring a recommended approach? |
Hello All,
I have a requirement for monitoring MQ queues and processes in our project.
The MQ architecture is very simple; we have only one queue manager and all the end applications directly con ... |
