[WebSphere] The startup script hangs when the system has multiple CPUs

The startup script hangs when the system has multiple CPUs

Problem(Abstract)

If you install IBM® WebSphere® Application Server on a Linux® operating system, the product might not start properly. This situation occurs when the the system boot loader is configured with the maxcpus property set to one and then you change the value of this property to a value that is greater than one. When you issue the startServer.sh command, the startup process hangs indefinitely.

Symptom

The startServer.sh script hangs on a multi-core system.

Cause

The single core Ahead-of-Time (AOT) compiler output is cached in the class cache.

Diagnosing the problem

To reproduce the symptom, complete these steps:

1. On a multi-core Linux operating system, change the setting for the maxcpus property for the grub bootloader, which is located in the SLES /boot/grub/menu.lst directory, to 1.
2. Reboot the operating system.
3. Install the product, create a profile, and then start the server. The start and stop functionality works as expected.
4. Change the setting for the maxcpus property to a value that is greater than one.
5. Reboot the Linux operating system.
6. Issue the Start.sh command to start the product. The startup process hangs indefinitely.

Resolving the problem

Clear the class cache, and run startServer.sh script again. For example, if the product is installed in the /opt/IBM/WebSphere/AppServer directory, issue the following command to clear the cache:

/opt/IBM/WebSphere/AppServer/bin/clearClassCache.sh

This command removes the single core specific code from the cache. After this command completes, reissue the startServer.sh command