| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| MQRC 2053 and re-connect problems |
« View previous topic :: View next topic » |
| Author |
Message
|
| LouML |
 Posted: Mon Mar 17, 2008 9:49 am Post subject: MQRC 2053 and re-connect problems |
 |
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
Hello all.
I've recently installed MQ 6.0.2.3 on a Solaris x86 box in preparation for a particular applications migration to the latest MQ release. Currently that app is running on 5.3.12.
Just got a frantic call from the programmers who are extremely agitated. One of their apps has a problem where, when it receives a 2053 (queue full) reason code, it crashes when trying to reconnect. Besides the obvious questions (why are you trying to reconnect? why did you even disconnect?) has anyone heard of any such issues? I've asked them if they have recompiled their apps but have yet to hear back on that. I suspect this is not an MQ problem, but due to the nature of office politics, I've raised a PMR with IBM and am awaiting their response.
They claim this exact code does not crash on the 5.3.12 box.
The programmers exact wording is:
-----------------------------------------------------
When the queue is full, the write returns an error, it is correctly handled and logged. It msg can be seen in the log file.
When MR tries to connect again, it produces this stack trace.
The highlighted calls are all in MQ API.
The exact code runs perfectly fine in the MR QA environment.
current thread: t@4
[1] DoConnect(0x9d60b64, 0x0, 0x9d4c984, 0xfe42d890, 0xfe42d894, 0x0, 0x0, 0x0, 0x0), at 0xfe6fa58f
[2] zstMQCONN(0x9d60b64, 0x9d4c984, 0xfe42d890, 0xfe42d894, 0x0), at 0xfe6f8aba
[3] MQCONN(0x9d60b64, 0x9d4c984, 0xfe42d890, 0xfe42d894), at 0xfe971c89
[4] ImqMgr::connect(0x9d4c88c), at 0xfeb5d4d0
=>[5] StrMq::connect(this = 0x9d4c888), line 148 in "mq.cpp"
[6] StrMq::connect(this = 0x9d4c888, m = 0x9d84a00 "QM.MRBLADE1.01"), line 140 in "mq.cpp"
[7] WriteFixMsgToMqThread::WriteToQueue(outMgrName = CLASS, outQueName = CLASS, bin = CLASS), line 310 in "WriteFixMsgToMqThread.cpp"
[8] WriteFixMsgToMqThread::WriteToErrorQueue(this = 0x82f63a0, bin = CLASS), line 338 in "WriteFixMsgToMqThread.cpp"
[9] WriteFixMsgToMqThread::WriteData(this = 0x82f63a0, bulk = CLASS), line 288 in "WriteFixMsgToMqThread.cpp"
[10] WriteFixMsgToMqThread::ProcessMsgLoop(this = 0x82f63a0), line 223 in "WriteFixMsgToMqThread.cpp"
[11] WriteFixMsgToMqThread::QueueLoop(this = 0x82f63a0, qName = 0xfe42de6c "QL.MR.CLIENT.IN.ERROR"), line 190 in "WriteFixMsgToMqThread.cpp"
[12] WriteFixMsgToMqThread::run(this = 0x82f63a0), line 156 in "WriteFixMsgToMqThread.cpp"
[13] Thread::entry_point(_obj = 0x82f63a0), line 190 in "Thread.cpp"
[14] _thr_setup(0xfe430400), at 0xfec8fc42
[15] _lwp_start(), at 0xfec8ff30
-----------------------------------------------------
_________________
Yeah, well, you know, that's just, like, your opinion, man. - The Dude |
|
| Back to top |
|
 |
