| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ60 issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| knowhow |
 Posted: Mon Apr 23, 2007 7:27 am Post subject: MQ60 issue |
 |
|
Novice
Joined: 16 May 2006
Posts: 21
|
Hi,
Is there a way in MQ60 that we get a method for forcing the WebSphere MQ JMS classes to use ISOLATED bindings?
We upgraded MQ60 on AIX53 and one of our WebSphere JVM(5.1) was not able to communicate with MQ60 and throwing AMQ6207 errors in mq logs. We tried the possible workaround solutions given in www.ibm.com.
By adding the following stanza to the qm.ini file and restarting MQ you can avoid this problem:
Connection:
DefaultBindType=ISOLATED.
But still it didn't work.
Any thoughts??
Thanks. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Apr 23, 2007 9:19 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If you read the 6.0 manual it clearly states that the application (here WAS) needs to set an environment variable to allow for more then X (10 ?) entries in the shared memory segments table...
Alternatively have you tried running the app (WAS) with a 64 bit JVM ???
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| knowhow |
| Posted: Mon Apr 23, 2007 9:49 am Post subject: |
|
|
Novice
Joined: 16 May 2006
Posts: 21
|
Hi,
I think I mentioned that we are running WAS 5.1 version which we can't have a 64-bit Queue Manager. The problem is even after you set the EXTSHM value, the MQ JMS classes are overwriting them which is causing this issue. I am looking for a solution i.e if there is any fix or patch to apply on MQJMS so that they won't overwrite the settings.
Thanks. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Apr 23, 2007 11:03 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| knowhow wrote: |
Hi,
I think I mentioned that we are running WAS 5.1 version which we can't have a 64-bit Queue Manager. The problem is even after you set the EXTSHM value, the MQ JMS classes are overwriting them which is causing this issue. I am looking for a solution i.e if there is any fix or patch to apply on MQJMS so that they won't overwrite the settings.
Thanks. |
You mean to say 64 bit JVM.
You specified MQ V6.0 and on AIX this means your QMGR is 64 bit. So you don't need to specify the ESTSHM when you start the qmgr?
However WAS is a process running a JVM and that process is running a 32 bit JVM if my memory serves me well. This process will need the env variable to allow it to access more then 10 entries in the table.
Now if you can run WAS on a 64 bit JVM (WAS 6.x) you might get rid of that problem altogether...
The other way to reduce your memory footpring would be to take a critical look at the way the application accesses MQ and optimize what you can.
Enjoy
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
