| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Dead Letter Q (message taking 30 sec) |
« View previous topic :: View next topic » |
| Author |
Message
|
| pammy |
 Posted: Wed Feb 21, 2007 4:32 pm Post subject: Dead Letter Q (message taking 30 sec) |
 |
|
Newbie
Joined: 21 Feb 2007
Posts: 1
|
Hi,
I am 3 weeks old kid in MQ stuff. tried to solve one problem in
in my MQ life(3 weeks) but was not sucessful. hope masters can help me out.
Here we go....
In our application, we are sending message from WMQ to MQe
(point-of-sale). If the point-of-sale system is down, message is sent
back
to the
dead letter queue of MQ system. To perform this task, we are
using UndeliveredMQMessageToDLQRule class (provided with examples) that simply returns -2 to XMITQ listener. Listener then sends this
message to Dead Letter Queue.
Our Problem:
If the Point-of-sale system is down, message takes 30 sec (approx) to
come back to Dead Letter Queue. This 30 sec time gap is severely affecting the performance of our application. We want to reduce this time as much as possible.
Down here is the Exception that is thrown when POS is down:
(code=700)com.ibm.mqe.communications.MQeCommunicationsException:An
exception occured in the
communications layer(java.net.SocketException: Operation timed
out:
connect:could be due to invalid address)[GATEWAY_QM 34] (code=700)
Thanks in advance for any help.
Regards
Saini |
|
| Back to top |
|
 |
| pathipati |
| Posted: Wed Feb 21, 2007 7:21 pm Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
How much time it is taken by the message to reach MQe if MQe is not down?
the 30 sec time may depends on many factors like message size, network traffic etc..It may be hard to tell what is the cause of issue with above information. |
|
| Back to top |
|
|
| tleichen |
| Posted: Thu Feb 22, 2007 7:15 am Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
Also explore how and when your messages are being committed! 
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
| ajunod |
| Posted: Fri Feb 23, 2007 8:03 am Post subject: |
|
|
Newbie
Joined: 23 Feb 2007
Posts: 1
|
I was the one that asked Saini to pursue this delay in writing to the MQ deadletter Q and can provide the following additional facts.
1) Normal time to place a message is under 1.5 seconds.
2) Current data packet size is under 100 bytes.
3) If the connecting machine is up but the MQe service is down the time to the DLQ is instant
4) the extended delay only occurs when the machine receiving the message is shut off.
In further discussion with Saini we believe we need to change the OS level tcp/ip connection settings but have been unsucessful in finding where we can dynamaically override at the application level versus making a global change at the OS level |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
