| Author |
Message
|
| irwn |
 Posted: Sat Jul 19, 2003 12:46 am Post subject: AMQ8041 during testing. |
 |
|
Newbie
Joined: 19 Jul 2003
Posts: 7
Location: ID
|
We are testing an application running on WebLogic Server 6.1.
We have threads running to listen to the queue for reply. We are trying to simulate such that if something happen to MQ we will be able to recover the connection again.
However during testing we are having trouble to start the MQ again after we shutdown MQ Manager (using MQ Explorer). Everytime we are trying to start the q manager again it give us error AMQ8041 and the pid specify is the WebLogic (java) PID which of course we cannot stop.
In our application, upon detecting that the connection is not valid/open, we try to close (and disconnect in the case of manager) the queues and manager then go to sleep for x seconds before trying to create the connection again.
Has anyone has this kind of problem and/or solutions?
One other question, when we called a close on a queue is that still possible that the queue still connected?
as well as the q manager itself, which is cleaner or better to release the connection? will disconnect perform the close as well or do I still need to perform both close and disconnect?
The test system I am using is a Pentium III - 1GHz, 512 MB, WebLogic 6.1 SP3, IBM WebSphereMQ 5.3 running Windows XP.
TIA,
Iwan. |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Sat Jul 19, 2003 3:14 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Close just closes a queue, whereas Disc disconnects the app from the queue manager. You have to do BOTH at all times. Not sure if missing the disc is the cause of your problem because you did not mention so.
But if it is so, then incorporate MQDISC and it should work fine.
Who is connecting and opening the queue. Is it an app or is it something within weblogic that is doing this.
Cheers
Kumar |
|
| Back to top |
|
|
| Prahasith |
| Posted: Sat Jul 19, 2003 8:36 am Post subject: AMQ9028 |
|
|
Disciple
Joined: 16 May 2003
Posts: 184
Location: Kansas City
|
| I am getting AMQ9208 error when my java application is trying to connect the queue manager. can any one throw light on this |
|
| Back to top |
|
|
| irwn |
| Posted: Sun Jul 20, 2003 6:00 pm Post subject: RE: AMQ8041 |
|
|
Newbie
Joined: 19 Jul 2003
Posts: 7
Location: ID
|
Thanks for the input.
We are actually do the disconnect from the manager. I believe there is no disconnect API for the queue.
The queue and manager is created from a java application running inside weblogic.
I will check again make sure that all the queue manager do call the disconnect.
Thanks,
Irwn |
|
| Back to top |
|
|
| mqonnet |
| Posted: Sun Jul 20, 2003 6:27 pm Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
As i mentioned in my earlier post, MQCLOSE just closes the queue, and MQDISC disconnects an app from the queue manager. So, if you see an error saying there are connected applications, then MQCLOSE has nothing to do with it. Some app is not cleaning up properly, in the sense that it is not doing a Disconnect. Or even if it is doing, it may be getting an error and not catching and ending. Check and verify the same.
Cheers
Kumar |
|
| Back to top |
|
|
| irwn |
| Posted: Sun Jul 20, 2003 8:02 pm Post subject: AMQ8041 from java app running in weblogic |
|
|
Newbie
Joined: 19 Jul 2003
Posts: 7
Location: ID
|
Thank for your help. I do a trace, somehow I believe we cannot close the queue. I did call the disconnect on the app manager but failed to close the queue (nor the manager). Thus both the queue and manager still open (although the manager is not connected anymore).
Everytime the app tries to close the queue, it failed with reason code 2009 (connection broken). This is cause by the termination of MQ (we force to stop it to simulate MQ down). But subsequently, it still failed to close the queue.
Any idea how to force the queue to close it (as well as the manager)? I tried using the close() but it seems that it may not be working. Setting it to null don't think will help (i.e. the resources are not release).
Thanks |
|
| Back to top |
|
|
| syangloo |
| Posted: Mon Jul 21, 2003 7:26 pm Post subject: |
|
|
Centurion
Joined: 01 Oct 2002
Posts: 120
Location: Kuala Lumpur
|
irwn,
May be you can stop the Java App first before you shout down the queue manager. It may cause by the java program still connect to the queue, so you can't bring up the queue manager properly.
I hit this problem before, after I can't bring up the queue manager. I check the queue manager status, it still go one app is connect to the queue. I manually kill the process, and then I can bring up the queue manager successfully.
Hope it help you. 
Regards
Syangloo |
|
| Back to top |
|
|
| irwn |
| Posted: Thu Jul 24, 2003 6:14 pm Post subject: |
|
|
Newbie
Joined: 19 Jul 2003
Posts: 7
Location: ID
|
Thank you for your reply.
The problem I cannot shutdown the java app first. It is running inside the weblogic (i.e. have to kill weblogic). If that's the case it will beat the purpose of the test (to recover connection automatically upon mq restarted).
TGIF. |
|
| Back to top |
|
|
|
|
