Access Gateway error - Error occurred during initiatlization of VM

Products

• SITEMINDER

Issue/Introduction

When starting a previously working Access Gateway server, this error was seen:

Error occurred during initiatlization of VM
java/lang/NoClassDefFoundError: java/lang/Object
/opt/CA/secure-proxy/proxy-engine/logs/nohup.out  (END)

Cause

Maintenance had been performed on the server including using a script to clean up old Java instances.

The Java path used by the Access Gateway was not included in the script. The Java paths used by the Access Gateway all matched and had not changed.

The most common reasons for this error are:

- invalid paths/classpaths in the environment variables

- invalid Java version, either the release or bit level

- permissions on the Java path

- invalid Java install

Resolution

In this particular instance, the issue was the Java install. A backup of the original Java path was made and Java was redeployed again keeping the same path name. The Access Gateway was able to start successfully now.

Doing a directory comparison, it was found that the rt.jar was missing in the "bad" backup copy, which is why the redeployment worked.