JNDI Security issue; Please help!!!

[sjkwadzo]

Hi,

We have a web application running on ServletExec application server. In
our code we're trying to get the home interface of an EJB deployed on a
pramati server. This used to worked fine. But for some unknown reason,
this is throwing now a Security exception. The weird this is it'll work
when the application runs in windows (we're using tomcat in windows to
debug). But will not work when deployed to unix. This is the complete
stack trace :

----------- Stack trace begins ------------
java.lang.ExceptionInInitializerError
at
com.pramati.naming.client.PramatiClientContextFactory.getInitialContext(PramatiClientContextFactory.java:223)
at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.(InitialContext.java:195)
at
org.grnds.facility.factory.GrndsJndiProducer.produce(GrndsJndiProducer.java:91)
at
com.msdw.refdata.o2.integration.savvion.O2SavvionEJBProducer.getEjbHome(O2SavvionEJBProducer.java:152)
at
com.msdw.refdata.o2.integration.savvion.O2SavvionEJBProducer.produce(O2SavvionEJBProducer.java:105)
at
com.msdw.refdata.o2.integration.savvion.O2SavvionEJBProducer.produce(O2SavvionEJBProducer.java:91)
at
org.grnds.facility.factory.GrndsFactory$ProducerContainer.produce(GrndsFactory.java:607)
at
org.grnds.facility.factory.GrndsFactory.produce(GrndsFactory.java:202)
at
org.grnds.facility.factory.GrndsFactory.produce(GrndsFactory.java:133)
at
com.msdw.refdata.o2.integration.savvion.O2SavvionAccessorBLManagerImpl.getWorkflowRequestStatus(O2SavvionAccessorBLManagerImpl.java:54)
at
com.msdw.refdata.o2.ui.createWorkflow.WorkflowRequestStatusAction.execute(WorkflowRequestStatusAction.java:113)
at
org.grnds.structural.ic.http.ActionHttpAdapterCore.perform(ActionHttpAdapterCore.java:332)
at
org.grnds.structural.ic.struts.IcStrutsAction.perform(IcStrutsAction.java:346)
at
org.grnds.structural.ic.struts.IcStrutsAction.execute(IcStrutsAction.java:310)
at
org.apache.struts.action.RequestProcessor.processActionPerform(Unknown
Source)
at org.apache.struts.action.RequestProcessor.process(Unknown Source)
at org.apache.struts.action.ActionServlet.process(Unknown Source)
at org.apache.struts.action.ActionServlet.doGet(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.newatlanta.servletexec.ServletExec.CallServletService(ServletExec.java:1717)
at
com.newatlanta.servletexec.SERequestDispatcher.forwardServlet(SERequestDispatcher.java:274)
at
com.newatlanta.servletexec.SERequestDispatcher.forward(SERequestDispatcher.java:191)
at
com.newatlanta.servletexec.SEFilterChain.doFilter(SEFilterChain.java:74)
at
com.msdw.refdata.o2.ui.auth.O2AuthFilter.doFilter(O2AuthFilter.java:166)
at
com.newatlanta.servletexec.SEFilterChain.doFilter(SEFilterChain.java:50)
at
com.newatlanta.servletexec.ApplicationInfo.filterApplRequest(ApplicationInfo.java:1454)
at
com.newatlanta.servletexec.ApplicationInfo.processApplRequest(ApplicationInfo.java:1299)
at
com.newatlanta.servletexec.ServerHostInfo.processApplRequest(ServerHostInfo.java:958)
at
com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:1267)
at
com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:1115)
at
com.newatlanta.servletexec.ServletExecService.processServletRequest(ServletExecService.java:165)
at
com.newatlanta.servletexec.ServletExecService.Run(ServletExecService.java:197)
at
com.newatlanta.servletexec.HttpServerRequest.run(HttpServerRequest.java:106)
Caused by: java.security.AccessControlException: access denied
(java.util.PropertyPermission jmx.serial.form write)
at
java.security.AccessControlContext.checkPermission(AccessControlContext.java:269)
at
java.security.AccessController.checkPermission(AccessController.java:401)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:524)
at java.lang.System.setProperty(System.java:654)
at
com.pramati.naming.client.PramatiClientContext.(PramatiClientContext.java:70)
.... 37 more

----------- Stack trace ends --------------
Any help will be greatly appreciated.

Thanks,

- Jonathan

 

[John C. Bollinger]

We have a web application running on ServletExec application server. In
our code we're trying to get the home interface of an EJB deployed on a
pramati server. This used to worked fine. But for some unknown reason,
this is throwing now a Security exception. The weird this is it'll work
when the application runs in windows (we're using tomcat in windows to
debug). But will not work when deployed to unix. This is the complete
stack trace :

----------- Stack trace begins ------------
java.lang.ExceptionInInitializerError
at
com.pramati.naming.client.PramatiClientContextFactory.getInitialContext(PramatiClientContextFactory.java:223)
at
[...]

Caused by: java.security.AccessControlException: access denied
(java.util.PropertyPermission jmx.serial.form write)
at
java.security.AccessControlContext.checkPermission(AccessControlContext.java:269)
at
java.security.AccessController.checkPermission(AccessController.java:401)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:524)
at java.lang.System.setProperty(System.java:654)
at
com.pramati.naming.client.PramatiClientContext.(PramatiClientContext.java:70)
... 37 more

----------- Stack trace ends --------------

The SecurityManager on your unix server is configured differently from
the one on your debug system. If ServletExec installs its own
SecurityManager then you'll have to consult its documentation. If it's
using the standard Java SecurityManager then you'll need to make
appropriate modifications to the SecurityManager's configuration file,
which might be $JAVA_HOME/jre/lib/security/java.policy. Consult your
Java docs for information on the config file.


John Bollinger
(e-mail address removed)

 

[John C. Bollinger]

Jonathan,

Note also that the PramatiClientContext seems to be attempting to set a
system property when it is denied access. This is a somewhat strange
thing for it to do, albeit not necessarily unreasonable. You may get
some help from Pramati tech support.


John Bollinger
(e-mail address removed)