Sun Microsystems 819468310 manual Windows and HP-UX Issues, Federation and Saml Issues

Known Issues and Limitations

JVM problems occur when running Access Manager on Application Server (6223676)

If you are running Application Server 8.1 on Red Hat Linux, the stack size of the threads created by the Red Hat OS for Application Server is 10 Mbytes, which can cause JVM resource problems when the number of Access Manager user sessions reaches 200.

Workaround: Set the Red Hat OS operating stack size to a lesser value such as 2048 or even 256 Kbytes, by executing the ulimit command before you start Application Server. Execute the ulimit command on the same console that you will use to start Application Server. For example:

# ulimit -s 256;

Windows and HP-UX Issues

■“Access Manager auto configuration failed when installing on zh_TW and es locales (6515043)” on page 30

■“HP-UX needs gettext binary with AM while installing JES full stack (6497926)” on page 30

Access Manager auto configuration failed when installing on zh_TW and es locales (6515043)

Workaround: In zh_TW and es locales on HP-UX platform, Access Manager has to be configured in "Config Later" mode only. Start the JavaES installer, install the Access Manager product and exit the JavaES installer. Then invoke the Access Manager configurator as shown below:

1.LANG=C

2.export LANG

3.Edit accessmanager-base/bin/amsamplesilent file

4.Run accessmanager-base/bin/amconfig -s amsamplesilent

HP-UX needs gettext binary with AM while installing JES full stack (6497926)

There is no current workaround for this problem.

Federation and SAML Issues

■“Federation fails when using Artifact profile (6324056)” on page 31

■“Logout error occurs in Federation (6291744)” on page 31

30 Sun Java System Access Manager 7.1 Release Notes • March 2007