| Author |
Message
|
| V J |
 Posted: Thu May 30, 2013 1:17 pm Post subject: Deployment of large bar file |
 |
|
Novice
Joined: 30 May 2013
Posts: 11
|
Need to deploy a large bar file ~ 23MB size.
we are getting the bellow errors
Atleast i have not seen such an error in the past, Has anybody seen such an error, Any suggestions on getting around this issue.
Adding in some more addtional info.
This bar file contains a number of Jar Files, which are being created as libraries, and thats the reason we have such a large file.
This is a interim solution. In the future a WAS service will be stood up to use these jars.
When we break the barfile into parts and then try to deploy, we don't see any error |
|
| Back to top |
|
 |
| V J |
| Posted: Thu May 30, 2013 1:18 pm Post subject: Re: Deployment of large bar file |
|
|
Novice
Joined: 30 May 2013
Posts: 11
|
| V J wrote: |
Need to deploy a large bar file ~ 23MB size.
we are getting the bellow errors
BIP3702E: A Fatal Java exception was thrown whilst calling the Java JNI method ''AdminAgentThread_getDeployMessage''. The Java exception was ''java.lang.OutOfMemoryError: Java heap space''. The Java stack trace was ''Frame : 0 java.lang.OutOfMemoryError: Java heap space| @: java.lang.StringBuffer.ensureCapacityImpl(StringBuffer.java:338)| @: java.lang.StringBuffer.append(StringBuffer.java:204)| @: com.ibm.broker.config.common.XMLHelper.transformXML(XMLHelper.java:305)| @: com.ibm.broker.config.deploymgr.AdminAgentThread.getDeployMessage(AdminAgentThread.java:711)|''.
Atleast i have not seen such an error in the past, Has anybody seen such an error, Any suggestions on getting around this issue.
Adding in some more addtional info.
This bar file contains a number of Jar Files, which are being created as libraries, and thats the reason we have such a large file.
This is a interim solution. In the future a WAS service will be stood up to use these jars.
When we break the barfile into parts and then try to deploy, we don't see any error |
|
|
| Back to top |
|
|
| kash3338 |
| Posted: Thu May 30, 2013 8:54 pm Post subject: |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
| Can you try to place the JAR files in CLASSPATH (Shared Classes folder) than deploying in EG? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri May 31, 2013 3:13 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| kash3338 wrote: |
| Can you try to place the JAR files in CLASSPATH (Shared Classes folder) than deploying in EG? |
or a Java Classloader configurable service.... |
|
| Back to top |
|
|
| V J |
| Posted: Fri May 31, 2013 12:22 pm Post subject: |
|
|
Novice
Joined: 30 May 2013
Posts: 11
|
thanks for the reply mqjeff, kash3338.
Admin's do not want to use both these approaches. for there own reasons.
Is there a way we can increase the java heap size for deployment.
My guess is this heap size is different from the java heap size allocated to the execution group. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri May 31, 2013 9:16 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| V J wrote: |
Admin's do not want to use both these approaches. for there own reasons.
Is there a way we can increase the java heap size for deployment.
|
Possibly...
- They are two lazy
- This is something new and they don't understand it.
So they give the standard first answer of all Admins
No
{followed by}
Now what is the question?
Keep at them. If you have a legitimate business reason for deploying all the jars in one go then get the business to tell their admins to get off their backsides and sort it.
_________________
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 |
|
|
| lancelotlinc |
| Posted: Mon Jun 03, 2013 3:25 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| V J |
| Posted: Mon Jun 03, 2013 9:26 am Post subject: |
|
|
Novice
Joined: 30 May 2013
Posts: 11
|
Thanks lancelotlinc,
Admins, Dont have a problem as such with the approach, but they have challenges are around administration and including this as part of automated build and deployment process. As different teams are involved, this will take time. But this as an option is being considered.
Wanted to check, if there was a way we could allocate more resources to process doing the deployment. what i am almost sure now is, EG heap size is different from the heap used by the process doing the deployment.
Any pointers on this will be helpful.. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Jun 03, 2013 10:14 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| dogorsy |
| Posted: Sun Jun 09, 2013 12:30 am Post subject: Re: Deployment of large bar file |
|
|
Knight
Joined: 13 Mar 2013
Posts: 553
Location: Home Office
|
| V J wrote: |
| V J wrote: |
Need to deploy a large bar file ~ 23MB size.
we are getting the bellow errors
BIP3702E: A Fatal Java exception was thrown whilst calling the Java JNI method ''AdminAgentThread_getDeployMessage''. The Java exception was ''java.lang.OutOfMemoryError: Java heap space''. The Java stack trace was ''Frame : 0 java.lang.OutOfMemoryError: Java heap space| @: java.lang.StringBuffer.ensureCapacityImpl(StringBuffer.java:338)| @: java.lang.StringBuffer.append(StringBuffer.java:204)| @: com.ibm.broker.config.common.XMLHelper.transformXML(XMLHelper.java:305)| @: com.ibm.broker.config.deploymgr.AdminAgentThread.getDeployMessage(AdminAgentThread.java:711)|''.
Atleast i have not seen such an error in the past, Has anybody seen such an error, Any suggestions on getting around this issue.
Adding in some more addtional info.
This bar file contains a number of Jar Files, which are being created as libraries, and thats the reason we have such a large file.
This is a interim solution. In the future a WAS service will be stood up to use these jars.
When we break the barfile into parts and then try to deploy, we don't see any error |
|
change the MaxHeapSize value, use
mqsichangeproperties <brokername> -o ComIbmJVMManager -n jvmMaxHeapSize -v < newvalue > |
|
| Back to top |
|
|
| V J |
| Posted: Mon Jun 10, 2013 11:13 am Post subject: |
|
|
Novice
Joined: 30 May 2013
Posts: 11
|
would like to thank all of you for the support provided.
Deployment issue was resolved when we increased the memory for broker agent.
mqsichangeproperties brokerName -b agent -o ComIbmJVMManager -n jvmMaxHeapSize -v *** |
|
| Back to top |
|
|
| dosttumhara1810 |
| Posted: Thu Mar 27, 2014 4:00 am Post subject: |
|
|
Voyager
Joined: 01 Dec 2010
Posts: 76
|
hi,
Just wanted to knwo the heap size have given for the fix. I am facing the same issue, my bar file size is 5.6 MB |
|
| Back to top |
|
|
| Gralgrathor |
| Posted: Wed Mar 09, 2016 1:27 am Post subject: |
|
|
Master
Joined: 23 Jul 2009
Posts: 297
|
Out of curiosity: how do you get your BAR files that big? Even with resources inlined and sources included, the files are mostly text, which is compressed when included into the BAR, and I've never managed to get my BARs to grow beyond 1M. What kind of resources are you including in your BAR?
_________________
A measure of wheat for a penny, and three measures of barley for a penny; and see thou hurt not the oil and the wine. |
|
| Back to top |
|
|
| stoney |
| Posted: Wed Mar 09, 2016 2:11 am Post subject: |
|
|
Centurion
Joined: 03 Apr 2013
Posts: 140
|
| Quote: |
| something about reopening old threads |
The answer will almost certainly be JAR files.
For example, log4j-api and log4j-core are about 1.2MB by themselves.
Start adding in things like ehcache, multiple apache-commons libraries, and the size soon shoots up. |
|
| Back to top |
|
|
|
|
