| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Queue Manager Goes Down |
« View previous topic :: View next topic » |
| Author |
Message
|
| kiruthigeshwar |
 Posted: Thu May 29, 2014 7:51 am Post subject: Queue Manager Goes Down |
 |
|
Acolyte
Joined: 31 Oct 2012
Posts: 50
|
Hi All,
We faced same issue twice in our live environment, that queue manager goes down unexpectedly. When investigated the /var/log/messages we found the below in two cases.
| Quote: |
| Case 1: The queue manager was stopped after creating an FDC file. The messages captured till the second before it generated FDC file, one of the back end systems was down or not responding alternatively for the whole day. |
| Quote: |
| Case 2: Same problem. But this time the front end was sending duplicate requests except for once in ten times. i.e, first request request will be new and the next 9 request will be duplicate requests as it was sending the same value in the unique identifier field of a request message, which in turn is a parser exception. This was happening for almost half a day. |
My question is: Do exceptions occurring for a very long time continuously filling the broker log (/var/log/messages) affect the system resource consumption by broker
| Quote: |
| .Because only during these two cases when we tried to switch as the broker user into the linux system or when we tried to access mqm folder or tried to list the files under a directory, we got 'Resource not available' message. And there was lot of orphan processes |
Note: Queue depth was around 60% and enough space for log files.
We fixed the issue with the front end and restarted the broker and it working fine now.
Please help me with this. . Any points, referral inks will be helpful
Thanks ,
NK
_________________
Regards,
K |
|
| Back to top |
|
 |
| Inisah |
| Posted: Thu May 29, 2014 8:26 am Post subject: |
|
|
Apprentice
Joined: 21 Mar 2014
Posts: 44
|
| What does the FDC contain ? Can you dispplay the FDC header ? |
|
| Back to top |
|
|
| kiruthigeshwar |
| Posted: Sat May 31, 2014 11:30 pm Post subject: |
|
|
Acolyte
Joined: 31 Oct 2012
Posts: 50
|
| Inisah wrote: |
| What does the FDC contain ? Can you dispplay the FDC header ? |
| Quote: |
|
| Effective UserID :- 781 (mqm)
|
| Real UserID :- UNKNOWN
|
| Program Name :- amqzlaa0
|
| Addressing mode :- 64-bit
|
| Process :- 20980
|
| Process(Thread) :- 20980
|
| Thread :- 1
|
| ThreadingModel :- PosixThreads
|
| UserApp :- FALSE
|
| Last HQC :- 0.0.0-0
|
| Last HSHMEMB :- 0.0.0-0
|
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC
|
| Minor Errorcode :- OK
|
| Probe Type :- MSGAMQ6119
|
| Probe Severity :- 2
|
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred
|
| ('11 - Resource temporarily unavailable' from pthread_create.)
|
| FDCSequenceNumber :- 0
|
| Arith1 :- 11 (0xb)
|
| Comment1 :- '11 - Resource temporarily unavailable' from
|
| pthread_create. |
_________________
Regards,
K |
|
| Back to top |
|
|
| kiruthigeshwar |
| Posted: Sun Jun 01, 2014 5:01 am Post subject: |
|
|
Acolyte
Joined: 31 Oct 2012
Posts: 50
|
We are using two servers. And we are informed that one of the processes in the second server was a long running process which caused deadlock for other backend system processes. Isnt that broker will resolve the deadlock,i.e, it will realease the connection after a while.
When checking the exception log we are maitaining on ESB side, while updating a table in ESB's database there was an exception given below
| Code: |
(0x03000000:PCDataField):Type = 5 (INTEGER)
(0x03000000:PCDataField):Text = '[unixODBC][IBM][ODBC 20101 driver][Oracle]ORA-00060: deadlock detected while waiting for resource' (CHARACTER) |
The Core system we are using is Sybase and the ESB's database is Oracle.
_________________
Regards,
K |
|
| 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
|
|
|
|
