| Author |
Message
|
| Vitor |
 Posted: Tue Sep 25, 2012 5:31 am Post subject: |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shashir wrote: |
WAS 6.1 uses WebSphere MQ Resource Adapter 6.0.2.1, so its WMQ client 6.x version
WAS 8.0.0.4 uses WebSphere MQ Resource Adapter 7.0.1.7, so its WMQ client 7.x version
WAS 6.1 & WAS 8.0.0.4 uses different WMQ clients. |
So given that the WMQ pub/sub was redesigned and reimplemented to WMQv7, it's hardly surprising that the clients behave differently is it?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| shashir |
| Posted: Tue Sep 25, 2012 5:40 am Post subject: |
|
|
Novice
Joined: 24 Sep 2012
Posts: 13
|
Yes, I think they are two different implementations and support jms spec at different levels.
I brought that WAS 6.1 into picture, to isolate the problem i.e. is it a MQ Server side problem or a WAS side problem.
Irrespective of whether its WAS 6.1, WAS 8.0.0.4 - the configuration on MQ Server is same.
Hope my interpretation is not confusing. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Sep 25, 2012 5:59 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shashir wrote: |
| Yes, I think they are two different implementations and support jms spec at different levels. |
I think the JMS spec, and WMQ's support of it, hasn't changed.
I know they are 2 different implementations of the client because you told me that. So why do you only think that?
| shashir wrote: |
| I brought that WAS 6.1 into picture, to isolate the problem i.e. is it a MQ Server side problem or a WAS side problem. |
And as a result, we've identified that it's potentially both. The v7 queue manager implements pub/sub in a way the v6 client does not expect (but is compatible with). The v6 and v7 clients mirror these differences.
| shashir wrote: |
| Irrespective of whether its WAS 6.1, WAS 8.0.0.4 - the configuration on MQ Server is same. |
But it will work differently with the 2 clients.
| shashir wrote: |
| Hope my interpretation is not confusing. |
In places, it's just plain wrong. But you've identified the issue even if you're trying to think your way out of it, round it and just in circles.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| nathanw |
| Posted: Tue Sep 25, 2012 6:01 am Post subject: |
|
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
Something that has happened in the past to me is teh following
| Code: |
If WAS Version 6 is being used on the server by java applications to connect to WMQ then ensure that the WAS environment variable MQ_INSTALL_ROOT is changed in the WAS administration console by an authorised WAS admin userid.
MQ_INSTALL_ROOT should be changed from default of:
‘${WAS_INSTALL_ROOT}/lib/WMQ’
where WAS_INSTALL_ROOT is
‘X:\X\IBM\WebSphere\AppServer’
to
‘X:\X\IBM\WebSphere MQ’
and WAS then should be restarted twice (to enable WAS to clear a cache). |
Just a thought
_________________
Who is General Failure and why is he reading my hard drive?
Artificial Intelligence stands no chance against Natural Stupidity.
Only the User Trace Speaks The Truth  |
|
| Back to top |
|
|
| shashir |
| Posted: Tue Sep 25, 2012 9:10 am Post subject: |
|
|
Novice
Joined: 24 Sep 2012
Posts: 13
|
Nathanw: Thank you for the details.
Coming back to the Topic object thing, Here is the reply from my Admins:
you do only configure a topic string in your configuration. MQ in v7 has TOPIC objects, but you probably don't specify that specifically. You specify a Stream to publish to with a topic string. The Stream essentially is the TOPIC object, if that makes any sense. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Sep 25, 2012 6:52 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| shashir wrote: |
Nathanw: Thank you for the details.
Coming back to the Topic object thing, Here is the reply from my Admins:
you do only configure a topic string in your configuration. MQ in v7 has TOPIC objects, but you probably don't specify that specifically. You specify a Stream to publish to with a topic string. The Stream essentially is the TOPIC object, if that makes any sense. |
Yes and No. The topic object will be used to authorize the topic. To access the topic you only need the topic string...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| shashir |
| Posted: Wed Sep 26, 2012 9:58 am Post subject: |
|
|
Novice
Joined: 24 Sep 2012
Posts: 13
|
Here is one of the ways to get it working.
One of my colleagues suggested me to set the Provider Version attribute on the topic connection factory configuration in WAS 8 admin console to 6
I set the above mentioned provider version to 6 and My application is now able to publish messages to the MQ topic.
It throws that same exception if I use the default value ( unspecified ) or 7 on provider version attribute.
Any ideas why it works with value 6
Thank you everyone for sharing your knowledge and experience on this topic... its a good learning for me. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Sep 26, 2012 10:07 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shashir wrote: |
| Any ideas why it works with value 6 |
Because that uses the old, out of support and one no longer working v6 method. The 7 value uses the correct method.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shashir |
| Posted: Wed Sep 26, 2012 10:47 am Post subject: |
|
|
Novice
Joined: 24 Sep 2012
Posts: 13
|
| Sure, If I want to use 7 in my WAS configuration.... where (MQ Server etc) and what changes need to be made? any pointers/links? |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Sep 26, 2012 11:07 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shashir wrote: |
| Sure, If I want to use 7 in my WAS configuration.... where (MQ Server etc) and what changes need to be made? any pointers/links? |
Everything that's been said in this thread.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shashir |
| Posted: Wed Sep 26, 2012 1:20 pm Post subject: |
|
|
Novice
Joined: 24 Sep 2012
Posts: 13
|
|
| Back to top |
|
|
|
|
