2 Replies Latest reply on Jun 18, 2004 12:21 AM by kikuze

    Bunch of errors at startup

    kikuze

      Hi, I am trying JBoss for the 1st time on W2K. I've downloaded both version 4 and 3.2.4 but they have similar problems. This is what I see on the log when I call run.bat

      ===============================================================================
      .
      JBoss Bootstrap Environment
      .
      JBOSS_HOME: C:\jboss-4.0.0DR4\bin\\..
      .
      JAVA: C:\j2sdk1.4.2_04\bin\java
      .
      JAVA_OPTS: -Dprogram.name=run.bat -Xms128m -Xmx512m
      .
      CLASSPATH: C:\j2sdk1.4.2_04\lib\tools.jar;C:\jboss-4.0.0DR4\bin\\run.jar
      .
      ===============================================================================
      .
      16:39:45,727 INFO [Server] Starting JBoss (MX MicroKernel)...
      16:39:45,727 INFO [Server] Release ID: JBoss [Zion] 4.0.0DR4 (build: CVSTag=HEAD date=200405190212)
      16:39:45,737 INFO [Server] Home Dir: C:\jboss-4.0.0DR4
      16:39:45,737 INFO [Server] Home URL: file:/C:/jboss-4.0.0DR4/
      16:39:45,737 INFO [Server] Library URL: file:/C:/jboss-4.0.0DR4/lib/
      16:39:45,737 INFO [Server] Patch URL: null
      16:39:45,737 INFO [Server] Server Name: default
      16:39:45,747 INFO [Server] Server Home Dir: C:\jboss-4.0.0DR4\server\default
      16:39:45,747 INFO [Server] Server Home URL: file:/C:/jboss-4.0.0DR4/server/default/
      16:39:45,747 INFO [Server] Server Data Dir: C:\jboss-4.0.0DR4\server\default\data
      16:39:45,767 INFO [Server] Server Temp Dir: C:\jboss-4.0.0DR4\server\default\tmp
      16:39:45,767 INFO [Server] Server Config URL: file:/C:/jboss-4.0.0DR4/server/default/conf/
      16:39:45,767 INFO [Server] Server Library URL: file:/C:/jboss-4.0.0DR4/server/default/lib/
      16:39:45,767 INFO [Server] Root Deployment Filename: jboss-service.xml
      16:39:45,777 INFO [Server] Starting General Purpose Architecture (GPA)...
      16:39:46,949 INFO [ServerInfo] Java version: 1.4.2_04,Sun Microsystems Inc.
      16:39:46,959 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.2_04-b05,Sun Microsystems Inc.
      16:39:46,959 INFO [ServerInfo] OS-System: Windows 2000 5.0,x86
      16:39:47,891 INFO [Server] Core system initialized
      16:39:57,014 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
      16:39:58,005 INFO [WebService] Using RMI server codebase: http://joker:8083/
      16:39:58,235 INFO [NamingService] Started jnpPort=1099, rmiPort=1098, backlog=50, bindAddress=null, Client SocketFactory=
      null, Server SocketFactory=null
      16:39:58,265 WARN [NamingService] Context.PROVIDER_URL in server jndi.properties, url=file:///C:/jakarta-tomcat-5.0.25/we
      bapps/iccs/WEB-INF/classes
      16:40:01,400 WARN [NamingContext] Failed to connect to file:1099
      javax.naming.CommunicationException: Failed to connect to server file:1099 [Root exception is javax.naming.ServiceUnavaila
      bleException: Failed to connect to server file:1099 [Root exception is java.net.UnknownHostException: file: file]]
      at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:214)
      at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1182)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:513)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:506)
      at javax.naming.InitialContext.lookup(InitialContext.java:347)
      at org.jboss.invocation.jrmp.server.JRMPInvoker.rebind(JRMPInvoker.java:410)
      at org.jboss.invocation.jrmp.server.JRMPInvoker.startService(JRMPInvoker.java:307)
      at org.jboss.invocation.jrmp.server.JRMPInvoker$1.startService(JRMPInvoker.java:107)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
      at org.jboss.invocation.jrmp.server.JRMPInvoker.jbossInternalLifecycle(JRMPInvoker.java:576)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:232)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:643)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:844)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:369)
      at org.jboss.system.ServiceController.start(ServiceController.java:391)
      at org.jboss.system.ServiceController.start(ServiceController.java:391)
      at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:232)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:643)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:174)
      at $Proxy4.start(Unknown Source)
      at org.jboss.deployment.SARDeployer.start(SARDeployer.java:260)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:863)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:674)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:637)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:621)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:232)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:643)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:174)
      at $Proxy5.deploy(Unknown Source)
      at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:386)
      at org.jboss.system.server.ServerImpl.start(ServerImpl.java:291)
      at org.jboss.Main.boot(Main.java:150)
      at org.jboss.Main$1.run(Main.java:395)
      at java.lang.Thread.run(Thread.java:534)
      Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server file:1099 [Root exception is java.net.Unk
      nownHostException: file: file]
      at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:189)
      ... 55 more
      Caused by: java.net.UnknownHostException: file: file
      at java.net.InetAddress.getAllByName0(InetAddress.java:1011)
      at java.net.InetAddress.getAllByName0(InetAddress.java:981)
      at java.net.InetAddress.getAllByName(InetAddress.java:975)
      at java.net.InetAddress.getByName(InetAddress.java:889)
      at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:121)
      at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:185)
      ... 55 more


      The errors are very lengthy and it is throughout the whole startup log. I must have missed something in the configs but I can't seem to find any information about it. Can someone shed some light on this? Thanks!

      Russ

        • 1. Re: Bunch of errors at startup
          kikuze

          By the way these errors come up even though I did not do any setup at all.. all I did was just to unzip JBoss and execute the run.bat... so hope someone can tell me if there is anything i need to look out for prior to running the server.. thanks

          Russ

          • 2. Re: Bunch of errors at startup
            kikuze

            ok.. i find the cause of the errors.. it was due to a tomcat-configured jndi.properties placed in the lib folder of the sdk..