Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How can I debug the Java 2 security exceptions and AccessControlExceptions?

April 26, 2017debug exceptions Java security

0

10 Posted

How can I debug the Java 2 security exceptions and AccessControlExceptions?

1 Answer

0

10 Posted

There are two primary aids, the WebSphere SystemOut.log file and the com.ibm.websphere.java2secman.norethrow property.The AccessControlException logged in the SystemOut.log file contains the permission violation that causes the exception, the exception call stack, and the permissions granted to each stack frame. This information is usually enough to determine the missing permission and the code requiring the permission. When Java 2 security is enabled in WebSphere Application Server, the security manager component throws a java.security.AccessControl exception when a permission violation occurs. This exception, if not handled, often causes a run time failure. This exception is also logged in the SystemOut.log file. However, when the JVM com.ibm.websphere.java2secman.norethrow property is set and has a value of true, the security manager does not throw the AccessControl exception. This information is logged. To set the com.ibm.websphere.java2secman.norethrow property for the server, go