During upgrade of Portal on a Windows system, Portal server launches but fails to initialize

Technote (troubleshooting)


Problem

When attempting to upgrade Portal on a Windows OS with either a fix/cumulative fix/fixpack, it may be required that Portal be stopped and started several times during the process. It is possible that the upgrade can fail if you are using the -Xlp flag to enable large pages for the JVM heap.

Symptom

Receive a build failed message which states that Portal Server failed to initialize. The configTrace.log shows the following exception: ADMU3011E: Server launched but failed initialization.

The SystemOut.log does not log anything relevant.


Cause

When tuning WebSphere Application Server and Portal, the -Xlp flag can be set on the JVM Heap. This will enable large pages which will reduce CPU overhead. Setting this flag in a Windows environment will cause Portal to not start reliably. This flag only applies to Unix systems.

Environment

Windows OSs

Diagnosing the problem

Reviewing the native_stderr.log we saw the following entry:

JVMJ9GC032E System configuration does not support option '-Xlp'
JVMJ9VM015W Initialization error for library j9gc24(2): Failed to initialize; unable to parse command line
Could not create the Java virtual machine.


Resolving the problem

To resolve this problem, the -Xlp flag will need to be removed from the WebSphere_Portal's server.xml file.

ie. genericJvmArguments="-Xlp -Xgcpolicy:gencon..."


Related information

WebSphere Portal and WCM 6.1.x Performance Tuning Guide


Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Portal

Software version:

6.1, 7.0

Operating system(s):

Windows

Reference #:

1500477

Modified date:

2011-05-24

Translate my page

Machine Translation

Content navigation