3 Replies Latest reply on Aug 18, 2003 5:24 AM by Juha Lindfors

    JBOSS3.2.1 start-up problem - security.properties

    bbbear Newbie

      Hi,

      I wasn't sure if anyone of u have encounter this exception before? It says cannot find this file C:\JBOSS3\bin\config\security.properties. What is this security.properties used for? I don't even see this config folder exist in my bin folder! Below is part of the start-up information. If anyone knows how to get around with this, please enlighten!! Thanks.

      p/s: I'm using JDK 1.4.1_04

      Regards,
      bb

      ----------------------------------------------------------------

      16:00:35,786 INFO [NamingService] Starting
      16:00:35,806 INFO [NamingService] Starting jnp server
      16:00:35,996 INFO [NamingService] Started jnpPort=1099, rmiPort=0, backlog=50, bindAddress=null, Client SocketFactory=null, Server SocketFactory=null
      16:00:36,417 ERROR [STDERR] java.io.FileNotFoundException: C:\JBOSS3\bin\config\security.properties (The system cannot find the path specified)
      16:00:36,437 ERROR [STDERR] at java.io.FileInputStream.open(Native Method)
      16:00:36,447 ERROR [STDERR] at java.io.FileInputStream.(FileInputStream.java:103)
      16:00:36,447 ERROR [STDERR] at com.sun.enterprise.util.Utility.getPropertiesFromFile(Utility.java:56)
      16:00:36,457 ERROR [STDERR] at com.sun.enterprise.iiop.POAEJBORB.(POAEJBORB.java:83)
      16:00:36,457 ERROR [STDERR] at java.lang.Class.forName0(Native Method)
      16:00:36,467 ERROR [STDERR] at java.lang.Class.forName(Class.java:217)
      16:00:36,467 ERROR [STDERR] at org.omg.CORBA.ORB.create_impl(ORB.java:295)
      16:00:36,477 ERROR [STDERR] at org.omg.CORBA.ORB.init(ORB.java:336)
      16:00:36,477 ERROR [STDERR] at com.sun.enterprise.util.ORBManager.createORB(ORBManager.java:140)
      16:00:36,487 ERROR [STDERR] at com.sun.enterprise.util.ORBManager.init(ORBManager.java:69)
      16:00:36,487 ERROR [STDERR] at com.sun.enterprise.naming.SerialInitContextFactory.(SerialInitContextFactory.java:35)
      16:00:36,497 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
      16:00:36,497 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
      16:00:36,507 ERROR [STDERR] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
      16:00:36,507 ERROR [STDERR] at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
      16:00:36,517 ERROR [STDERR] at java.lang.Class.newInstance0(Class.java:306)
      16:00:36,517 ERROR [STDERR] at java.lang.Class.newInstance(Class.java:259)
      16:00:36,527 ERROR [STDERR] at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:649)
      16:00:36,527 ERROR [STDERR] at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
      16:00:36,537 ERROR [STDERR] at javax.naming.InitialContext.init(InitialContext.java:219)
      16:00:36,537 ERROR [STDERR] at javax.naming.InitialContext.(InitialContext.java:175)
      16:00:36,557 ERROR [STDERR] at org.jboss.naming.NamingService.startService(NamingService.java:160)
      16:00:36,567 ERROR [STDERR] at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
      16:00:36,577 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      16:00:36,577 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      16:00:36,587 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      16:00:36,587 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:324)
      16:00:36,597 ERROR [STDERR] at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      16:00:36,607 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
      16:00:36,607 ERROR [STDERR] at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:966)
      16:00:36,617 ERROR [STDERR] at $Proxy0.start(Unknown Source)
      16:00:36,617 ERROR [STDERR] at org.jboss.system.ServiceController.start(ServiceController.java:392)
      16:00:36,627 ERROR [STDERR] at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
      16:00:36,627 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      16:00:36,637 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:324)
      16:00:36,637 ERROR [STDERR] at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      16:00:36,647 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
      16:00:36,657 ERROR [STDERR] at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      16:00:36,657 ERROR [STDERR] at $Proxy5.start(Unknown Source)
      16:00:36,667 ERROR [STDERR] at org.jboss.deployment.SARDeployer.start(SARDeployer.java:226)
      16:00:36,667 ERROR [STDERR] at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
      16:00:36,677 ERROR [STDERR] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640)
      16:00:36,677 ERROR [STDERR] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:613)
      16:00:36,687 ERROR [STDERR] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:597)
      16:00:36,687 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      16:00:36,697 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      16:00:36,707 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      16:00:36,707 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:324)
      16:00:36,717 ERROR [STDERR] at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      16:00:36,727 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
      16:00:36,727 ERROR [STDERR] at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      16:00:36,737 ERROR [STDERR] at $Proxy6.deploy(Unknown Source)
      16:00:36,737 ERROR [STDERR] at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:365)
      16:00:36,747 ERROR [STDERR] at org.jboss.system.server.ServerImpl.start(ServerImpl.java:272)
      16:00:36,747 ERROR [STDERR] at org.jboss.Main.boot(Main.java:150)
      16:00:36,757 ERROR [STDERR] at org.jboss.Main$1.run(Main.java:388)
      16:00:36,757 ERROR [STDERR] at java.lang.Thread.run(Thread.java:536)

        • 1. Re: JBOSS3.2.1 start-up problem - security.properties
          Juha Lindfors Master

          You have a conflicting jndi.properties somewhere in your classpath from J2EE RI implementation that is trying to use Sun's Corba naming implementation rather than JBoss JNP naming implementation.

          You need to make sure to get rid of the incorrect naming service configuration.

          • 2. Re: JBOSS3.2.1 start-up problem - security.properties
            bbbear Newbie

            Hi, thank you for the reply.

            Actually previously I was having JVM_Bind problem, shown below:

            13:18:28,713 INFO [NamingService] Starting
            13:18:28,723 INFO [NamingService] Starting jnp server
            13:18:28,914 ERROR [NamingService] Could not start on port 1099
            java.net.BindException: Address already in use: JVM_Bind

            So, I thought to change the port number then. However, after I've changed the port number, I get java.io.FileNotFoundException instead. Shown below:

            13:13:38,025 INFO [NamingService] Starting
            13:13:38,035 INFO [NamingService] Starting jnp server
            13:13:38,656 INFO [NamingService] Started jnpPort=1089, rmiPort=0, backlog=50, bindAddress=null, Client SocketFactory=null, Server SocketFactory=null
            13:13:39,307 ERROR [STDERR] java.io.FileNotFoundException: C:\JBOSS3\bin\config\security.properties (The system cannot find the path specified)

            I've checked the server domain, it contains only 1 jndi.properties file. I've looked through the jboss-service.xml, there's no changes on the NamingService conf at all. I've checked the CLASSPATH, it only has those .jar that's necessary for JBoss start-up, nothing else.

            Seriously, I really have no clue why the Sun's Corba implementation will be requested instead of the JBoss JNP naming implementation. Where have I gone wrong? Is there any other xml I need to keep an eye on??

            Really need some advises out there, thanks!!

            Regards,
            bb

            • 3. Re: JBOSS3.2.1 start-up problem - security.properties
              Juha Lindfors Master

              Bind exception on port 1099 says that you probably have rmi registry (or naming) already running as part of another process.

              Look for conflicting jndi.properties or uninstall Sun's J2EE server from your machine.

              -- Juha