| Author |
Message
|
| aldarwiche |
 Posted: Tue May 05, 2009 12:06 pm Post subject: problems with WAS 5.1.1 and mqm 5.3.0.7 |
 |
|
Newbie
Joined: 05 May 2009
Posts: 1
|
was listeners and channels keep on dying, and can not connect to mqm. Was throws error 2009 and FDC has this porb id: ZD005030.
Any Clue or Idea will be appreciated. Thanks; |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue May 05, 2009 2:45 pm Post subject: Re: problems with WAS 5.1.1 and mqm 5.3.0.7 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| aldarwiche wrote: |
| Any Clue or Idea will be appreciated. Thanks; |
WMQv5.3.0.7? 
Apply maintenance at the very least. If you look up that probe id you'll see a number of problems fixed in versions of v5.3 that worked.
Better still, move to v6 or even v7.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed May 06, 2009 2:50 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You are out of maintenance for both MQ and WAS.
Be aware that in those early days you might have needed to upgrade WAS as well as MQ for them to work nice in tandem.
Upgrade... upgrade... upgrade (Was 6.1 or WAS 7 and MQ 6.0.2.6 or MQ 7.0.0.1) 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| tbully |
| Posted: Wed May 06, 2009 5:56 am Post subject: |
|
|
Newbie
Joined: 06 May 2009
Posts: 6
|
Hello! I'm Al's client and working with him to solve this issue. I lurk here often but never had the need to post. (basically because the wealth of knowledge on this site and good search indexing - THANK YOU)
While I agree with (and am embarrassed by) the fact that we're way beyond maintenance, upgrading is not an option at this point. (minor releases of MQ could be possible) The main reason we haven't opened a PMR is because I'm afraid IBM will tell us the same thing. 
An upgrade would have to be executed through several environments and effect 50+ developer's workstations.
This identical deployment is working fine in other environments so this must be a configuration / environmental issue.
Any help would be appreciated! |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 06, 2009 6:04 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| tbully wrote: |
| The main reason we haven't opened a PMR is because I'm afraid IBM will tell us the same thing. |
You think? 
It's all part and parcel of the "out of support" concept
| tbully wrote: |
| An upgrade would have to be executed through several environments and effect 50+ developer's workstations. |
Then the sooner you start, the sooner you'll finish (Great Poobah save me, I'm turning into my mother!). Seriously, take the hit. It's not that many environments; I doubt all the workstations have server side code installed. If they have, you might get a better response from IBM with all that license you're paying.
As a minimum, move off CSD 7. It was just contact admin. Go to CSD 11 at least.
| tbully wrote: |
| This identical deployment is working fine in other environments so this must be a configuration / environmental issue. |
Possibly, but CSD 7 was a bit funky and capable of breaking by itself. I also put it to you that the time you spend tracking this down will be greater than the time taken upgrading your site.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 06, 2009 6:11 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| tbully wrote: |
This identical deployment is working fine in other environments so this must be a configuration / environmental issue.
|
You don't mention platform in use, but Mr Google seems to think that problem is more concerned with migration issues. You seem to have a running server (and I'm guessing you've not migrated to CSD 7 recently!) that keeps throwing 2009 reason codes.
From this, Mr Google and I think you've found something new - possibly because you're running on Windows. If you're not going to move to a working level of software, best advice is to keep bouncing the queue manager when it happens.
While kicking yourself (or the appropriate management) for letting yourself get so far behind on maintenance. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| tbully |
| Posted: Wed May 06, 2009 6:20 am Post subject: |
|
|
Newbie
Joined: 06 May 2009
Posts: 6
|
| Vitor wrote: |
| tbully wrote: |
This identical deployment is working fine in other environments so this must be a configuration / environmental issue.
|
You don't mention platform in use, but Mr Google seems to think that problem is more concerned with migration issues. You seem to have a running server (and I'm guessing you've not migrated to CSD 7 recently!) that keeps throwing 2009 reason codes.
From this, Mr Google and I think you've found something new - possibly because you're running on Windows. If you're not going to move to a working level of software, best advice is to keep bouncing the queue manager when it happens.
While kicking yourself (or the appropriate management) for letting yourself get so far behind on maintenance. |
Vitor -
I appreciate your responses. As usual, you always have good feedback.
Upgrading is a long term goal but not to get this environment operational - business and management.
The OS is Solaris 10 (5.10 Generic_138888-01). The MQ "software" and manager was installed by the WAS installer. This connection failure happens from the get-go. It never connects. The QM starts and we're able to connect to it just fine with MQ Explorer. The QM is local to the App server so the normal 2009 troubleshooting is out. (firewalls, etc) Interesting fact: When connected using MQ Explorer and you try to start the listener, your MQ Explorer connection (using the SYSTEM.ADMIN.SVRCONN channel - of course) gets dumped. A reconnect of MQ Explorer fixes the issue. Websphere is using it's own channel - WAS.JMS.SVRCONN. |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Wed May 06, 2009 6:26 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| I had 2009 errors constantly previously when WAS and MQ were located on the same box. Took me a while to find the solution but.... When WAS and MQ are on the same box, ensure WAS uses the MQ jars thats ship with MQ (and not WAS) |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 06, 2009 6:32 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| tbully wrote: |
| The OS is Solaris 10 (5.10 Generic_138888-01). |
You're running v5.3.7 on this? Gosh.
This underlines my point. You have a small number of Solaris boxes to upgrade; this "50+ developer workstations" is neither here nor there because they're not going to have server installed; if you've paid for Solaris licenses, you're not going to waste money on 50+ Windows licenses.
Upgrades to WMQv6 or v7 will only cost you time. And less time than this probably.
I'd say you've got serious issues. Possibly a bad install. (Or a bad version. )
If it's a new server that's never worked (and you have other servers on the same Solaris version) reinstall.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| tbully |
| Posted: Wed May 06, 2009 8:07 am Post subject: |
|
|
Newbie
Joined: 06 May 2009
Posts: 6
|
| Vitor wrote: |
| tbully wrote: |
| The OS is Solaris 10 (5.10 Generic_138888-01). |
You're running v5.3.7 on this? Gosh.
This underlines my point. You have a small number of Solaris boxes to upgrade; this "50+ developer workstations" is neither here nor there because they're not going to have server installed; if you've paid for Solaris licenses, you're not going to waste money on 50+ Windows licenses.
Upgrades to WMQv6 or v7 will only cost you time. And less time than this probably.
I'd say you've got serious issues. Possibly a bad install. (Or a bad version. )
If it's a new server that's never worked (and you have other servers on the same Solaris version) reinstall. |
The issue is upgrading the 50+ machines from WSAD to RAD. (not to mentioning training the staff and regression testing our custom apps against new versions of WAS / jdk...as well as making the necessary changes from that QA process)
I don't want to debate why I've not upgraded. Mainly because your lecture sounds like me when I'm speaking with our development and project leads.
My hands are simply tied. End of story for now...
I'll keep working on a solution. If I find one, I'll post it here. There must be at least one poor sap on this planet that is stuck in the dark ages with me.
 |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 06, 2009 9:37 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| tbully wrote: |