| LouML |
| Posted: Tue Mar 18, 2008 5:00 am Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
I'm beginning to hate this job.
IBM is waiting for us to send them trace files. They made this request after I had gone home for the evening. One of the developers thought he would do it himself. Apparently, he either knew the mqm password, or has root access. But either way, while trying to delete some trace files, he inadvertantly deleted /var/mqm/mqs.ini and /var/mqm/services.env.
I can't do a dspmq. There are mqm processes running. No matter what I do, I get an
AMQ8101: WebSphere MQ error (893) has occurred.
Is my only option now to delete everything and rebuild the queue manager from scratch?
_________________
Yeah, well, you know, that's just, like, your opinion, man. - The Dude |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 18, 2008 5:33 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| LouML wrote: |
| Is my only option now to delete everything and rebuild the queue manager from scratch? |
Not if someone's done a file system backup that has the missing files on it. Aside from that check out the FDC & see if there's any advice on that.
I'd also get a military-grade trout to the developer, find out who gave him the mqm password and/or the root password and use a nice, fresh trout on them.
Let this post be a warning to those of our readers who think dev environments don't need to be secured or controlled that tightly. You know who you are. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 18, 2008 5:36 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Vitor wrote: |
| Let this post be a warning to those of our readers who think dev environments don't need to be secured or controlled that tightly. You know who you are. |
| LouML wrote: |
| Is my only option now to delete everything and rebuild the queue manager from scratch? |
I'm confused.
If the developer broke it, why is it your problem to fix it?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 18, 2008 5:41 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jefflowrey wrote: |
| If the developer broke it, why is it your problem to fix it? |
Because developers never fix anything?
Because the adminisrator is always left to clear up any mess, the only joy left being the wielding of fish in a spirited & agressive manner?
Because the development environment is like a baby - everybody wants to play with it until it poops itself, then suddenly no-one wants to know?
It's an unjust situation.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| LouML |
| Posted: Tue Mar 18, 2008 6:05 am Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
The developer is good for nothing, except now making such wonderful comments as:
Yes, I deleted files my mistake. My bad. Let me know when the Queue Manager is back up.
Can't we just install the same version as we had on out other test box? (Answer - No, because:
A - you guys chose a Solaris x86 box for this new install and the only version available for that is 6.0 while the other box is a Solaris Sparc on 5.3
B - 5.3 is out of support)
I Googled MQ 6.0 and did you know that there are many patches to be installed? (Answer - Yes, I know. We are at 6.0.2.3)
Meanwhile, I've stopped all mqm processes, deleted the associated /var/mqm/qmgrs and /var/mqm/log directories.
I tried to do a crtmqm but still get:
AMQ8101: WebSphere MQ error (893) has occurred.
_________________
Yeah, well, you know, that's just, like, your opinion, man. - The Dude |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 18, 2008 6:08 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| LouML wrote: |
The developer is good for nothing, except now making such wonderful comments as:
Yes, I deleted files my mistake. My bad. Let me know when the Queue Manager is back up. |
Trout....trout.....trout...... 
| LouML wrote: |
Meanwhile, I've stopped all mqm processes, deleted the associated /var/mqm/qmgrs and /var/mqm/log directories.
|
Erm.... why? If 2 files have been accidently deleted, is deliberately deleting more stuff really going to help? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 18, 2008 6:17 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You should maybe have been able to move mqs.ini from somewhere else and tweak - it is just a text file.
I don't know about services.env...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| LouML |
| Posted: Tue Mar 18, 2008 6:23 am Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
| Vitor wrote: |
| LouML wrote: |
The developer is good for nothing, except now making such wonderful comments as:
Yes, I deleted files my mistake. My bad. Let me know when the Queue Manager is back up. |
Trout....trout.....trout......
| LouML wrote: |
Meanwhile, I've stopped all mqm processes, deleted the associated /var/mqm/qmgrs and /var/mqm/log directories.
|
Erm.... why? If 2 files have been accidently deleted, is deliberately deleting more stuff really going to help? |
Because I'm stuck with 'AMQ8101: WebSphere MQ error (893) has occurred' for anyting I try. This is a new machine, not in production. We do not have any backups of the /var/mqm directory.
I'm going to delete the Queue Manager and start over.
_________________
Yeah, well, you know, that's just, like, your opinion, man. - The Dude |
|
| Back to top |
|
|
| LouML |
| Posted: Tue Mar 18, 2008 6:37 am Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
| jefflowrey wrote: |
You should maybe have been able to move mqs.ini from somewhere else and tweak - it is just a text file.
I don't know about services.env... |
Actually, it was /var/mqm/service.env.
Anyway, you were correct. I was able to create a new mqs.ini file. Of course, since I had already deleted the ququ manager directories, I had to continue on my mission.
I was then able to execute the dspmq, dtlmqm, crtmqm and strmqm commands and load the configuration file successfully.
Now, back to the original problem...
_________________
Yeah, well, you know, that's just, like, your opinion, man. - The Dude |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 18, 2008 6:58 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| LouML wrote: |
| Now, back to the original problem... |
Well as you correctly pointed out in your original post, their problem reconnecting after a 2053 error would be resolved if they didn't disconnect in response to a 2053!
The reconnect shouldn't crash, so a PMR is clearly the route to take, but a short to medium term fix would be to change the code to do something more sensible. Like waiting a few seconds and re-trying the put, and disconnecting only if 10 (20/30/40/etc) consecuative puts fail.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| LouML |
| Posted: Tue Mar 18, 2008 7:15 am Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
| Vitor wrote: |
| LouML wrote: |
| Now, back to the original problem... |
Well as you correctly pointed out in your original post, their problem reconnecting after a 2053 error would be resolved if they didn't disconnect in response to a 2053!
The reconnect shouldn't crash, so a PMR is clearly the route to take, but a short to medium term fix would be to change the code to do something more sensible. Like waiting a few seconds and re-trying the put, and disconnecting only if 10 (20/30/40/etc) consecuative puts fail. |
Of course I could tell them that, but they will respond with It works on the other server!
IBM has a copy of the traces so we'll see what they say.
Let me know when you've shipped the trout!
_________________
Yeah, well, you know, that's just, like, your opinion, man. - The Dude |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 18, 2008 7:33 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| LouML wrote: |
| Let me know when you've shipped the trout! |
You'll need to contact SAFraser, official supplier of quality trout to the WMQ community.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 18, 2008 7:38 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Vitor wrote: |
You'll need to contact SAFraser, official supplier of quality trout to the WMQ community.
|
Among other things, Vitor would only be able to supply metric trout.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 18, 2008 7:53 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jefflowrey wrote: |
| Vitor wrote: |
You'll need to contact SAFraser, official supplier of quality trout to the WMQ community.
|
Among other things, Vitor would only be able to supply metric trout. |
Don't forget the UK has exemptions from the EU from many metric measures. I also supply imperial / metric conversion kits (at additional charge).
(I also run imperial trout across the border in violation of EU directives. Many old sites still run imperial trouting).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
|
  |
Goto page 1, 2 Next |
Page 1 of 2 |
|
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
|
|
|
|
