Why does JBoss SOA-P fail to start cleanly when the Java security manager is enabled?
Issue
- Why does JBoss SOA-P fail to start cleanly when the Java security manager is enabled?
- I followed the EAP Security Guide for enabling the Java Security Manager, so that I could write some ESB actions that utilize policy permissions. However, upon starting the server I get lots of AccessControlException errors due to sufficient permissions not being set in the policy file to enable a clean start.
Environment
- JBoss SOA-P
- 5.1.0
- 5.2.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
