|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
I told them.... |
« View previous topic :: View next topic » |
Author |
Message
|
csmith28 |
Posted: Tue Dec 06, 2005 5:47 pm Post subject: I told them.... |
|
|
 Grand Master
Joined: 15 Jul 2003 Posts: 1196 Location: Arizona
|
and I told them.
and I told them
and I told them
and I told them
and I told them
the reason you are getting a 2058 is because their code was probably clobbering a pointer parameter. But OOOOOOOH NOOOooooooooo!
It has to be a problem with MQSeries.
In spite of the fact that I have at least ten other applications using JAVA to connect to the same MQManager and they are all working just fine. No one was secretly loging on to my MQManager server and deleting the MQManager and re-creating it with another name then surripticiously changing it back. They tried leaving the MQManagerName field blank. Still, 2058's.
So under duress I open an IBM Ticket. I know it won't do any good but what do I know anyway. All I have to give them is, "This Weblogic application starts up and works just fine for a while then suddenly it starts getting 2058 MGR_NAME_ERROR." So we go through the whole mess of what version of the OS are you running, what version MQServer, what version of the client, mining application logs, App Server OS, WebLogic Version, blah, blah, blah.....
The WMQ Clients were never properly installed on the WebLogic Application Servers and my MQManager was at 5.3.0.6.
So I got exactly the same answer from IBM that I expected to get. Do a full Client installation on the application servers and patch them to 5.3.0.11 and then patch the MQManager Server to 5.3.0.11. Then call us back if there's still a problem.
After having done so it's six weeks later and the problem remained but just for this one application. Could it be a problem with the code? Of course not. It has to be a problem with MQSeries so I call IBM and they say roughly the equvalent of what I said at the very start.
Fine, I pretty much snapped at this point. Actually the snapping point was a smug little email that the lead developer sent questioning not only the level of support that I was providing but my skills and whether they should consider using another product in the future. I mean I really layed into this guy.
I didn't actually use any foul language, I would have been fired but I did say some things that were at the very worst UN-PROFESSIONAL
So anyways, it's three weeks later and for some reason I haven't heard from these guys at all. Not a word so yesterday I send an email to the developer that I got written up for dressing down and CC a few other people in my department who had been involved in this mess and today I got this as part of an attachment. Not from the developer in question but it is quote from his email:
Quote: |
Here is what happens
1) when you bounce the server APP-1 starts first.
Its threads are started and they continuously listen to APP-1 queues
Now any first request to APP-2 resets the environment variable to APP-2 host/port/channel.
At this time APP-1 is unaffected as its threads are already listening.
2) Now if you either redeploy APP-1 or restart the threads for that, it messes up MQEnvironment for APP-2
And sets it back to APP-1 host/port/channel.
Now every request for APP-2 after this will try to connect to right queueManager name but guess what?
To a wrong host/port/channel (MQEnvironment is set to APP-1).
There is a reason why logs showed good MQ host as we wrote it out of config object, not from MQEnvironment.
If we redeploy APP-2 at this point it loads the APP-2Config and sets everything back up.
And everything works well till APP-1 tries to reconnect/refresh. |
From the date stamp on the attached email this was discovered about two weeks ago. I and my Leads were intentionally left off the distribution list for this email.
Tomorrow I'm fixen to  _________________ Yes, I am an agent of Satan but my duties are largely ceremonial.
Last edited by csmith28 on Wed Dec 07, 2005 7:06 am; edited 1 time in total |
|
Back to top |
|
 |
sebastianhirt |
Posted: Wed Dec 07, 2005 1:37 am Post subject: |
|
|
Yatiri
Joined: 07 Jun 2004 Posts: 620 Location: Germany
|
Chris,
I know it is not funny. And I feel really sorry for you. But I have to admit, that when I was reading this I was literally rolling over the floor, laughing.
What a bunch of schmucks!
Cheer up... It can only get better!
cheers
Sebastian |
|
Back to top |
|
 |
Toronto_MQ |
Posted: Wed Dec 07, 2005 6:29 am Post subject: |
|
|
 Master
Joined: 10 Jul 2002 Posts: 263 Location: read my name
|
Wow. It's like we work in the same office. |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Dec 07, 2005 6:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
So...
This is the job you're being laid off from...? _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
csmith28 |
Posted: Wed Dec 07, 2005 7:02 am Post subject: |
|
|
 Grand Master
Joined: 15 Jul 2003 Posts: 1196 Location: Arizona
|
jefflowrey wrote: |
So...
This is the job you're being laid off from...? |
No not laid off, just transitioning all my MQSeries work to another Group. Then I will be doing UNIX/NT Server builds and OS Support. _________________ Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Dec 07, 2005 7:26 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Right.
Still... it almost sounds like a good move! _________________ I am *not* the model of the modern major general. |
|
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
|
|
|
|