| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| 6.1 Configuration Manager running out of memory |
« View previous topic :: View next topic » |
| Author |
Message
|
| mattynorm |
 Posted: Fri Aug 01, 2008 1:13 am Post subject: 6.1 Configuration Manager running out of memory |
 |
|
Acolyte
Joined: 06 Jun 2003
Posts: 52
|
We are in the process of migrating from WBIMB v5 to WMB 6.1, and as such have the following set up on a Solaris server
1) Broker1 (WBIMBv5 CSD9), with a ConfigMgr on a Windows server
2) Broker2 (WMB v6.101)
3) ConfigMgr2 for Broker2
We now have approximately 120 flows, and 20 msgsets deployed to the new broker (as a flow is moved, the old v5 flow is stopped and the execution group reloaded).
We have started to get a stream of
| Quote: |
| (ConfigMgr2 )[17]BIP1528E: java.lang.OutOfMemoryError in Configuration Manager BrokerManager class run method. |
errors in the log, and the ConfigMgr process is using up to 80% of the cpu.
I have increased the Java Heap Size from 128mb to 1024mb, and the errors have gone away, but I am concerned that increasing it will have a knock on effect on other processes running on the server (this is a systest environment, and I'd like to nail this before migrating in UAT).
1) Is it correct to assume that as the ConfigMgr starts, it asks the Broker for state information, and due to the large number of flows\msgsets, the Broker is returning a message too big for the ConfigMgr to deal with?
2) Is there a way of calculating the Heap Size you need?
3) If you set the Heap siz to 1024mb, will the ConfigMgr hold onto all of this, or will it just use what it needs and return the rest for usage by other processes?
Thanks
Matt. |
|
| Back to top |
|
 |
| sami.stormrage |
| Posted: Fri Aug 01, 2008 12:00 pm Post subject: |
|
|
Disciple
Joined: 25 Jun 2008
Posts: 186
Location: Bangalore/Singapore
|
1) Is it correct to assume that as the ConfigMgr starts, it asks the Broker for state information, and due to the large number of flows\msgsets, the Broker is returning a message too big for the ConfigMgr to deal with?
Ans: Borker does not return any state information. It is the config manager with supplies the info if there are any changes.
2) Is there a way of calculating the Heap Size you need?
The only documentation I found was this:
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r0m0/topic/com.ibm.etools.mft.doc/ah14450_.htm
3) If you set the Heap siz to 1024mb, will the ConfigMgr hold onto all of this, or will it just use what it needs and return the rest for usage by other processes?
Think not, Thats why u allocate ur variables to Heap in C programming aswell.
_________________
*forgetting everything  * |
|
| Back to top |
|
|
| mqmatt |
| Posted: Mon Aug 04, 2008 5:05 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| sami.stormrage wrote: |
| Ans: Borker does not return any state information. It is the config manager with supplies the info if there are any changes. |
Yes it does in v6.1. In this version, the CM queries the broker for its flows etc. when it starts up. So this could well be the problem the OP is experiencing. |
|
| Back to top |
|
|
| JLRowe |
| Posted: Mon Aug 04, 2008 6:24 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
HI matt!
The main 2 memory related parameters are initial heap size and maximum heap size, if the value being set is maximum heap size - then the JVM will allocate upto that amount, but it will try and keep its memory consumption down by releasing memory when no longer needed.
Make sure there is enough swap space, the OS may still run out of memory when java grows the heap.
The high CPU is a result of the small heap, the JVM is spending all its time doing garbage collection to try and free up memory. |
|
| 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
|
|
|
|
