| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| (RESOLVED) Message in xmitq from amqrcmla |
« View previous topic :: View next topic » |
| Author |
Message
|
| SAFraser |
 Posted: Mon Jun 23, 2008 9:28 am Post subject: (RESOLVED) Message in xmitq from amqrcmla |
 |
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
I created a new sender channel and tried to start it. I expected it to go to a 'binding' state as I doubted the business partner had yet punctured their firewall, and that is exactly what happened. After stopping, the channel went almost immediately back to 'binding'. I checked the xmitq (it's triggered) and found two messages from 'amqrcmla', each with "$" as the message data.
I have found little information about 'amqrcmla'. These two bits are excerpted from an APAR:
| Quote: |
A design change at WMQ6.0 ... transfer(ed) some of the channel
related functionalities to a new process, amqrcmla.... |
| Quote: |
....the "amqrcmla" process, which is responsible for creating channels and writing down the channel definition table.
|
(Also noticed that the system admin statistics queue was full [bad admin, me!], but I cannot see how it would be relevant...?)
I cleared the xmitq, and the channel behaves as expected (goes to binding when started, and stops on command). No more messages in the xmitq.
But I am curious about those two messages. Anyone know anything about 'amqrcmla'?
Last edited by SAFraser on Fri Jun 27, 2008 8:14 am; edited 1 time in total |
|
| Back to top |
|
 |
| Roadie |
| Posted: Mon Jun 23, 2008 3:51 pm Post subject: |
|
|
Newbie
Joined: 21 Aug 2006
Posts: 8
|
Coincidence. I just had a similar issue today for the first time with amqrcmla writing a message to a transmit queue with data containing "$" sign, and msg priority = 1. I don't know the circumstances that caused the message to be generated. I am running MQ 6.0.2.3 on HPUX. The APAR IY77246 (referred to by SAFraser previously) was resolved in MQ 6.0.1.1 fixpack.
APAR IZ21552 also references the amqrcmla module and addresses a problem with SSL-enabled channels. However, in my case, SSL is not used.
Will open a PMR with IBM. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Tue Jun 24, 2008 6:15 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
I'll open one, too. Please PM me your PMR number & I'll reference it when I open mine. I think it helps when they know that more than one customer has the problem.
I'm running 6.0.2.2 on Solaris 9. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Fri Jun 27, 2008 8:20 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
I was able to recreate the problem. It happens when a 'stop chl status(inactive)' is issued.
An APAR is being created to correct a timing problem. Here is an excerpt from the PMR:
| Quote: |
When processing a STOP CHL(...) STATUS(INACTIVE) command then we first mark the channel as needing to stop, then we put a message to the XMIT-Q to break the channel out of any current MQGET + MQGMO_WAIT.
This introduces a timing window in that if the channel is not in the MQGET and sees the status change and ends before the MQPUT of the PCF command then the PCF command itself then causes the channel to be triggered and for the channel to restart. |
A simple workaround is: stop the channel first; after it's in a stopped state, issue stop chl a second time with 'status(inactive)' and the channel status will change to inactive. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Mon Mar 16, 2009 6:55 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
|
| 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
|
|
|
|
