| Author |
Message
|
| jbanoop |
 Posted: Mon Oct 11, 2010 9:35 am Post subject: Deployment - java.lang.OutOfMemoryError - WMB 7.0.0.1 |
 |
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
All,
Version:
WMB 7.0.0.1 on AIX
We are getting failed deployments on our Execution group.
The errors are:
| Code: |
Oct 11 14:30:05 BIP4395E: Java exception: 'java.lang.OutOfMemoryError'; thrown from class name: 'com.ibm.broker.flowgroupfiles.MbDirectory', method name: 'getCanonicalMbDirectory', file: 'MbDirectory.java', line: '301' : QWMB02.4d637b2f-2b01-0000-0080-de3d8bf07625: /build/S700_P/src/DataFlowEngine/PluginInterface/com_ibm_broker_plugin_CMbService.cpp: 1863: ImbJavaExceptionUtils::throwableToNativeException: :
$ 9065]BIP4395E: Java exception: 'java.lang.OutOfMemoryError'; thrown from class name: 'com.ibm.broker.flowgroupfiles.MbDirectory', method name: 'getCanonicalMbDirectory', file: 'MbDirectory.java', line: '301' : QWMB02.4d637b
BIP4395E: Java exception: 'com.ibm.broker.schemadeploy.MbXSDInternalError'; thrown from class name: 'com.ibm.broker.schemadeploy.MbXSDDeployDirector', method name: 'compileMessageSetSchemas', file: 'MbXSDDeployDirector.java', line: '505' : QWMB02.4d637b2f-2b01-0000-0080-de3d8bf07625: /build/S700_P/src/DataFlowEngine/PluginInterface/com_ibm_broker_plugin_CMbService.cpp: 1863: ImbJavaExceptionUtils::throwableToNativeException: :
|
however we suspect that this was because of previous out of memory exceptions that occured on the execution group.
When the same deploy was performed on a fresh execution group, it was successful.
There are only about 20 message flows deployed to this EG of which only 3-4 are started.
There are 2 SAP inadapter, 2 SAP outadapters and 1 file input node also deployed to this EG.
I understand that we can hike up the JVM memory on the EG but I wanted to know if you think this is this normal behavior or something we need to debug further on. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Oct 11, 2010 12:41 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
How big are the message sets, in particular the xsdzip files?
What's the disk utilization on the broker workpath look like? |
|
| Back to top |
|
|
| jbanoop |
| Posted: Wed Oct 13, 2010 7:56 am Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
Jeff and all,
we have around 10 xsdzips deployed each approximately around 60KB.
These are mostly the message sets created from the SAP system using ESD.
disk utilization on the workpath looks OK.
The min and max JVM Heap Size are set to defaults (32MB and 256MB respectively).
The exact inventory on the EG in question is:
Message Flows - 21 (9 flows started out of which 3 have SAP adapters)
SAP Adapters - 8 (3 inadapters, 5 outadapters)
.Dictionary - 8
xspzips - 10
jar files - 3 (one jar file is 950 KB) |
|
| Back to top |
|
|
| tomasz.bandura |
| Posted: Tue Feb 01, 2011 3:37 am Post subject: |
|
|
Newbie
Joined: 01 Feb 2011
Posts: 2
|
Hi all,
Did you solve your OutOfMemory problem?
I have similiar configuration and the same problem.
The difference are:
- i use 2 SAP Adapters (In and Out)
- but my MessageSet consists of about 300 xsdzips ( ~2MB)
What is strange, project deployed on Windows environment works well (MB has default configuration).
regards
Tomasz |
|
| Back to top |
|
|
| jbanoop |
| Posted: Wed Feb 23, 2011 1:55 pm Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
Can anyone shed any light on what the broker actually does with the XSDZips at runtime ?
All I could gather was that it unzips the "zip" and writes out the XSDs n WSDLs (if any) to the broker file system but nothing substantial on why it should cause such an error.
I will anyways go ahead and raise a PMR for the error but an understanding of what the broker runtime actually does would be really good to know.. |
|
| Back to top |
|
|
| mqwlk |
| Posted: Wed May 04, 2011 6:27 am Post subject: |
|
|
Newbie
Joined: 04 May 2011
Posts: 2
|
IC73289: SAP MESSAGE-SETS DO NOT FREE MEMORY ON UN DEPLOY
An out of memory (OOM) condition is seen when deploying a bar
file that contains a SAP node. The problem actually occurs with
a redeploy of this bar file after it has already been deployed
once. If the maxJVMHeapSize is set to the size required for a
deploy and then doubled in size, the redeploy works. The errors
seen are BIP4395E (Java exception) BIP5024E BIP4041E BIP2087E.
This error could also be seen when deploying other adapter
nodes and their associated message sets. |
|
| Back to top |
|
|
|
|
