| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Bindings Mode Errors after MQ was upgraded from 5.2 to 5.3 |
« View previous topic :: View next topic » |
| Author |
Message
|
| mattbart |
 Posted: Tue May 18, 2004 8:09 am Post subject: Bindings Mode Errors after MQ was upgraded from 5.2 to 5.3 |
 |
|
Newbie
Joined: 18 May 2004
Posts: 2
Location: Burlington, VT
|
| The MQ version on the AIX machine I have java code running on was just upgraded from 5.3 to 5.3. My team has delt with this upgrade before. We usually has a few minor tweaks to do to work with 5.3. This includes building our java code against verion 1.3.1 and using the java 1.3.1 instilation on the server which I have done. I am able to connect in client mode, but when I try to connect with bindings mode I get a 2102 error. Normally, a client connection would be just fine, but for corporate review resons, this code must use bindings mode to connect. I see that the 2102 error code has something to do with insufficient recources, I'm wondering if 5.3 limits the number of bindings connections to a QMgr? Is there anything else that could be causing this problem? |
|
| Back to top |
|
 |
| mattbart |
| Posted: Tue May 18, 2004 9:26 am Post subject: Got It |
|
|
Newbie
Joined: 18 May 2004
Posts: 2
Location: Burlington, VT
|
Just as I posted this, our MQ support team sent me a note. He said to put this in my script:
export EXTSHM=ON
There seams to be a difference between the way 5.2 and 5.3 manages memory and this parameter setting is required to use Bindings mode. Thanks to anyone who read my topic. Maybe this will save others some time. |
|
| Back to top |
|
|
| mqonnet |
| Posted: Tue May 18, 2004 11:42 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
matt, real nice of you to share this info.
I am sure this info would surely save quite a significant amount of time for others.
Cheers
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue May 18, 2004 2:36 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Matt did it in fact solve your problem?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed May 19, 2004 5:03 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
There is definitely a difference in the way that MQ handles memory between 5.2 and 5.3. In 5.2, there was the constant conflict of java programs and segment 8. There was the temporary workaround of adding the IPCCBaseAddress (I think I have that right) to your ini file so that you could specify an address of segment 8.
With 5.3, the code was changed to take advantage of extended shared memory and the segment 8 problems went away. |
|
| 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
|
|
|
|
