| Author |
Message
|
| RangaKovela |
 Posted: Wed Jun 22, 2011 8:58 pm Post subject: MQ 6.0.2.1 server with MQ 6.0.2.8 client compatibility |
 |
|
Apprentice
Joined: 10 May 2011
Posts: 38
|
Hi MQ experts ,
environment :Solaris 10 NGZ (virtualized -MQclients from one zone connecting MQ server in JMS client mode )
We want to utilize com.ibm.mq.tuning.socketConnectTimeout facility made available in 6.0.2.8 (<http://www-01.ibm.com/support/docview.wss?uid=swg1IZ53228&wv=1>) in order to protect the application servers from thread blockages. Currently Our app server MQ clients and server are running with 6.0.2.1 and we wanted to know whether we could uplift just the client to 6.0.2.8 version so that the facility to set sockettimeout can be utilised. We were thinking of just uplifting the client and not the server due to prj funding issues .We have tested the set-up and it works fine .Do you foresee any compatibility issues .Is it good idea to support this kind of set-up in production ? 
Many thanks . .. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Jun 23, 2011 1:16 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Not without a full migration plan to MQ v7 in place before hand, as MQ v6 goes out of support within the next year. |
|
| Back to top |
|
|
| RangaKovela |
| Posted: Thu Jun 23, 2011 1:37 am Post subject: |
|
|
Apprentice
Joined: 10 May 2011
Posts: 38
|
| Yes we have plan to Migrate to MQv7 |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 23, 2011 4:44 am Post subject: Re: MQ 6.0.2.1 server with MQ 6.0.2.8 client compatibility |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| RangaKovela wrote: |
| Is it good idea to support this kind of set-up in production ? |
No.
Not only are you running limited shelf life software (v6) but the server code is seriously back level (why still 6.0.2.1? Why no maintenance) and you're using Solaris Zones. So you've tested it and it works; that's fine. You put it in production, it will probably work, that's fine.
It breaks unexpectedly one day - what's your plan? Assuming v6 is still in support at that point, first suggestion will be "get the servers to 6.0.2.8".
So why not do that now? Better still, advance your migration plan to v7 and avoid a step.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Jun 23, 2011 4:13 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
There is nothing wrong with newer clients connecting to older Queue Managers. By design MQ allows that.
MQ 6 is still supported for more than a year. Upgrading to MQ 7 is a good thing, but has nothing to do with the OP. Upgrading MQ Clients to MQ 7 is not something to be flip about, especially with all the grief related to Java/JMS clients and conversion in MQ 7.0.1.* .
More relevant would be to suggest going to the latest 6.0.2.* client instead only up to 6.0.2.8 if you are going to bother with an MQ Client upgrade.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jun 23, 2011 8:24 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
 with Peter and would go one step further...
If you intend staying @ 6.0.2.x, create a project to upgrade both Server and clients to the latest level. So should disaster strike you can open a PMR and not get the standard response: "Upgrade to latest level and let us know if the problem is still there"... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
