• Home
• Platform
• Download
• Documentation
• Community
• Wiki
• Blog

From OpenLaszlo

The following changes are needed to configure IBM WebSphere to deploy OpenLaszlo. These have been tested with WebSphere 6.0 and OpenLaszlo 3.0.

Use the OpenLaszlo version of jdom.jar.

   WebSphere ships with an older version of jdom.jar than OpenLaszlo requires.
   OpenLaszlo has its own version of jdom.jar which provides the classes and
   methods that it needs.  You need to make this version available to the 
   OpenLaszlo server.

   Symptom: The following error occurs when starting Laszlo Explorer.
   Error 500: org.jdom.Element: method getChildTextNormalize(Ljava/lang/String;)
   Ljava/lang/String; not found.

   Solution: Rename the WebSphere version of jdom.jar so that OpenLaszlo
   uses its own version. For example, rename jdom.jar to jdom.jar.ibm.
   On Linux, you will find jdom.jar in the lib directory under your WebSphere
   root directory (/opt/IBM/WebSphere/AppServer by default).
   On Windows, the default WebSphere root directory is
   C:\Program Files\IBM\WebSphere\AppServer.

   After renaming jdom.jar, restart the WebSphere server.

Increase the Java Heap Size

   The OpenLaszlo server needs to run with higher JVM heap size parameters than
   the default WebSphere values.

   Symptom: WebSphere shuts down with an OutOfMemory error when running the
   OpenLaszlo server.

   Solution: Increase the default JVM heap size parameters.
   To configure the Java heap size parameters, go to the  administrative console
   page and click Servers>Application Servers>server_name>Java and Process Management> 
   Process Definition>Java Virtual Machine.  Set the following values. (The values are in megabytes.)
     Initial Heap Size - 128
     Maximum Heap Size - 512

   Save the configuration.
   Restart the WebSphere server.

JVM with JIT enabled in AIX

   In AIX installations, we found that JVM JIT is doing optimizations 
   in some openlaszlo classes and corrupting some methods.
   Tested in openlaszlo 3.0 and 3.02
   Symptom: Starting the application and making some requests, some errors appear like the following:
   Can´t find resource /img/logo.swf
   Can´t find resource /img/logo2.jpg
   Another way to test it is to enable debug mode in server (that seems to disable JIT).
   Solution: You have to tell JVM that skip JIT options for some classes.
   If you disable JIT completely, application will run a bit slower but safe.
   We found that disabling only JIT for those classes, it runs fine and fast.
   Put an export with the following line in startServer.sh and restart the server
   JITC_COMPILEOPT=SKIP{org/openlaszlo/compiler/SourceLocator}{*}{org/openlaszlo/iv/flash/util/FlashBuffer}{skipBits}
   You should use lzrecompile=true option in request, to force cache to rewrite.