| Author |
Message
|
| Bharat7 |
 Posted: Tue May 23, 2006 7:18 pm Post subject: Completion code [2] Reason code [2058] |
 |
|
Newbie
Joined: 23 May 2006
Posts: 8
|
Hi,
We are getting the following error while connecting to WMQ v5.3 qmgr from a J2EE application running on WebSphere Application Server v5.0. We are using MQ native APIs to connect to the qmgr.
| Quote: |
| An MQ error occurred, Completion code [2] Reason code [2058] Description[com.ibm.mq.MQManagedConnectionJ11@413ae2] |
2058 is expected only if we specify an incorrect qmgr name. But in this case, the application gets qmgr name from a properties file. The qmgr name is given correctly in the config properties file. And it's a running application in Production successfully for the last 5 years. Now there are no changes in the Application code or the configuration of the MQ qmgr. So this error looks weired. Would it be related to any thing specific to the box? It's a Sun Solaris 8 Operating system. Or could there be any qmgr log space issue? What is the possible solution?
I appreciate your help in regarding this.
Thanks,
Bharat |
|
| Back to top |
|
 |
| Bharat7 |
| Posted: Tue May 23, 2006 7:28 pm Post subject: |
|
|
Newbie
Joined: 23 May 2006
Posts: 8
|
I forgot to mention one thing. When we bounce the MQ qmgr and the application this problem is going away. The applicaition will be able to connect to the qmgr and put messages in queues. But the problem is coming back intermittently.
Thanks,
Bharat |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue May 23, 2006 7:39 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
OS MQVersion and CSD please.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Bharat7 |
| Posted: Wed May 24, 2006 2:13 am Post subject: |
|
|
Newbie
Joined: 23 May 2006
Posts: 8
|
OS: Solaris 8
MQ Series Server: Version 5.3 CSD 8
Java Application is on WebSphere Application Server V5.0 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed May 24, 2006 3:19 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Bharat7 wrote: |
OS: Solaris 8
MQ Series Server: Version 5.3 CSD 8
Java Application is on WebSphere Application Server V5.0 |
Between CSD06 and CSD11 there are some JMS problems especially if the client is not on the exact same CSD as the server. You might want to consider upgrading to CSD11 or CSD12 or even V6 RP1 FP1.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Bharat7 |
| Posted: Wed May 24, 2006 3:29 am Post subject: |
|
|
Newbie
Joined: 23 May 2006
Posts: 8
|
We are not using JMS or client connection to connect to the qmgr.
We are using MQ native Java APIs to connect to the servrer. The application sits on the same box as that of MQ Server.
Thanks,
Bharat |
|
| Back to top |
|
|
| Bharat7 |
| Posted: Wed May 24, 2006 3:32 am Post subject: |
|
|
Newbie
Joined: 23 May 2006
Posts: 8
|
We are using MQServer 5.3 and CSD05.
Thanks,
Bharat |
|
| Back to top |
|
|
| tleichen |
| Posted: Wed May 24, 2006 7:44 am Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
Make sure the queue manager name field that you are using is a full 48 characters long (padded with blanks). The qmgr name does not need to be that long, but the field must be. If the field length is variable, or shorter than the appropriate size, it will still try to grab 48 bytes from memory and probably pick up something that you don't want it to. 
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
| Bharat7 |
| Posted: Wed May 24, 2006 9:35 am Post subject: |
|
|
Newbie
Joined: 23 May 2006
Posts: 8
|
| There is no change in code. It works fine when we bounce the application (WebSphere Appl Server). After some time this problem is coming intermittently. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed May 24, 2006 9:38 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Maybe you are running out of connections on the queue manager.
Maybe the queue manager is down briefly.
Maybe you are running out of connections in the QCF pool.
Regardless, you should make sure that you are using the most recent FixPack of WAS v5.0. And really, actually, migrate to the most recent fix pack of at least WAS 5.1.
And you also should upgrade to MQ CSD12. There are known issues with Java connections in CSD/FP 8 and 9.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Bharat7 |
| Posted: Wed May 24, 2006 10:44 am Post subject: |
|
|
Newbie
Joined: 23 May 2006
Posts: 8
|
Thanks Jeff for your suggestion.
We are not doing client connection from a different box by using Server Connection channel. We are using MQ native APIs and connecting to the qmgr on the same box. In this case also, is there a chance of running out of connections?
If so where can we figure out that? Does it write to any logs? I don't see any errors in the logs. Can you please tell how to make sure of the connections? How to fix it?
Thanks,
Bharat |
|
| Back to top |
|
|
|
|
