2 Replies Latest reply on Feb 25, 2005 1:06 PM by kenroberts

    /invoker/JNDIFactory in 4.0.1sp1

    kenroberts

      Hi folks.

      I was using jndi lookups over http in 3.0.6 and 3.2.5 by referencing http://localhost:8080/invoker/JNDIFactory as my proxy servlet.

      Suddenly, in 4.0.1sp1, I get the stack trace at the bottom of this message.

      This is a signed applet, can someone tell me what might have changed?

      Thanks.


      Stack trace:

      java.lang.ExceptionInInitializerError
      at org.jboss.naming.HttpNamingContextFactory.getNamingServer(HttpNamingContextFactory.java:106)
      at org.jboss.naming.HttpNamingContextFactory.getInitialContext(HttpNamingContextFactory.java:65)
      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 com.nineci.applet.HelloBeanApplet.start(HelloBeanApplet.java:31)
      at sun.applet.AppletPanel.run(AppletPanel.java:377)
      at java.lang.Thread.run(Thread.java:534)
      Caused by: java.security.AccessControlException: access denied (java.util.PropertyPermission org.jboss.security.httpInvoker.sslSocketFactoryBuilder read)
      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.SecurityManager.checkPropertyAccess(SecurityManager.java:1276)
      at java.lang.System.getProperty(System.java:573)
      at org.jboss.invocation.http.interfaces.Util.(Util.java:76)
      ... 9 more
      java.lang.IllegalArgumentException: null source
      at java.util.EventObject.(EventObject.java:34)
      at java.awt.AWTEvent.(AWTEvent.java:225)
      at java.awt.event.ComponentEvent.(ComponentEvent.java:94)
      at java.awt.event.WindowEvent.(WindowEvent.java:174)
      at java.awt.event.WindowEvent.(WindowEvent.java:211)
      at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:576)
      at java.awt.Component.dispatchEventImpl(Component.java:3506)
      at java.awt.Container.dispatchEventImpl(Container.java:1627)
      at java.awt.Window.dispatchEventImpl(Window.java:1606)
      at java.awt.Component.dispatchEvent(Component.java:3477)
      at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
      at java.awt.SequencedEvent.dispatch(SequencedEvent.java:93)
      at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
      at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
      at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
      at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
      at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
      at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

        • 1. Re: /invoker/JNDIFactory in 4.0.1sp1
          starksm64

          The applet does not have permission to read the org.jboss.security.httpInvoker.sslSocketFactoryBuilder system property used to configure a custom SSLSocketFactory. This check should be in a priviledged action and its failure should just be a warning message so its a bug.

          • 2. Re: /invoker/JNDIFactory in 4.0.1sp1
            kenroberts

            Thanks again, Scott.

            The big question here for me then is why is it trying an SSL socket? I'm using port 8080.

            I would also be interested in a means to fix this, when it's fixed.