You see an error saying "Cannot create thread" with the following stack trace:
"Access ManagerSessionPoller[9]" daemon prio=10 tid=0x0985e2e0 nid=0x37 in Object.wait() [0x10519000..0x10519a38] at java.lang.Object.wait(Native Method) - waiting on <0x2ad92c18> (a java.util.ArrayList) at java.lang.Object.wait(Object.java:474) at com.iplanet.Access Manager.util.ThreadPool.getTask (ThreadPool.java:125) - locked <0x2ad92c18> (a java.util.ArrayList) at com.iplanet.Access Manager.util.ThreadPool$ WorkerThread.run(ThreadPool.java:144)" |
The problem is due to an insufficient amount of JVM heap size, or invalid Access Manager session threads are created out of control. This behavior is expected and not a deadlock at all.
Solution: To increase the JVM heap size, you can change the domain.xml manually or simply run Access Manager amtune-as8.