Mainly because your lecture sounds like me when I'm speaking with our development and project leads.
...
My hands are simply tied. End of story for now... |
Go in peace; may the Trout be with you. 
| tbully wrote: |
| There must be at least one poor sap on this planet that is stuck in the dark ages with me. |
But are they using WAS and Solaris 10?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed May 06, 2009 8:13 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
| The OS is Solaris 10 (5.10 Generic_138888-01). The MQ "software" and manager was installed by the WAS installer. This connection failure happens from the get-go. It never connects. The QM starts and we're able to connect to it just fine with MQ Explorer. The QM is local to the App server so the normal 2009 troubleshooting is out. (firewalls, etc) Interesting fact: When connected using MQ Explorer and you try to start the listener, your MQ Explorer connection (using the SYSTEM.ADMIN.SVRCONN channel - of course) gets dumped. A reconnect of MQ Explorer fixes the issue. Websphere is using it's own channel - WAS.JMS.SVRCONN. |
Nice paradox here. I don't remember if MQ 5.3 was ever homologated on Solaris 10. My memory seems to be stuck with Solaris 8 or Solaris 9... Looks like you upgrade the OS fine but not the applications?
Forget the 100 PC's. Upgrade your server to at least MQ 6.0.2.6 or MQ 7.
The connections should then just work from the older client...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| tbully |
| Posted: Thu May 07, 2009 5:41 am Post subject: |
|
|
Newbie
Joined: 06 May 2009
Posts: 6
|
| fjb_saper wrote: |
| Quote: |
| The OS is Solaris 10 (5.10 Generic_138888-01). The MQ "software" and manager was installed by the WAS installer. This connection failure happens from the get-go. It never connects. The QM starts and we're able to connect to it just fine with MQ Explorer. The QM is local to the App server so the normal 2009 troubleshooting is out. (firewalls, etc) Interesting fact: When connected using MQ Explorer and you try to start the listener, your MQ Explorer connection (using the SYSTEM.ADMIN.SVRCONN channel - of course) gets dumped. A reconnect of MQ Explorer fixes the issue. Websphere is using it's own channel - WAS.JMS.SVRCONN. |
Nice paradox here. I don't remember if MQ 5.3 was ever homologated on Solaris 10. My memory seems to be stuck with Solaris 8 or Solaris 9... Looks like you upgrade the OS fine but not the applications?
Forget the 100 PC's. Upgrade your server to at least MQ 6.0.2.6 or MQ 7.
The connections should then just work from the older client...
|
Not really a paradox. Hardware breaks, software doesn't - that's "their" view, anyway.
The hardware was upgraded by our ops group but dev has been slow to respond to our needs to upgrade the middleware.
Honestly, I'm tired of defending our (silly) reasons for not upgrading. I was hoping for a little help from this great community.
As stated before, I'll provide an update once I find a fix. (I will find a fix, btw.) Maybe it'll help someone.
People telling me we're stupid for not upgrading is not helping my situation. I understand the silliness here. The plans are in place to upgrade but this will not be available for 10-12 mos.
Thanks for everyone's concern nonetheless. (I'm really surprised nobody else has been caught in this "paradox". I need to work where you guys do!!) |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu May 07, 2009 5:52 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You should, at a minimum, be able to upgrade MQ to v5.3 CSD 14.
This will not in any way affect your WSAD desktops, nor even your WAS runtime.
it should go a few steps towards eliminating your connection difficulties, as it will incorporate probably thousands of individual fixes for various issues at least one of which may be contributing to your actual problem. |
|
| Back to top |
|
|
| tbully |
| Posted: Thu May 07, 2009 7:19 am Post subject: |
|
|
Newbie
Joined: 06 May 2009
Posts: 6
|
| mqjeff wrote: |
You should, at a minimum, be able to upgrade MQ to v5.3 CSD 14.
This will not in any way affect your WSAD desktops, nor even your WAS runtime.
it should go a few steps towards eliminating your connection difficulties, as it will incorporate probably thousands of individual fixes for various issues at least one of which may be contributing to your actual problem. |
Thanks Jeff - agreed.
I have the CSD downloaded and will look at doing that ASAP. |
|
| Back to top |
|
|
|
|
