| Author |
Message
|
| giorginus80 |
 Posted: Fri Feb 27, 2009 1:36 am Post subject: Managing big message (>100mb), possible? |
 |
|
Centurion
Joined: 08 Jul 2008
Posts: 124
Location: Rome, Italy
|
Hi,
I have very big message coming on my input node (may be Httpinput or MqInput) I have an OutOfMemory Error, I would like to know, If I create a file under /var/mqsi/registry/BROKER/CurrentVersion/MaxJVMHeapSize (I'm using linux and WMB 6.1.0.3) I solve the problem or anyway the broker can't manage message so large? My message is 150mb in other case larger too! |
|
| Back to top |
|
 |
| kimbert |
| Posted: Fri Feb 27, 2009 3:11 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
|
| Back to top |
|
|
| giorginus80 |
| Posted: Fri Feb 27, 2009 3:25 am Post subject: |
|
|
Centurion
Joined: 08 Jul 2008
Posts: 124
Location: Rome, Italy
|
I saw first, but I haven't a repeatable structure.
I have a normal XML with one field (base64binary) and this field it's larger than 100mb. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Feb 27, 2009 3:28 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You have a very badly designed XML document.
You should never edit anything under the broker registry yourself, and should only use documented methods for increasing Broker JVM heap sizes. |
|
| Back to top |
|
|
| giorginus80 |
| Posted: Fri Feb 27, 2009 5:12 am Post subject: |
|
|
Centurion
Joined: 08 Jul 2008
Posts: 124
Location: Rome, Italy
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Feb 27, 2009 5:55 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Notice that article is dated 2006 and ends with "This article has explained the role and function of the HTTP transport nodes in WebSphere Message Broker V6.0.0.1."
It's not current and does not show the best mechanism for increasing the Java Heap in Broker 6.1 |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Feb 27, 2009 8:12 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| mqjeff wrote: |
Notice that article is dated 2006 and ends with "This article has explained the role and function of the HTTP transport nodes in WebSphere Message Broker V6.0.0.1."
It's not current and does not show the best mechanism for increasing the Java Heap in Broker 6.1 |
Jeff, I saw the same article and we set this on our 6.1.0.3 Brokers.
| Code: |
| mqsiservice MyBroker -r maxJVMHeapSize=536870912 |
We have a PMR open on how to verify this setting after the fact. We'll ask if this is even a valid thing to do at 6.1.0.3. Do you have any info to the contrary?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| slonkoski |
| Posted: Fri Feb 27, 2009 8:20 am Post subject: IBM had us issue this |
|
|
Acolyte
Joined: 18 Mar 2005
Posts: 52
|
mqsireportproperties brokername -c AllTypes -o AllReportableEntityNames -r
Gives lots of good info but doesn't confirm the setting. Playing with various flags now and waiting for word back on the PMR |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Feb 27, 2009 8:21 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| PeterPotkay wrote: |
| mqjeff wrote: |
Notice that article is dated 2006 and ends with "This article has explained the role and function of the HTTP transport nodes in WebSphere Message Broker V6.0.0.1."
It's not current and does not show the best mechanism for increasing the Java Heap in Broker 6.1 |
Jeff, I saw the same article and we set this on our 6.1.0.3 Brokers.
| Code: |
| mqsiservice MyBroker -r maxJVMHeapSize=536870912 |
We have a PMR open on how to verify this setting after the fact. We'll ask if this is even a valid thing to do at 6.1.0.3. Do you have any info to the contrary? |
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/index.jsp?topic=/com.ibm.etools.mft.doc/an09143_.htm
 |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Feb 27, 2009 8:24 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| More pedantically, in 6.1, I've seen hints that the C++ Runtime now gets it's stack/heap from the JVM in the first place. I expect this to be fully the case in later releases of Broker. So in any large memory situation, I expect it to continue to be useful/necessary to tune the JVM heap size. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Feb 27, 2009 8:37 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| mqjeff wrote: |
| PeterPotkay wrote: |
| mqjeff wrote: |
Notice that article is dated 2006 and ends with "This article has explained the role and function of the HTTP transport nodes in WebSphere Message Broker V6.0.0.1."
It's not current and does not show the best mechanism for increasing the Java Heap in Broker 6.1 |
Jeff, I saw the same article and we set this on our 6.1.0.3 Brokers.
| Code: |
| mqsiservice MyBroker -r maxJVMHeapSize=536870912 |
We have a PMR open on how to verify this setting after the fact. We'll ask if this is even a valid thing to do at 6.1.0.3. Do you have any info to the contrary? |
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/index.jsp?topic=/com.ibm.etools.mft.doc/an09143_.htm
|
What's not clear is if that link refers to the JVM setting for the httpListener, or just for the EGs. We don't have lots of Jave Nodes, so don't really care about the EG's heap, but need to prepare for lots of connections to the httpListener, so want to increase its heap.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Feb 27, 2009 8:55 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| PeterPotkay wrote: |
| What's not clear is if that link refers to the JVM setting for the httpListener, or just for the EGs. We don't have lots of Jave Nodes, so don't really care about the EG's heap, but need to prepare for lots of connections to the httpListener, so want to increase its heap. |
It's clearly for the broker as a whole, and not specifically for the bipHTTPListener process (which is separate from the SOAPListener, remember!).
But a simple ps command should tell you if it applies to both the DFEs and the bipHTTPListener, if you set the min JVM Heap... |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Feb 27, 2009 11:39 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| I can be clear about one thing. The memory occupied by the elements in the message tree does not come from Java. It is taken from the system heap ( in a well-organised way which avoids heap fragmentation ). So the Java heap setting will have no effect on whether memory is available for tree-building. |
|
| Back to top |
|
|
| slonkoski |
| Posted: Mon Mar 23, 2009 4:25 am Post subject: |
|
|
Acolyte
Joined: 18 Mar 2005
Posts: 52
|
We discovered that to verify the JVM setting for the biphttplistener process:
ls -l /var/mqsi/registry/qmgr/CurrentVersion
and you'll see a file named maxJVMHeapSize
view the file to see the size |
|
| Back to top |
|
|
|
|
