| Author |
Message
|
| golden_eye |
 Posted: Mon May 10, 2010 1:30 am Post subject: transmit message in XMIT queue |
 |
|
Newbie
Joined: 09 May 2010
Posts: 3
|
I want to send a message through queues from one Queue Manager to another Queue manager.
My application picks a message through an MDB from one queue and process it and puts an XML in the queue of sender queue manager.
The sender Queue Manager is in AIX machine, in one location.
The receiver Queue Manager is in Windows machine in another location. The message is sent through XMIT queue from AIX Queue manager to Windows Queue manager
The time taken to tramit the message is taking more than 60 seconds.
What is the reason for the delay?
But there is no delay when the message is processed directly without an MDB and sent to the XMIT queue. |
|
| Back to top |
|
 |
| fatherjack |
| Posted: Mon May 10, 2010 2:10 am Post subject: Re: transmit message in XMIT queue |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
| golden_eye wrote: |
The time taken to tramit the message is taking more than 60 seconds.
What is the reason for the delay?
But there is no delay when the message is processed directly without an MDB and sent to the XMIT queue. |
Given "there is no delay when the message is processed directly without an MDB" then "The time taken to tramit the message" is not more than 60 seconds. If the time taken to perform your end to end processing is more than 60 seconds then I suggest you look at what the MDB is doing.
Fr. Jack.
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
| exerk |
| Posted: Mon May 10, 2010 3:40 am Post subject: Re: transmit message in XMIT queue |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
I'm with the good father on this one.
| golden_eye wrote: |
| ...The time taken to transmit the message is taking more than 60 seconds... |
Unlikely. What is more likely is that the MDB is not committing the message until 60 seconds has elapsed, therefore the queue manager cannot send it until then.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| golden_eye |
| Posted: Tue May 11, 2010 5:05 am Post subject: Re: transmit message in XMIT queue |
|
|
Newbie
Joined: 09 May 2010
Posts: 3
|
| fatherjack wrote: |
| golden_eye wrote: |
The time taken to tramit the message is taking more than 60 seconds.
What is the reason for the delay?
But there is no delay when the message is processed directly without an MDB and sent to the XMIT queue. |
Given "there is no delay when the message is processed directly without an MDB" then "The time taken to tramit the message" is not more than 60 seconds. If the time taken to perform your end to end processing is more than 60 seconds then I suggest you look at what the MDB is doing.
Fr. Jack. |
Following is the MDB which we are using.
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="ejb-jar_ID" version="2.1" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
<display-name>ewms-ejb</display-name>
<enterprise-beans>
<message-driven id="EWMSDatagramMDB">
<ejb-name>EWMSDatagramMDB</ejb-name>
<ejb-class>com.klm.archi.ewms.application.EWMSDatagramMDB</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Container</transaction-type>
<message-destination-type>javax.jms.Queue</message-destination-type>
</message-driven>
<message-driven id="FFREWMSDatagramMDB">
<ejb-name>FFREWMSDatagramMDB</ejb-name>
<ejb-class>com.klm.archi.ewms.application.FFREWMSDatagramMDB</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Container</transaction-type>
<message-destination-type>javax.jms.Queue</message-destination-type>
</message-driven>
</enterprise-beans>
<assembly-descriptor/>
</ejb-jar>
But there is no delay in processing the request from the MDB. The listener port is picking the message from the queue and processing it immediately. The delay is caused in XMITQ from one queue manager to another Queue manager. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue May 11, 2010 5:12 am Post subject: Re: transmit message in XMIT queue |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| golden_eye wrote: |
| The delay is caused in XMITQ from one queue manager to another Queue manager. |
How do you know this?
From the timestamp that the MDB recorded for when it read the message?
From the timestamp that the sender application recorded for when it wrote the message?
Neither of these number may be accurate. Neither of them will indicate the time between when the message was committed by the sender and when the receiver channel wrote the message to the destination queue. |
|
| Back to top |
|
|
| golden_eye |
| Posted: Tue May 11, 2010 5:19 am Post subject: Re: transmit message in XMIT queue |
|
|
Newbie
Joined: 09 May 2010
Posts: 3
|
| mqjeff wrote: |
| golden_eye wrote: |
| The delay is caused in XMITQ from one queue manager to another Queue manager. |
How do you know this?
From the timestamp that the MDB recorded for when it read the message?
From the timestamp that the sender application recorded for when it wrote the message?
Neither of these number may be accurate. Neither of them will indicate the time between when the message was committed by the sender and when the receiver channel wrote the message to the destination queue. |
we dint use the time timestamp. We stopped the channels at each and every stage and found out to be delay in XMIT Q. |
|
| Back to top |
|
|
| fatherjack |
| Posted: Tue May 11, 2010 5:27 am Post subject: Re: transmit message in XMIT queue |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
| golden_eye wrote: |
| The delay is caused in XMITQ from one queue manager to another Queue manager. |
But you said earlier
| golden_eye wrote: |
| But there is no delay when the message is processed directly without an MDB and sent to the XMIT queue. |
So which is it? I don't recall MQ being discriminatory based on what type of application puts a message on a queue. Maybe things have moved on a bit in V7 
Have you tried stopping the channel and seeing how long it takes for the message to arrive on the XMITQ ? Then start the channel and see how long it takes the message to get to the other end.
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue May 11, 2010 5:28 am Post subject: Re: transmit message in XMIT queue |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| golden_eye wrote: |
| mqjeff wrote: |
| golden_eye wrote: |
| The delay is caused in XMITQ from one queue manager to another Queue manager. |
How do you know this?
From the timestamp that the MDB recorded for when it read the message?
From the timestamp that the sender application recorded for when it wrote the message?
Neither of these number may be accurate. Neither of them will indicate the time between when the message was committed by the sender and when the receiver channel wrote the message to the destination queue. |
we dint use the time timestamp. We stopped the channels at each and every stage and found out to be delay in XMIT Q. |
Then stop the SDR at the queue manager hosting the XMITQ, and have the application put a message(s) and check the status of the queue to see whether the message(s) sits there uncommitted - I can think of no other reason why a message will be held in an XMITQ for so long.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| fatherjack |
| Posted: Tue May 11, 2010 5:31 am Post subject: Re: transmit message in XMIT queue |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
| fatherjack wrote: |
| Have you tried stopping the channel and seeing how long it takes for the message to arrive on the XMITQ ? Then start the channel and see how long it takes the message to get to the other end. |
Obviously yes. I'll try to type a bit quicker next time.
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
|
|
