| Author |
Message
|
| syangloo |
 Posted: Sun Apr 06, 2003 6:01 pm Post subject: URGENT! msgid and corrid issue. |
 |
|
Centurion
Joined: 01 Oct 2002
Posts: 120
Location: Kuala Lumpur
|
Dear all,
Client - MQ 5.2
Host - MQ 5.2
Broker - MQ 5.2 and WMQI 2.1
We have build up the Request/Reply message flow for those transaction messages. Client application will send a request message (RqMsg) to broker and broker will pass it to the host, server application will reply it back to client with go through broker again. Client application will pick up the reply message (RpMsg) according the messageid.
Client -----> RqMsg with messageid ----> Broker copy the messageid into RqMsg CorrID before it put to the host queue -----> host application copy the RqMgs CorrID into RpMsg CorrID field -----> Broker pass it to client queue ------> Cleint application will pick up the message according the MsgID match with the CorrID.
This is the the concert we use for the request reply message flow.
But now we are trying the stress test for the client application, and then we facing some problem. That is after few hundrad message we send, the client application can't pick up the reply message from the reply queue and we find out the the reply message CorrID is not match with the RqMsg messageid. We try to stop start the client Qmgr also the same.
If i use other client program with other Qmgr to send a message to the same host, it can pick up the RpMsg successfully.
Below is the error log from the client qmgr:
| Quote: |
-------------------------------------------------------------------------------
04/04/03 20:20:09
AMQ6209: An unexpected asynchronous signal (1) has been received and ignored.
EXPLANATION:
Process 9112 received an unexpected asynchronous signal and ignored it. This
has not caused an error but the source of the signal should be determined as it
is likely that the signal has been generated externally to MQSeries. Use the
UNIX system command kill with option -l to determine the symbolic name for
signal 1.
ACTION:
Determine the source of the signal and prevent it from re-occurring.
-------------------------------------------------------------------------------
04/04/03 20:20:09
AMQ6183: An internal MQSeries error has occurred.
EXPLANATION:
An error has been detected, and the MQSeries error recording routine has been
called. The failing process is process 9112.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
-------------------------------------------------------------------------------
|
Please help me to verify this probelm and what is the main issue cause for it.
Thanks
Syang |
|
| Back to top |
|
 |
| rajmq |
| Posted: Sun Apr 06, 2003 11:25 pm Post subject: |
|
|
Partisan
Joined: 29 Sep 2002
Posts: 331
Location: USA
|
Hi
I have one doubt on ur post:
Client -----> RqMsg with messageid ----> Broker copy the messageid into RqMsg CorrID before it put to the host queue
How u are doing the above step??
are using ESQL command for above setup?
can u explain ...........
regards
raj |
|
| Back to top |
|
|
| syangloo |
| Posted: Mon Apr 07, 2003 1:02 am Post subject: |
|
|
Centurion
Joined: 01 Oct 2002
Posts: 120
Location: Kuala Lumpur
|
Hi Rajmq
Yes, we using the ESQL in the message flow to copy the RqMsg msgid into the RqMsg CorrID field before it put into host queue. Because we find out the msgid will be change when we put the msg into diff queue.
Regards
Syang. |
|
| Back to top |
|
|
| rajmq |
| Posted: Wed Apr 09, 2003 2:53 am Post subject: |
|
|
Partisan
Joined: 29 Sep 2002
Posts: 331
Location: USA
|
Hi
Can u post ur ESQL commands,
Be'z i had same issues for our application.
regards
raj |
|
| Back to top |
|
|
| syangloo |
| Posted: Wed Apr 09, 2003 3:42 am Post subject: |
|
|
Centurion
Joined: 01 Oct 2002
Posts: 120
Location: Kuala Lumpur
|
Below is the ESQL we set it in one of the compute node before put the msg to host queue.
| Code: |
Set OutputRoot.MQMD.CorrId=InputRoot.MQMD.MsgId
|
Do you facing the same problem i have? After few hundrad message the client can't pick up the message. Because of the host reply the CorrId is not sync with the msgid of client.
Regards
syang |
|
| Back to top |
|
|
| syangloo |
| Posted: Mon Apr 28, 2003 4:59 pm Post subject: |
|
|
Centurion
Joined: 01 Oct 2002
Posts: 120
Location: Kuala Lumpur
|
Any one of you have this solution?
Currently i plan to use the scheduler to stop start the Qmgr and the application every day. (before this we never donw the Qmgr).
Urgently need the solution of this issue.
Regards
Syang |
|
| Back to top |
|
|
| bower5932 |
| Posted: Tue Apr 29, 2003 5:19 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| The error message from your amqerr01.log above should have an FDC file with it. Can you post the top part of it here? |
|
| Back to top |
|
|
| syangloo |
| Posted: Tue Apr 29, 2003 5:24 pm Post subject: |
|
|
Centurion
Joined: 01 Oct 2002
Posts: 120
Location: Kuala Lumpur
|
Sorry "brower5932", my MQ trace is off or i can't found any FDC file in the MQ Series directory.
Regards
Syang |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Apr 29, 2003 5:41 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
FDC files are generated irrespective of MQ trace being turned ON or NOT. Ususally they are (if any) in the errors directory like
<MQInstall Dir>/qmgrs/<QM Name>/errors
-------
Venny |
|
| Back to top |
|
|
| syangloo |
| Posted: Tue Apr 29, 2003 6:25 pm Post subject: |
|
|
Centurion
Joined: 01 Oct 2002
Posts: 120
Location: Kuala Lumpur
|
Sorry..... about the MQ trace.
I can't find any FDC file in the folder, it only content 3 AMQERRxx files.
Regards
Syang |
|
| Back to top |
|
|
| clindsey |
| Posted: Tue Apr 29, 2003 7:34 pm Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
Take a look in <MQ Install Dir>/errors. You should find the FDC there.
The signal 1 is a SIGHUP which could mean that a client or even the broker that has an open MQ connection disconnected the terminal session prior to disconnecting from the queue manager. If your problem is repeatable but you only have one occurence of this message in the error log, then it has nothing to do with the problem.
Are you getting any exceptions or mq return codes either at the client or the broker application or just a 2033 to indicate that no messages match the requested correlation id? Do you have expiry times set on the request or reply message. If so, the time interval may be too short to survive in your stress test cases.
Charlie |
|
| Back to top |
|
|
| syangloo |
| Posted: Wed Apr 30, 2003 6:49 pm Post subject: |
|
|
Centurion
Joined: 01 Oct 2002
Posts: 120
Location: Kuala Lumpur
|
In <MQ Install Dir>/errors directory, i found AMQERR01 and some *.TRC files.
We are getting time out becoz of the MsgId not match with the CorrID. Currently our time out/Wait interval is 60 sec. |
|
| Back to top |
|
|
|
|
