1) How big is your EAR?
2) What did you set the heap to?
3) Did you verify that the app server is using the new heap setting?
4) Have you monitored the heap usage?
I suspect that the admin console is uploading the EAR into memory before placing it on disk, so you might need twice as much heap space as the EAR file size.
Thanls for ur reply,
1. Ear is 35MB
2. I have set my heap to set JAVA_OPTS=%JAVA_OPTS% -Xms256m -Xmx256m
3. Yes, i confirmed from admin-console that is using the new heap setting.
4. yes the heap available was 57MB.
When i increased my heap to set JAVA_OPTS=%JAVA_OPTS% -Xms512m -Xmx512m it worked fine.
But now the problem is,
I have deployed my application through admin-console by adding a new resource it is deployed fine. As per my knowledge this ear should not serve any requests till i update it from the content tab. But this application serves all requests before updating. But i want this application to serve only after i start(update) the application after deploying.
Can you help me in this.
As per my knowledge this ear should not serve any requests till i update it from the content tab. But this application serves all requests before updating. But i want this application to serve only after i start(update) the application after deploying.
I don't know where you got this "knowledge" but it is incorrect. The admin console will not give you the control you are looking for unless you are using AS 7. In AS 6 and earlier, once an app is deployed it is immediately started (and thus available).
BTW, the default setting for max heap is 512MB, so reducing that down to 256MB would make the problem worse.
Thanku, Im currently deploying my applications in jboss4.2.0. How will be the migration effect.?
I'm sorry, but I do not understand your question...
Sorry for confusion. Currently im deploying my applications using JBoss4.2.0. But i want a feature to start an application after deploying which is available in JBossAS7. So if i want to migrate from jboss4.2.0 to JBoss AS7, how does it effect me.? Or can i use any trigger to jboss4.2.0 which my application doesnot start serving after deployment.?
I am not sure about the details, but in the samples for the JBoss deployment API, I see a deployment operation followed by a "start" operation.
Take a look e.g. at this wiki article: http://community.jboss.org/wiki/ProfileServiceDeploymentManagerIn5x
So, maybe this API is an alternative to the admin console?