| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| 2059 Error under load |
« View previous topic :: View next topic » |
| Author |
Message
|
| kirani |
 Posted: Wed Aug 04, 2004 6:15 am Post subject: 2059 Error under load |
 |
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
We are having weird problems with our COM components when making connection to the queue manager. Sometimes they get 2059 error code. Object pooling is set on the COM components, but they make a connection to the queue manager only when a method is called that will bring data from the backend system. This problem happens under the load as the number of users goes high. It works OK after the user retries the transaction after getting this error. Any clues as to what might be the problem here.
Env Details:
Windows 2000
WMQ 5.2 CSD5
COM components connect to the queue manager in server binding mode. They use MQ wrapper classes from shared DLL.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
 |
| kirani |
| Posted: Wed Aug 04, 2004 6:28 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
We don't see any errors in the event viewer or the MQ logs when this happens.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| kirani |
| Posted: Thu Aug 05, 2004 9:28 pm Post subject: 2059 Error under load [Closed] |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
OK, here is an update.
Since it's a production server we cannot do any test on it, but we replicated the problem via a client box connecting to the server queue manager. Its not the same setup, but it was enough to identify the the problem. We turned on the trace on MQSeries to capture all info. In the trace we found that connection handle was -999. I guess it was not getting handle or the memory was getting overwritten. This component had some memory leaks and threading issues also. So when the developer fixed his code for threading and memory problem, it started to work fine. It's been more than 48 Hrs now and we have not seen this problem occur again.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| 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
|
|
|
|
