topic Re: Caused by: java.io.IOException: Not enough space (errno:12) in Alfresco Archive

Caused by: java.io.IOException: Not enough space (errno:12)

awanty — Wed, 23 Jan 2008 04:34:28 GMT

Hi, I am trying to deploy the alfresco.war in tomcat server in a HPUX 11.23IA environment with Java 1.5.0.11. When i start the tomcat server, its giving following error messsages,Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedConstructorAccessor61.newInstance

Re: Caused by: java.io.IOException: Not enough space (errno:12)

pmonks — Wed, 23 Jan 2008 05:47:17 GMT

Have you run out of disk space in any of the filesystems Alfresco is configured to use? If not, it may be a problem with the HPUX JDK or OS - a quick google turns up similar problems with other (non-Alfresco) applications on HPUX too.

As an FYI, we don't currently test or certify Alfresco against the HPUX JDK or OS - the current list of supported platforms is maintained at http://www.alfresco.com/services/support/stacks/. We're always keen to hear feedback on our supported stack of course - details on how to contact us are listed on that page.

Re: Caused by: java.io.IOException: Not enough space (errno:12)

awanty — Wed, 23 Jan 2008 06:00:17 GMT

Thanks for the response.
For other application its not giving these kind of errors. I think alfresco application needs lots memory, is there anywhere documented about the memory it needs? Currently in my machine 4Gb RAM is available.

As this is the platform independent product, so we are trying deploy in HPUX.
Regards.
Ambika

Re: Caused by: java.io.IOException: Not enough space (errno:12)

pmonks — Wed, 23 Jan 2008 06:24:40 GMT

The error has nothing to with the JVM heap size - that error (errno 12) is happening within an mmap operation, which, from further googling (eg. ftp://hprc.external.hp.com/memory.htm#examples), often indicates problems with swap space when seen on HPUX.

Regarding JVM heap, I personally run Alfresco with 512MB of heap and 128MB of PermGen on a 32bit Windows machine with 2GB of physical RAM, and haven't noticed any problems (provided I don't try to deploy other web applications to the same Tomcat instance - that can create JVM heap contention / starvation). That being said I'm not typically running Alfresco with a large amount of content, nor witnessing high traffic, so this is best considered a typical developer configuration.

As for being cross-platform, we definitely do our best to be platform agnostic, however the reality is that not all JVMs were created equal. We currently certify on the Sun JVM (v1.5), but are in the process of prioritising and testing with other JVMs. We have found bugs when Alfresco is run on other JVMs (some in our code, some in 3rd party code and some in the JVMs themselves) so at this point I would recommend sticking to a supported stack as much as possible. I realise that there's only a single JVM produced for HPUX - all the more reason to formally provide feedback via the supported stack page to let us know that you're using the HP JVM so that we can prioritise it appropriately.