Mar 22, 2013 3:38:23 PM org.apache.tomcat.util.net.JIoEndpoint$Acceptor runSEVERE: Socket accept failedjava.lang.ClassCircularityError: com/liferay/portal/security/pacl/PACLPolicyManager$PACLPolicyPrivilegedAction at com.liferay.portal.security.pacl.PACLPolicyManager.getPACLPolicy(PACLPolicyManager.java:70) at com.liferay.portal.security.pacl.PortalPolicy.getPermissions(PortalPolicy.java:133) at com.liferay.portal.security.pacl.PortalPolicy.implies(PortalPolicy.java:197) at java.security.ProtectionDomain.implies(ProtectionDomain.java:224) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:352) at java.security.AccessController.checkPermission(AccessController.java:549) at com.liferay.portal.security.pacl.PortalSecurityManagerImpl.checkPermission(PortalSecurityManagerImpl.java:205) at java.lang.SecurityManager.checkAccept(SecurityManager.java:1157) at java.net.ServerSocket.implAccept(ServerSocket.java:466) at java.net.ServerSocket.accept(ServerSocket.java:430) at org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(DefaultServerSocketFactory.java:60) at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:216) at java.lang.Thread.run(Thread.java:680)

> Wow! This is the first time I've seem an automatic message post in this> forum. :-)>>> To view the thread, follow the link below:>> http://www.liferay.com/community/forums/-/message_boards/view_message/22944127> --> Thanks, Liferay.com Forums <http://http://www.liferay.com>

First, I would like to thank you for your quick answers. Yes, I am using a master version (about 2 week old) because the M4 has a small annoying problem : it calls spring portlet controllers in 'edit' mode twice, in render as well as action phase. In master, everything is ok again.

Being away, I was not able to test further.

Ray Augé:

For anyone wanting try it out, follow these steps to auto generate the packpolicy for your plugin:

- add security-manager-enabled=generate to yourliferay-plugin-package.properties- deploy plugin- do usability testing of app (test all operations)- as you test, policy is auto generated into${lifers.home}/pacl-policy/${plugin-context-name}-pacl.policy- when completed testing, paste generated policy into app's own lpp.props

Now that I am back to work, I just activated the "generate" security mode with the last master, using a sample portlet with just the Spring requestContextFilter.

As a result, I just got : security-manager-environment-variables=\\*

Having tested this setting with true, everything seems ok. Anyway, the value "\*" seems strange to me, as a security setting.