3PAR Secure Service Policy Manager Release Notes

Secure Service Policy Manager Release Notes

Known Issues with Secure Service Policy Manager

Policy Manager may Appear Hung Following Startup

The 3PAR Secure Service Policy Manager, version 4.0.0.8 and earlier, contain the following

known issue.

Under certain circumstances the Secure Service Policy Manager may appear hung following

startup. In the wrapper, log file there will be a java exception trace indicating:

SEVERE: Exception processing Global JNDI Resources.

This error is typically caused by user defined groupnames in the Tomcat file realm which

contain XML reserved characters. The input panel in Tomcat erroneously allows the characters

to be used, and fails to properly escape them in the XML file.

Workaround - Perform the following steps:

1 Stop the

3PARSSPM service.

2 Edit the

Tomcat5/conf/tomcat-users.xml file and delete any lines that have

groupname's with '

&' or '<' characters.

3 Restart the 3PARSSPM service.

NOTE: These characters must be deleted and not simply edited. Administrator

privilege is needed to edit this file.