| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Can't put message into Q |
« View previous topic :: View next topic » |
| Author |
Message
|
| syangloo |
 Posted: Thu Mar 20, 2003 6:19 am Post subject: Can't put message into Q |
 |
|
Centurion
Joined: 01 Oct 2002
Posts: 120
Location: Kuala Lumpur
|
Dear All,
Currently i have one local queue, it can't put any message in. I no getting any error message and i attach the error log from MQ.
error log from /var/mqm/errors
-------------------------------------------------------------------------------------
03/20/03 20:17:22
AMQ6090: MQSeries was unable to display an error message 2.
EXPLANATION:
MQSeries has attempted to display the message associated with return code
hexadecimal '2'. The return code indicates that there is no message text
associated with the message. Associated with the request are inserts 0 : 0 : :
: .
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.
-------------------------------------------------------------------------------
03/20/03 20:17:22
AMQ6184: An internal MQSeries error has occurred on queue manager QD!BK!KL!001.
EXPLANATION:
An error has been detected, and the MQSeries error recording routine has been
called. The failing process is process 6052.
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.
-------------------------------------------------------------------------------
When i runmqsac qmgr and display the queue detail i find IPPRCS(15) at the queue.
DESCR(Queue for all Requests going thru the Broker)
PROCESS( ) BOQNAME( )
INITQ( ) TRIGDATA( )
CLUSTER( ) CLUSNL( )
QUEUE(Q.REQUESTS.BROKERED) CRDATE(2002-06-12)
CRTIME(17.56.17) ALTDATE(2003-03-20)
ALTTIME(21.23.51) GET(ENABLED)
PUT(ENABLED) DEFPRTY(0)
DEFPSIST(NO) MAXDEPTH(5000)
MAXMSGL(4194304) BOTHRESH(0)
SHARE DEFSOPT(SHARED)
HARDENBO MSGDLVSQ(PRIORITY)
RETINTVL(999999999) USAGE(NORMAL)
NOTRIGGER TRIGTYPE(FIRST)
TRIGDPTH(1) TRIGMPRI(0)
QDEPTHHI(80) QDEPTHLO(20)
QDPMAXEV(ENABLED) QDPHIEV(DISABLED)
QDPLOEV(DISABLED) QSVCINT(999999999)
QSVCIEV(NONE) DISTL(NO)
DEFTYPE(PREDEFINED) TYPE(QLOCAL)
SCOPE(QMGR) DEFBIND(OPEN)
IPPROCS(15) OPPROCS(0)
CURDEPTH(0)
What is this mean?
URGENT
Hope your can help me on this.
Regards
syang |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Thu Mar 20, 2003 7:31 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
You are checking the system wide mqerror log. Look at the qmgr error log to see if it has more info, which i think would. /var/mqm/qmgrs/<your qm>/errors
The info that you have posted here is really inconclusive. The other error log would +vely have better explaination.
Any FD's along the way.
Any idea who has kept the queue open.
Of course, as a last resort you could end and restart your qm.
Cheers
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| syangloo |
| Posted: Fri Mar 21, 2003 3:00 am Post subject: |
|
|
Centurion
Joined: 01 Oct 2002
Posts: 120
Location: Kuala Lumpur
|
dear mqonnet,
I try to stop start and even reboot the server also, still have 15 process listen to the queue.
Today morning i find out it because of my colleage start other 14 message flow listen to the queue.
thsnks for you response
Syang |
|
| Back to top |
|
|
| mqonnet |
| Posted: Fri Mar 21, 2003 6:25 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Well, my first reaction to this would be that you are running some processes or apps that keep trying to connect to this qm. Because, it is impossible for a qm to keep its connections active once it goes down and comes back again.
So, the only options are.
1) Either you have a corrupted queue that has orphaned process info hanging around in it.
2) You have apps that keep connecting to this qm. And hence when you restart your qm, the ipprocs goes up. I see that this is a broker queue. That kind of suggests that your broker is running and opens this queue when the qmgr is available for connection. If this is so, then i would suggest you to end your broker and then restart your qm.
Cheers
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| syangloo |
| Posted: Fri Mar 21, 2003 4:56 pm Post subject: |
|
|
Centurion
Joined: 01 Oct 2002
Posts: 120
Location: Kuala Lumpur
|
mqonnet,
Thanks for you advice. I able to solve this problem with stop other 14 message flow which is connect to the same queue.
Regards
Syang |
|
| 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
|
|
|
|
