-
Bug
-
Resolution: Done
-
Major
-
2.0.5.Final
-
None
If we modify jboss-modules to remove the allPermissions by default, then change the WildflySecurityManager to avoid throwing exceptions, we get this error when starting Wildfly:
org.jboss.msc.service.StartException in service jboss.as: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.security.AccessControlException: access denied ("org.jboss.as.server.security.ServerPermission" "setCurrentServiceContainer") at java.security.AccessControlContext.checkPermission(AccessControlContext.java:472) at java.security.AccessController.checkPermission(AccessController.java:884) at org.jboss.as.server.CurrentServiceContainer.checkPermission(CurrentServiceContainer.java:63) at org.jboss.as.server.CurrentServiceContainer.setServiceContainer(CurrentServiceContainer.java:56) at org.jboss.as.server.ApplicationServerService.start(ApplicationServerService.java:137) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) ... 3 more
- blocks
-
JBEAP-2543 Incorreclty bypassing the SecurityManager and call AccessControl.checkPermission() directly
- Closed