| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Out of memory error in execution group |
« View previous topic :: View next topic » |
| Author |
Message
|
| thiyan |
 Posted: Wed Jul 16, 2014 11:25 am Post subject: Out of memory error in execution group |
 |
|
Newbie
Joined: 10 Jul 2014
Posts: 4
|
I get this error in production. What is best solution to get rid of this!
BIP4367E: The method 'evaluate' in Java node 'Logging4.Log4jLoggingPlugin' has thrown the following exception: java.lang.OutOfMemoryError. : PNGIBRK2.5956b4e9-4101-0000-0080-e0cd89682cb4: /build/S700_P/src/DataFlowEngine/PluginInterface/com_ibm_broker_plugin_CMbService.cpp: 1845: ImbJavaExceptionUtils::throwableToNativeException: :
Jul 15 15:05:01 vmpb01 WebSphere Broker v7003[30316]: (PNGIBRK2.EXEGRP_EXT_SERVICES)[21]BIP4395E: Java exception: 'java.lang.OutOfMemoryError'; thrown from class name: 'java.lang.StringBuilder', method name: 'ensureCapacityImpl', file: 'StringBuilder.java', line: '339' : PNGIBRK2.5956b4e9-4101-0000-0080-e0cd89682cb4: /build/S700_P/src/DataFlowEngine/PluginInterface/com_ibm_broker_plugin_CMbService.cpp: 1863: ImbJavaExceptionUtils::throwableToNativeException:[/code] |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Jul 16, 2014 12:21 pm Post subject: Re: Out of memory error in execution group |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| thiyan wrote: |
| I get this error in production. What is best solution to get rid of this! |
Write less data out through log4j.
Get more memory.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| thiyan |
| Posted: Wed Jul 16, 2014 12:27 pm Post subject: Re: Out of memory error in execution group |
|
|
Newbie
Joined: 10 Jul 2014
Posts: 4
|
| Vitor wrote: |
| thiyan wrote: |
| I get this error in production. What is best solution to get rid of this! |
Write less data out through log4j.
Get more memory. |
Thanks for your reply. Ok we will plan to reduce log contents written using log4j, but if we still face this issue, is it advisable to increase min and max heap size?
Thanks in advance! |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 17, 2014 5:37 am Post subject: Re: Out of memory error in execution group |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| thiyan wrote: |
| Ok we will plan to reduce log contents written using log4j, but if we still face this issue, is it advisable to increase min and max heap size? |
That error isn't about the size of the log - it's complaining that one single log message is too large to be assembled in memory. I would suspect that, for one reason or another, you're "logging" the entire contents of a message tree and sometimes the messages are too big. log4j is really intended for the "String out of range" message.
Also log4j support doesn't come with WMB so you've either added the support pac or rolled your own solution. In the first case memory requirements are documented, in the latter ask the guy who wrote it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| thiyan |
| Posted: Thu Jul 17, 2014 9:44 pm Post subject: Re: Out of memory error in execution group |
|
|
Newbie
Joined: 10 Jul 2014
Posts: 4
|
| Vitor wrote: |
| thiyan wrote: |
| Ok we will plan to reduce log contents written using log4j, but if we still face this issue, is it advisable to increase min and max heap size? |
That error isn't about the size of the log - it's complaining that one single log message is too large to be assembled in memory. I would suspect that, for one reason or another, you're "logging" the entire contents of a message tree and sometimes the messages are too big. log4j is really intended for the "String out of range" message.
Also log4j support doesn't come with WMB so you've either added the support pac or rolled your own solution. In the first case memory requirements are documented, in the latter ask the guy who wrote it. |
Yes you are correct.... In one of our web service we are logging an method which is used to submit a file attachment of size 5 to 10mb and the complete byte array was being logged. We have removed the logs for attachments and now it seems to be working fine. |
|
| 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
|
|
|
|
