| Author |
Message
|
| bkiran2020 |
 Posted: Thu Nov 29, 2012 3:55 pm Post subject: Uncomiitted message |
 |
|
Master
Joined: 20 Jan 2011
Posts: 243
Location: US
|
The transmission queue is stalled & the channel is running fine.
But the on the channel the UNCOM(YES)
this show that the uncommitted message is there on the XMIT queue.
Could any one explain when the about the uncommitted message |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu Nov 29, 2012 4:19 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Look at error logs on both ends of the channel. Any channel errors?
Stalled? Are you saying that curdepth is non-zero? What is cur-depth? What are batchsize and batchintervsl attributes of channel?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Nov 30, 2012 7:16 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Why do you think that it's the MCA that has an uncommitted message on the xmitq?
It could just as easily be a sending application. |
|
| Back to top |
|
|
| bkiran2020 |
| Posted: Fri Nov 30, 2012 11:51 am Post subject: |
|
|
Master
Joined: 20 Jan 2011
Posts: 243
Location: US
|
| mqjeff wrote: |
Why do you think that it's the MCA that has an uncommitted message on the xmitq?
It could just as easily be a sending application. |
Could you please explain how the uncommitted message are flow in the MQ ?
Please suggest any link or doc for uncommitted message in MQ |
|
| Back to top |
|
|
| bkiran2020 |
| Posted: Fri Nov 30, 2012 11:55 am Post subject: |
|
|
Master
Joined: 20 Jan 2011
Posts: 243
Location: US
|
| bruce2359 wrote: |
Look at error logs on both ends of the channel. Any channel errors?
Stalled? Are you saying that curdepth is non-zero? What is cur-depth? What are batchsize and batchintervsl attributes of channel? |
Thanks the issues is resolved ....
Could please explain about the how the uncommitted message flow in MQ... |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Nov 30, 2012 1:07 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| bkiran2020 wrote: |
| bruce2359 wrote: |
Look at error logs on both ends of the channel. Any channel errors?
Stalled? Are you saying that curdepth is non-zero? What is cur-depth? What are batchsize and batchintervsl attributes of channel? |
Thanks the issues is resolved ....
Could please explain about the how the uncommitted message flow in MQ... |
How about this: I will explain uncommitted messages if you will explain how the issue is resolved.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| bkiran2020 |
| Posted: Fri Nov 30, 2012 1:30 pm Post subject: |
|
|
Master
Joined: 20 Jan 2011
Posts: 243
Location: US
|
| bruce2359 wrote: |
| bkiran2020 wrote: |
| bruce2359 wrote: |
Look at error logs on both ends of the channel. Any channel errors?
Stalled? Are you saying that curdepth is non-zero? What is cur-depth? What are batchsize and batchintervsl attributes of channel? |
Thanks the issues is resolved ....
Could please explain about the how the uncommitted message flow in MQ... |
How about this: I will explain uncommitted messages if you will explain how the issue is resolved. |
sorry for that the issues is resolved by L3 team...i too dont how they resolved |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Nov 30, 2012 2:10 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Here is a brief, high-level description of uncommitted messages, as they relate to channels. Do some research on google. Search for mq+uncommitted+messages.
Uncommitted messages are messages that are MQPUT to a queue, or MQGET from a queue inside a Unit of Work. While the Unit of Work remains active, the messages are not visible to, or consumable by, any other application.
A message MQPUT to an xmit queue inside a UofW will not be consumable by the sender channel MCA until the application MQCMITs the message. If the app MQBACKs the message, it will be deleted from the queue.
Once the message has been committed into the xmitq, the sender MCA will MQGET the message, and attempt to transmit it to its partner receiver MCA.
The usual behavior of a channel is to MQGET messages in a UofW, and to commit (MQCMIT) the message(s) out of the xmitq only when they have successfully MQPUT (in the same UofW) to the appropriate destination queue or DLQ.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Dec 01, 2012 6:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
What bruce's explanation means is that it is somewhat usual to see uncommitted messages on a transmission queue while a channel is running.
Depending on the behavior of your applications, it may in fact be normal to see uncommited messages on *all* of your queues, while applications are running - because they PUT and GET messages in units of work.
Until you understand the behavior of MQ and understand the behavior of your applications, you will not be able to do any singificant troubleshooting beyond following the instructions of L2 and L3 in terms of giving them data.
You should evaluate your responsibilities to your employer in that respect, and consider your responsibilities to yourself from a professional point of view, and determine if that means you should spend much more of your own time reading, thinking, trying and learning things. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Dec 01, 2012 7:11 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
To add to the complexity of this issue, you need to consider exactly what channel status 'RUNNING' means, and what it does not mean.
Channel state RUNNING indicates that the channel ends (MCA's) are either currently transmitting messages; OR, if the channel is not currently transmitting messages, that the channel ends believe that the next time they attempt to transmit messages, that they will be able to successfully do so. The channel ends may not detect that the channel has failed until the next time it attempts to transmit a message.
As Jeff suggests, it is possible that some application(s) MQPUT a message to a xmitq in a UofW, then waits for some human activity or extended period of time, before committing the message. This is an example of a long-running UofW - a long-running transaction. As Jeff suggests, a long-running transaction is not the usual application design.
As Jeff also suggests, get your organization to enroll you in WMQ system administration training.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
