| Author |
Message
|
| aboggis |
 Posted: Wed Sep 10, 2003 4:32 pm Post subject: 2009 Errors on client (MQRC_CONNECTION_BROKEN) |
 |
|
Centurion
Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California
|
I seem to be getting some 2009 errors on a client application, but with no corresponding errors on the queue manager logs.
I'm still in the research phase, so I don't have much more info at this point...
But curious to know if anyone else has experienced this?
Regards,
tonyB. |
|
| Back to top |
|
 |
| Prahasith |
| Posted: Wed Sep 10, 2003 7:49 pm Post subject: |
|
|
Disciple
Joined: 16 May 2003
Posts: 184
Location: Kansas City
|
| It might be the Queue manager has been restarted and your connection has been broken. Restart your application and you should be fine. |
|
| Back to top |
|
|
| aboggis |
| Posted: Wed Sep 10, 2003 9:31 pm Post subject: |
|
|
Centurion
Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California
|
| No. The queue manager has benn active constantly. |
|
| Back to top |
|
|
| Remco |
| Posted: Thu Sep 11, 2003 12:17 am Post subject: |
|
|
Acolyte
Joined: 19 Mar 2002
Posts: 68
Location: Capelle aan den IJssel (Rotterdam)
|
What platform are you on, and what version ??? Windows NT/2000 ???
If so, have you installed the client from the server CD or, from the Client CD. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Sep 11, 2003 12:43 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| The most common reason that I've seen for 2009 errors is not having the most up-to-date version of the MQ code (specifically the jar files). It seems to happen the most with WAS and WSAD since they require one of the MQ CSDs. |
|
| Back to top |
|
|
| Heidils |
| Posted: Thu Sep 11, 2003 4:57 am Post subject: |
|
|
Novice
Joined: 25 May 2003
Posts: 11
Location: SA
|
Hi Tony
We've just gone through a very long month of getting MQRC 2009 and MQRC 2019 as well as MQRC 2018.
Our environment: MQ Series 5.3 on Windows NT. We have a 3rd party client that uses Java/JMS to connect to a client server (and then later a full Mq serverinstallation) and then remote queues on a local Queue Manager to the main MQ server and queue Queue manager. (The 3rd party's installation is running on Linux Redhat)
Our first mistake was that the installation was not 100% correct (should have been done as the Admin / Root user and not any other user) and apparently some of the java files/classes was no installed with the first try.
Having fixed this we still got the error and after a lot of late nigths finally realised that the JMS/Java client was opening up multiple threads/connections to the queues but only closing the last thread. We then eventually ran out of channels (max was set to 256) and that would be the reason for the above errors. (If you did a dis chstatus(*) we could see 100's of channels still open even though not activity was taking place).
Having solved the problem of closing the connections properly we are now running very stable and will hopefully never see those contact admin errors again !
Hope this gives you an idea of where to start looking
Cheers
Heidi-Lize
 |
|
| Back to top |
|
|
| aboggis |
| Posted: Thu Sep 11, 2003 8:52 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California
|
AFAIK all the client code is C/C++ based (in fact the Java VM is not even installed on the hosts), running on Solaris environments.
BUT... that certainly does give me a starting point.
This is not the only problem too... |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sat Sep 13, 2003 3:35 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Anything that causes your connection to drop will give your app this return code. The QM bouncing is one of the reasons. But the more common one is network burps. No network connection = a broken MQ connection for clients = a 2009.
This is not the only reason for 2009, but the most common one I think.
The other common reason is that your channel definitions (MQCONNX, MQSERVER, defs in the channel table) for the client side are misspelled. But this reason will only give you a 2009 on the initial connect attempt. Not your scenario I think.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| aboggis |
| Posted: Fri Oct 24, 2003 10:15 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California
|
Just bringing this one back up... although less frequently, we are still seeing this issue.
The applications concerned are server apps (C++, no Java), running on the same box as the queue manager and are using server bindings (linking with libmqm.so), and connect using MQCONN, supplying the queue manager name (there is no default queue manager defined).
Upping the MaxChannels and MaxActiveChannels in qm.ini helped somewhat, but (to quote the movie) "theyrrrrreeeeee baaaaaaack" 
Additional info:Solaris 5.8
MQ 5.2 CSD06 (I know CSD07 is availbale)
Applications linked with libmqm.so
There are no MQ environment variables defined (no MQSERVER).
This host has only two queue managers defined.
The queue manager is a member of a cluster (six qmgrs total). I'm not getting anything obvious in the error logs (neither the global or the queue manager local). Nothing that would indicate a server error prior to the application getting a reason code of 2009. |
|
| Back to top |
|
|
| Nathan |
| Posted: Fri Oct 24, 2003 11:00 am Post subject: |
|
|
Acolyte
Joined: 15 Sep 2003
Posts: 52
Location: Rochester, NY
|
The 2009 errors are received by clients. I have seen this error too.
If your code is running on the same server, why not set it up to connect directly and not use the client connection? |
|
| Back to top |
|
|
| yaravind |
| Posted: Fri Oct 24, 2003 11:36 am Post subject: |
|
|
Apprentice
Joined: 17 Jun 2002
Posts: 25
|
We have experienced the same issues and here is my feedback based upon my experience
1. Once this happened due to the network (TCP) issues
2. The message channels reached to the maximum channel limit set at the Qm level. Subsequent connections to the QM reslted in 2009 |
|
| Back to top |
|
|
| aboggis |
| Posted: Fri Oct 24, 2003 11:36 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California
|
| Quote: |
| The 2009 errors are received by clients. I have seen this error too. |
However, as I stated these are SERVER applications, linked with the server bindings (libmqm.so). I do not have the power (nor the inclination) to change this, since that would require an architectural change request from management. There's no reason to change the way the applications are built.
There is also the additional performance overhead that would be incurred by switching to a client-based mode. These applications are intended to run on the same box as the queue manager. It would introduce unneccessary overhead in sending/receiving data via either the loopback address (127.0.0.1) or the host's IP address (even though there are multiple gigabit ethernet cards installed. This machine has 24 CPUs and 96 Gb of RAM. Performance is critical to this application. |
|
| Back to top |
|
|
| aboggis |
| Posted: Fri Oct 24, 2003 11:40 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California
|
| yaravind wrote: |
| 1. Once this happened due to the network (TCP) issues |
We have not seen any network issues. Plus these are server applications, so there's no network activity per se, since the applications are directly connected to the queue manager.
| yaravind wrote: |
| 2. The message channels reached to the maximum channel limit set at the Qm level. Subsequent connections to the QM reslted in 2009 |
I have already bumped up the MaxChannels/MaxActiveChannels to 1000 (default is 100), and it did aleviate the problem somewhat. I'll try more... |
|
| Back to top |
|
|
| aboggis |
| Posted: Fri Oct 24, 2003 12:58 pm Post subject: |
|
|
Centurion
Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California
|
| yaravind wrote: |
| 1. Once this happened due to the network (TCP) issues |
We have not seen any network issues. Plus these are server applications, so there's no network activity per se, since the applications are directly connected to the queue manager.
| yaravind wrote: |
| 2. The message channels reached to the maximum channel limit set at the Qm level. Subsequent connections to the QM reslted in 2009 |
I have already bumped up the MaxChannels/MaxActiveChannels to 1000 (default is 100), and it did aleviate the problem somewhat. I'll try more... |
|
| Back to top |
|
|
| aboggis |
| Posted: Tue Apr 13, 2004 4:36 pm Post subject: |
|
|
Centurion
Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California
|
I am seeing a re-occurrence of this error and would like some pointers in tracking it down.
These are server connections - the application is running on the same host as the queue manager, so any of the commands to watch TCP/IP connections isn't going to help me.
The MaxChannels and MaxActiveChannels in qm.ini have been bumped up to 5000. It seems (according to application error logs - not MQ error logs) to be occurring in MQGET's.
Because nothing is getting recorded in the MQ error logs I sort of stabbing in the dark in trying to resolve this issue. Whilst I'd like to point the finger at the application (and thus shift the blame!) I don't have any evidence to back me up. |
|
| Back to top |
|
|
|
|
