Hi Jayan, thanks for the reply, but as I stated, this is not a java heap space problem. I have done all the necesary tests to confirm that, the XmX is set to 1280m which is the maximum for the 32-bit jdk and at the point of the crash there's still plety of java heap space avaible (the crash occurs after like a 3 minuts already in the early stage of the deployment phae). Also, when Livecycle does run out of heap space (which happened to us on some windows machines), you get a clear message java.lang.OutOfMemory : Out of heap space, which does not occur in our case.
So to clariy, the java heap space is here not the problem, the bug is the same as in sun's bug database (see links for details) and has to do with the mmap system call under linux.