Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
[GLASSFISH-9166] error when running EJB client in ACC with security manager on Created: 19/Aug/09 Updated: 21/Sep/09 Resolved: 21/Sep/09 Status: Project: Component/s: Affects Version/s: Fix Version/s: Resolved glassfish standalone_client v2.1 Type: Reporter: Resolution: Labels: Remaining Estimate: Time Spent: Original Estimate: Environment: Bug Dies Koper Duplicate None Not Specified Issuezilla Id: 9,166 V3 Priority: Assignee: Votes: Major Tim Quinn 0 Not Specified Not Specified Operating System: All Platform: All Description When I run an EJB client in the ACC with the security manager enabled, I get an 'access denied' error message on GFv2.1: D:\GFv2.1\glassfish-v2.1-b60e\glassfish>bin\appclient -client ExitTestAppClientClient.jar 02/06/2009 10:44:00 AM com.sun.corba.ee.impl.util.Utility loadStub WARNING: "IOP01211405: (BAD_OPERATION) Exception in loadStub" org.omg.CORBA.BAD_OPERATION: vmcid: SUN minor code: 1405 completed: No at com.sun.corba.ee.impl.logging.UtilSystemException.exceptionInLoadStub(UtilSystemException.java:179) at com.sun.corba.ee.impl.logging.UtilSystemException.exceptionInLoadStub(UtilSystemException.java:197) at com.sun.corba.ee.impl.util.Utility.loadStub(Utility.java:856) [...] at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:407) at javax.naming.InitialContext.lookup(InitialContext.java:392) at ejb30.Client.main(Client.java:14) [...] Caused by: java.security.AccessControlException: access denied (com.sun.corba.ee.impl.presentation.rmi.DynamicAccessPermission access) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:323) at java.security.AccessController.checkPermission(AccessController.java:546) at java.lang.SecurityManager.checkPermission(SecurityManager.java:532) at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.<init>(StubInvocationHandlerImpl.java:105 at com.sun.corba.ee.impl.presentation.rmi.bcel.StubFactoryBCELImpl.makeStub(StubFactoryBCELImpl.java:171 at com.sun.corba.ee.impl.util.Utility.loadStub(Utility.java:852) When I add the following privileges to the grant block in glassfish/lib/appclient.policy, the client can successfully access the deployed EJB. permission com.sun.corba.ee.impl.presentation.rmi.DynamicAccessPermission "access"; permission java.lang.RuntimePermission "accessDeclaredMembers"; The client application was trying to do a JNDI lookup: Context gfic = new InitialContext(); ejb30.ExitTestRemote bean = (ejb30.ExitTestRemote)gfic.lookup("java:comp/env/ejb/ExitTestBean"); Shouldn't we have these privileges enabled in GlassFish by default? Comments Comment by kumara [ 01/Sep/09 ] Changing version from 9.1.1 to v2.1 to reflect new name/version. Comment by Tim Quinn [ 19/Sep/09 ] Adding Ken C. to the cc list and marking this as v3_exclude. Issue 9164 addresses this general issue (running a client with the security manager on) for v3. Comment by Tim Quinn [ 21/Sep/09 ] I am closing this as a dup of 9164. I know that there is a difference between this issue and 9164 - the version. This issue describes a problem for a specific priv that was added to the ORB in v2.1. (9164 refers to v3 which we are in the process of fixing) We have the other issue to track our progress on the v3 fix. Further progress on fixing this in v2.x will probably need to come via an escalation. o This issue has been marked as a duplicate of 9164 *** Comment by Tim Quinn [ 21/Sep/09 ] Forgot to remove the v3_exclude tag in my previous update. Generated at Wed May 10 19:16:07 UTC 2017 using JIRA 6.2.3#6260sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.