| Author |
Message
|
| KSkelton |
 Posted: Wed Feb 05, 2003 1:01 pm Post subject: BIP1528E: java.lang.OutOfMemoryError |
 |
|
Apprentice
Joined: 28 Oct 2001
Posts: 45
|
Running WMQI 2.1 CSD2 on Win2000 with local broker.
MQ 5.2 CSD4.
DB2 7.1 fp3
2 CPUs with 2 GB RAM.
I am receiving the following error when attempting to perform a deploy complete on my entire broker.
I've run the mqsichangeconfigmgr -j many times to the same results.
Is there anything else I can tune to allow a large deploy? I heard somewhere about additional tuning parameters in 2.1 CSD2 which we are on.
BIP1528E: java.lang.OutOfMemoryError in Configuration Manager BrokerManager class run method.
A java.lang.OutOfMemoryError was caught by the Configuration Manager BrokerManager class run method. This means the Java Virtual Machine has exhausted its available memory heap.
Stop the Configuration Manager using the mqsistop command. Increase the maximum size of the Java Virtual Machine memory heap using the mqsichangeconfigmgr command, specifying the -j option. Refer to the WebSphere MQ Integrator Administration Guide for guidance. Then restart the Configuration Manager and retry the operation. Repeat if necessary until the error no longer occurs. |
|
| Back to top |
|
 |
| kirani |
| Posted: Wed Feb 05, 2003 9:24 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Welcome to the group 
How many EG's do you have on the Broker? Configuration manager has a limit of 2GB JVM HeapSize. To avoid this error try deploying your Message Flows/Message Sets in a smaller group. I'd recommend that you do a delta deploy of each EG's, try to avoid broker level deploys. Is it possible to install CSD4 on your box?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| KSkelton |
| Posted: Thu Feb 06, 2003 5:05 am Post subject: |
|
|
Apprentice
Joined: 28 Oct 2001
Posts: 45
|
Kiran,
We have five EGs running about 210 message flows with 210 message sets. I am successful deploying each EG individually. I have never had a problem peforming a deploy complete on Win2k before. However, the number of message flows are increasing so I fear I've reached some kind of limit.
2.1 CSD4 is possible, however due to the problems we had with bugs in CSD2 (we have a number of fixes on CSD2 installed) our developers are very resistant to CSD installs. (Glad we did not go with CSD3).
Why do you ask, does CSD4 offer us anything here? |
|
| Back to top |
|
|
| kirani |
| Posted: Sat Feb 15, 2003 12:58 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Sorry for the late reply, I was out for the conference.
There is no limit on the number of message flows you can deploy to the broker.
CSD4 fixed a bug related to the incorrect results in operations view after removing a message set from the broker. So if you are at lower CSD you will not know whether or not the message set is removed from the broker unless you do a complete deploy of the broker.
CSD4 should have all the e-fixes that you have installed on your machine after CSD2, unless the changes are specific to your organization. Before installing any CSD you must read readme.txt file very carefully and get to know the changes in that CSD.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| Vinayak.Satapute |
| Posted: Wed Mar 18, 2009 6:38 pm Post subject: |
|
|
Acolyte
Joined: 20 Dec 2006
Posts: 70
|
Hi,
I have the same issue of BIP1528E: java.lang.OutOfMemoryError in Configuration Manager BrokerManager class run method.
I have set the java memory heap size to 1024MB and I am running broker 6.1.0.2 version on AIX server.
This error is appearing once in every 2-3 days and I have my Broker Configuration Manager in running state during these days. Am I suppose to have my Broker configuration manager in stop mode? this was not the case some days ago.
kindly do advice.
Thanks,
Vinayak |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Mar 18, 2009 10:47 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
As the Configuration MGR in 6.1 is not remotely like that(under the hood) in V2.1 it is probably best to start a new thread here rather than ressurecting one from years ago. At least it tells us that you have done some searhing on the topic. 
That said, what you are seeing is a new one on me (since the major changes made to the CM in V5) and if I were you I would more than likely be looking at raising a PMR with IBM on the topic.
Stephen D
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| yuj |
| Posted: Mon Nov 30, 2009 11:15 am Post subject: |
|
|
Novice
Joined: 19 Mar 2007
Posts: 10
|
I'm in the exactly same situation. Have you got a perm fix of it?
| Vinayak.Satapute wrote: |
Hi,
I have the same issue of BIP1528E: java.lang.OutOfMemoryError in Configuration Manager BrokerManager class run method.
I have set the java memory heap size to 1024MB and I am running broker 6.1.0.2 version on AIX server.
This error is appearing once in every 2-3 days and I have my Broker Configuration Manager in running state during these days. Am I suppose to have my Broker configuration manager in stop mode? this was not the case some days ago.
kindly do advice.
Thanks,
Vinayak |
|
|
| Back to top |
|
|
| mqmatt |
| Posted: Tue Dec 01, 2009 2:49 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Some defects in this area were fixed in a later fixpack than the one you are using - particularly if there is a lot deployed to your brokers, or you using a lot of ESQL.
I'd recommend installing 6.1.0.5. Then, if the problem persists, raise a PMR. |
|
| Back to top |
|
|
|
|
