| Author |
Message
|
| duffMan |
 Posted: Mon Oct 20, 2008 3:54 pm Post subject: DefaultBindType=ISOLATED |
 |
|
Voyager
Joined: 03 Jun 2002
Posts: 75
|
Does anyone have experience using this for qm.ini setting for queue managers connected to by 32-bit WAS instances on AIX? (binding mode)
We're experiencing some issues with MQv6.0.2.4 (64-bit) and WAS5.1 (32-bit).
We've set the EXTSHM variable on both WAS (root) and queue manager (mqm)...but still am getting strange memory issues. (WAS memory problems...not MQ)
technote from IBM has a list of "other" suggestions for unusual situations ...one of which is DefaultBindType=ISOLATED.
Can't find much documentation for this, and am a bit apprehensive in blindly setting it... wanted to see anyone had any other experiences of information on this topic that I could not find. |
|
| Back to top |
|
 |
| gbaddeley |
| Posted: Mon Oct 20, 2008 5:07 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
|
| Back to top |
|
|
| duffMan |
| Posted: Mon Oct 20, 2008 7:02 pm Post subject: |
|
|
Voyager
Joined: 03 Jun 2002
Posts: 75
|
thanks.
We have v6.0.2.4 and have set EXTSHM on both the qmgr as WAS profile.
What we are experiencing now is that Websphere crashes because it has run out of native heap. We have reduced the Java heap in an effort to free up some memory for the native....and we'll see what happens.
If this doesn't work then we'll either go to CLIENT connection or try the ISOLATED bindings.
we do have an IBM WAS expert looking at this too....so we'll see what they come up with.
man...I wish we'd get to 64-bit apps. |
|
| Back to top |
|
|
| zboy |
| Posted: Mon Oct 20, 2008 11:03 pm Post subject: |
|
|
Novice
Joined: 01 Oct 2008
Posts: 13
|
ISOLATED will not help with heap problems
it is to do with not using IPC memory to communicate between app and qmgr, but using sockets instead
this is an example of a quite common false syllogism
we must do something..
this is something..
let's do this!
this is most often found in excutive and management circles
it is quite rare in technical staff, who usually like to think through the consequences of actions before they do them |
|
| Back to top |
|
|
| ranganathan |
| Posted: Mon Oct 20, 2008 11:50 pm Post subject: |
|
|
Centurion
Joined: 03 Jul 2008
Posts: 104
|
| duffMan wrote: |
man...I wish we'd get to 64-bit apps. |
Upgrade your WAS.. i feel thats a better option ..  |
|
| Back to top |
|
|
| duffMan |
| Posted: Tue Oct 21, 2008 5:24 am Post subject: |
|
|
Voyager
Joined: 03 Jun 2002
Posts: 75
|
| zboy wrote: |
| ISOLATED will not help with heap |
I'm not sure about the ISOLATION parameter, but going to CLIENT mode sure does help with heap problems (read: we don't get them), it keeps the MQ memory outside the native heap....giving more addressable space to the jvm.
| zboy wrote: |
this is most often found in excutive and management circles
it is quite rare in technical staff, who usually like to think through the consequences of actions before they do them |
I agree with this, but when production is unstable and management is in your face you don't get the opportunity to think things through....all you can say is "the documentation indicates that this will work"... and hope for the best.
...anyway the WAS group abandoned BINDING mode and are now at CLIENT mode with appropriate qm.ini settings... |
|
| Back to top |
|
|
|
|
