| Author |
Message
|
| flwilliams87 |
 Posted: Fri Feb 02, 2007 9:37 am Post subject: Probe ID: XC338001 AMQ6109: An Internal WebSphere MQ |
 |
|
Acolyte
Joined: 04 Feb 2003
Posts: 66
Location: Chicago, IL
|
Below is a cut and past of my FFST Log, and I get this error sporadically, but when ever it happens the Application cannot pull messages of off the queue and I get a 2080 when I attempt to pull messages off with amqsget. And since OPPROCS is open I have to recycle the Queue Manager to Clear the messages. Any Ideas?
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Friday February 02 11:00:51 CST 2007 |
| Host Name :- aix3stg (AIX 5.2) |
| PIDS :- 5724B4101 |
| LVLS :- 530.8 CSD08 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Sep 21 2004 |
| CMVC level :- p530-08-L040921 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000515 (mqm) |
| Program Name :- runmqlsr_nd |
| Process :- 00127982 |
| Thread :- 00000002 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 1 1 |
| Arith2 :- 127982 1f3ee |
| Comment1 :- SIGHUP |
| |
| |
+-----------------------------------------------------------------------------+ |
|
| Back to top |
|
 |
| EddieA |
| Posted: Fri Feb 02, 2007 10:13 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
The FFST and your inability to pull messages are completely unrelated.
The FFST was generated because someone sent a SIGNAL to the listener, and it promptly ignored it, but warned you it received it. You need to investigate who is sending these SIGNALs.
2080 0x00000820 MQRC_TRUNCATED_MSG_FAILED: This is caused because the message is larger than the buffer in amqsget, which if I remember correctly is 80 or 100 bytes.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| flwilliams87 |
| Posted: Fri Feb 02, 2007 10:18 am Post subject: |
|
|
Acolyte
Joined: 04 Feb 2003
Posts: 66
Location: Chicago, IL
|
| I realize that 2080 and the FFST data seem unrelated, but the message size is within the limits of the buffer size of amqsget (I checked), and the only time this happens is when an FFST is generated with that particular message and voila I can no longer pull messages of off the queue, no matter what size they are. I know it doesn't make sense but there has to be some type of correlation. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Feb 02, 2007 10:37 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Is it a client application?
Also, at least in MQ v6, you can force application connections (client or server) closed.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| flwilliams87 |
| Posted: Fri Feb 02, 2007 11:55 am Post subject: |
|
|
Acolyte
Joined: 04 Feb 2003
Posts: 66
Location: Chicago, IL
|
| Yes it is a Client application. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Feb 02, 2007 12:23 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Try simply restarting the listener instead of the queue manager.
Try restarting your client app, to recreate a new connection.
It sounds like something is interrupting your client connection - for example someone is trying to kill -HUP the MCA process.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| flwilliams87 |
| Posted: Fri Feb 02, 2007 12:31 pm Post subject: |
|
|
Acolyte
Joined: 04 Feb 2003
Posts: 66
Location: Chicago, IL
|
| I can't kill the listener with the command endmqlsr -m <QM>, because the Queue Manager is running, but I can kill the processes using kill <pid> |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Feb 02, 2007 12:39 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Oh, right. You're using v5.3.
Try force stopping the svrconn?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Feb 02, 2007 12:42 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Really, though, you need to find out what's messing around with you.
It could be an issue where MQ is trying to reclaim the mca in some manner. But there should be more errors for that on the server side.
It's more likely that there's a management process of some kind on the server that's trying to screw with things. Like something trying to clean up zombie processes or etc.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| flwilliams87 |
| Posted: Fri Feb 02, 2007 12:53 pm Post subject: |
|
|
Acolyte
Joined: 04 Feb 2003
Posts: 66
Location: Chicago, IL
|
| Cool, i'll look into that with our AIX admins |
|
| Back to top |
|
|
|
|
