LiveCycle ES Update 1 (8.2.1) is supported on 64-bit JDKs. 64-bit JDKs liberate us from the 1.2 GB maximum heap size limitation experienced on 32-bit JDKs on Windows. With all LiveCycle components deployed (including Content Services ES), LiveCycle's heap size requirements are now close to the limits afforded by 32-bit JDKs. However, the installation of the JBoss Turnkey will fail under a 64-bit JDK at the point where it tries to create a Windows service.
It is assumed that you are running on 64-bit CPU(s) and a 64-bit version of Windows. To confirm, download CPU-Z and run it. On an Intel CPU, the instruction sets supported will list EM64T, if the CPU is 64-bit. For an AMD CPU, it should say AMD64.
If you don't care whether JBoss is configured as a Windows service to start automatically on server re-start, you can easily bypass this step and continue. All you have to do are the following:
- Download and install the 64-bit version of Sun's HotSpot JDK from http://java.sun.com Please note the 6.0 (1.6) version of any JDK is not tested or supported by LiveCycle 8.2.1
- Configure the %JAVA_HOME% and %Path% system environment variables properly
- Run 'Group Policy Editor' (gpedit.msc)
- Assign the following user rights to the user that will be launching and running JBoss:
: Lock pages in Memory
- Start the Turnkey install and continue until it fails on the creation of the JBoss windows service
- Exit the LiveCycle Configuration Manager
- Edit JBoss' run.bat and add the following entries. These lines configure JBoss to start with a minimum and maximum heap size of 2 GB. This means that your system should have at least 4 GB of physical RAM installed. This also assumes a single dual-core CPU. If you've got a single quad-core CPU, change -XX:ParallelGCThreads from 2 to 4.
set JAVA_OPTS=%JAVA_OPTS% -server
set JAVA_OPTS=%JAVA_OPTS% -Dadobeidp.serverName=lc_server1
set JAVA_OPTS=%JAVA_OPTS% -Dfile.encoding=utf8
set JAVA_OPTS=%JAVA_OPTS% -Djava.net.preferIPv4Stack=true
set JAVA_OPTS=%JAVA_OPTS% -XX:PermSize=512m -XX:MaxPermSize=512m
set JAVA_OPTS=%JAVA_OPTS% -Xms2048m -Xmx2048m -XX:+UseLargePages
set JAVA_OPTS=%JAVA_OPTS% -Djboss.partition.name=partitionLIVECYCLE
set JAVA_OPTS=%JAVA_OPTS% -Djava.io.tmpdir=C:\Adobe\LiveCycle8.2\lc_java_io_tmpdir
set JAVA_OPTS=%JAVA_OPTS% -XX:+UseParallelOldGC -XX:ParallelGCThreads=2
set JAVA_OPTS=%JAVA_OPTS% -DCASBOOTPROPS=bam.properties
set JAVA_OPTS=%JAVA_OPTS% -Dcom.celequest.bootstrap.envpropname=CASBOOTPROPS
- From a command prompt, start JBoss with the command run -c all. If this fails with an error such as this:
"Error occurred during initialization of VM
Could not reserve enough space for object heap",
chances are that your memory is fragmented. Reboot the server and continue.
- Once JBoss is fully initialized, start LiveCycle Configuration Manager again
- Skip all steps until "Initialize Database'
- Continue from there
Please note that with this configuration, although MySQL will be configured as a Windows service to startup automatically on server re-start, JBoss has to be manually started every time. You have the option of configuring it as a 'scheduled task' to start on server re-start. For instructions, see here.
Here's a blog entry that describes how to get a 64-bit JBoss instance working on Linux.
Leave a comment