topic Re: deploy alfresco in JBoss w/ 'All' configuration fa in Alfresco Archive

deploy alfresco in JBoss w/ 'All' configuration fa

hamptont — Wed, 29 Mar 2006 16:06:16 GMT

I have been able to deploy Alfresco into a JBoss 4.0.3 with JBoss Portal 2.2.0 but only into the default configuration. I tried deploying it into the all configuration and it fails.Steps that I followed are below. These instructions work for the default configuration but not the all configuration.

Re: deploy alfresco in JBoss w/ 'All' configuration fa

kevinr — Wed, 29 Mar 2006 16:28:11 GMT

Looks like a JBoss out-of-memory issue rather than an Alfresco issue. I think the "all" JBoss configuration loads a lot of JBoss services into memory. Your best bet is too change "run.sh" to give JBoss more memory e.g. 512MB or 1GB? So set the JAVA_OPTS variable to:
-Xmx512m

Does that help?

Thanks,

Kevin

Re: deploy alfresco in JBoss w/ 'All' configuration fa

hamptont — Wed, 29 Mar 2006 17:06:05 GMT

I'm running with 2GB of memory for my JVM. Here are the Java options that I'm running JBoss with.

JAVA_OPTS="-server -Xms2048m -Xmx2048m -d64"

I'm running on a 64-bit Solaris/Sparc platform with JDK 1.5.0_06

Still get the OutOfMemory problem. Alfresco never even comes up. I load the portal and click on the Alfresco Tab and about a minute or so later OutOfMemory.

I think Alfresco is conflicting with something in the all config.

Tom

Re: deploy alfresco in JBoss w/ 'All' configuration fa

kevinr — Wed, 29 Mar 2006 17:16:29 GMT

Well it's definitely not a memory issue then sounds like a decent machine.

I'm not sure what the problem is without giving it a try - we'll test it out on the "all" configuration and see what happens here.

Thanks for finding this,

Kevin

Re: deploy alfresco in JBoss w/ 'All' configuration fa

steve — Thu, 30 Mar 2006 14:10:02 GMT

Hello,

The settings you have are for heap size, and do not affect the Permanent Generation size - which is where you are getting your OutOfMemory errors.

The permanent generation is special because it holds meta-data describing user classes (classes that are not part of the Java language). Examples of such meta-data are objects describing classes and methods and they are stored in the Permanent Generation.

Applications with large code-base can quickly fill up this segment of the heap which will cause java.lang.OutOfMemoryError: PermGen no matter how high your -Xmx and how much memory you have on the machine.

To set a new initial size on Sun JVM use the -XXermSize=64m option when starting the virtual machine.
To set the maximum permanent generation size use -XX:MaxPermSize=128m option.

If you set the initial size and maximum size to equal values you may be able to avoid some full garbage collections that may occur if/when the permanent generation needs to be resized.
The default values differ from among different versions but for Sun JVMs upper limit is typically 64MB. And if you are running the 'All' Jboss configuration the default sounds like it is not enough.

Hope this helps,

Steve

Re: deploy alfresco in JBoss w/ 'All' configuration fa

hamptont — Thu, 30 Mar 2006 16:51:42 GMT

Steve,

Thank you for you help. Chaning the PermSize fixed the problem.

Tom