6 Replies Latest reply on Dec 3, 2010 2:55 PM by vijaya chanumolu

    Regarding classpath

    vijaya chanumolu Newbie

      Do we need to modify the classpath envinornment variable when installing and configuring jboss.

      If so what are the jar files we need to add to it.

        • 1. Re: Regarding classpath
          Peter Johnson Master

          No, you should not set the CLASSPATH env var. JBoss AS will pick up all the JARs it needs automatically, and your app should include the additional JARs it needs.

           

          Oh, and welcome to the JBoss forums!

          • 2. Re: Regarding classpath
            vijaya chanumolu Newbie

            Thxs for the reply.Then in that case when I am starting jboss (run.bat) I found the following errors I dont know why?

             

             

            ObjectName: jboss.web.deployment:war=jmx-console.war,id=743670507

             

              State: FAILED

             

              Reason: org.jboss.deployment.DeploymentException: URL file:/C:/jboss/jboss-4.2

             

            .2.GA/server/default/deploy/jmx-console.war/ deployment failed

             

            --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---

            ObjectName: jboss.web.deployment:war=ROOT.war,id=2022917149

              State: FAILED

              Reason: org.jboss.deployment.DeploymentException: URL file:/C:/jboss/jboss-4.2

            .2.GA/server/default/deploy/jboss-web.deployer/ROOT.war/ deployment failed

             

            ObjectName: jboss:service=Hypersonic,database=localDB

              State: FAILED

              Reason: java.sql.SQLException: The database is already in use by another proce

            ss: org.hsqldb.persist.NIOLockFile@8a2161f0[file =C:\jboss\jboss-4.2.2.GA\server

            \default\data\hypersonic\localDB.lck, exists=true, locked=false, valid=false, fl

            =null]:

              Depends On Me:

                jboss.jca:service=ManagedConnectionFactory,name=DefaultDS

             

            ObjectName: jboss.web.deployment:war=jbossws-context.war,id=-2017997605

              State: FAILED

              Reason: org.jboss.deployment.DeploymentException: URL file:/C:/jboss/jboss-4.2

            .2.GA/server/default/deploy/jbossws.sar/jbossws-context.war/ deployment failed

             

            ObjectName: jboss:service=invoker,type=pooled

              State: FAILED

              Reason: java.lang.Exception: Port 4445 is already in use

              I Depend On:

                jboss:service=TransactionManager

             

            ObjectName: jboss.web.deployment:war=jbossmq-httpil.war,id=-1077341680

              State: FAILED

              Reason: org.jboss.deployment.DeploymentException: URL file:/C:/jboss/jboss-4.2

            .2.GA/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ deploymen

            t failed

             

            ObjectName: jboss:service=invoker,type=jrmp

              State: FAILED

              Reason: java.rmi.server.ExportException: Port already in use: 4444; nested exc

            eption is:

                    java.net.BindException: Address already in use: JVM_Bind

              I Depend On:

                jboss:service=TransactionManager

              Depends On Me:

                jboss:service=proxyFactory,target=ClientUserTransactionFactory

                jboss:service=proxyFactory,target=ClientUserTransaction

                jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory

             

            ObjectName: jboss.web.deployment:war=jmx-console.war,id=743670507

              State: FAILED

              Reason: org.jboss.deployment.DeploymentException: URL file:/C:/jboss/jboss-4.2

            .2.GA/server/default/deploy/jmx-console.war/ deployment failed

             

            ObjectName: jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3

             

              State: FAILED

              Reason: java.net.BindException: Address already in use: JVM_Bind

              I Depend On:

                jboss.aop:service=AspectDeployer

             

            ObjectName: jboss:service=Naming

              State: FAILED

              Reason: java.rmi.server.ExportException: Port already in use: 1098; nested exc

            eption is:

                    java.net.BindException: Address already in use: JVM_Bind

              I Depend On:

                jboss.system:service=ThreadPool

                jboss:service=NamingBeanImpl

              Depends On Me:

                jboss.mq:service=DestinationManager

                jboss.mq:service=Invoker

                jboss.mq:service=InvocationLayer,type=UIL

                jboss.mq:service=InvocationLayer,type=UILXA

                jboss.mq:service=InvocationLayer,type=UIL2,alias=UIL2ConnectionFactory

                jboss.mq:service=InvocationLayer,type=UIL2XA,alias=UIL2XAConnectionFactory

                jboss.jms:alias=QueueConnectionFactory

                jboss.jms:alias=TopicConnectionFactory

                jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory

                jboss.jmx:alias=jmx/rmi/RMIAdaptor

                jboss:service=Mail

             

            ObjectName: jboss:service=WebService

              State: FAILED

              Reason: java.lang.Exception: Port 8083 already in use.

              I Depend On:

                jboss.system:service=ThreadPool

              Depends On Me:

                jboss.ejb:service=EJBDeployer

             

            ObjectName: jboss.web.deployment:war=invoker.war,id=-1335363296

              State: FAILED

              Reason: org.jboss.deployment.DeploymentException: URL file:/C:/jboss/jboss-4.2

            .2.GA/server/default/deploy/http-invoker.sar/invoker.war/ deployment failed

             

            ObjectName: jboss.remoting:service=Connector,transport=socket

              State: FAILED

              Reason: java.net.BindException: Address already in use: JVM_Bind

              I Depend On:

                jboss.remoting:service=NetworkRegistry

              Depends On Me:

                jboss:service=invoker,type=unified

             

             

                    at org.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDepl

             

            oyer.java:1385)

             

                    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:785)

             

                    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)

             

                    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

             

                    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.

             

            java:39)

             

                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces

             

            sorImpl.java:25)

             

                    at java.lang.reflect.Method.invoke(Method.java:585)

             

                    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch

             

            er.java:155)

             

                    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)

             

                    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept

             

            or.java:133)

             

                    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)

             

                    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM

             

            BeanOperationInterceptor.java:142)

             

                    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)

             

                    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.

             

            java:264)

             

                    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)

             

                    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)

             

                    at $Proxy5.deploy(Unknown Source)

             

                    at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)

             

                    at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)

             

                    at org.jboss.Main.boot(Main.java:200)

             

                    at org.jboss.Main$1.run(Main.java:508)

             

                    at java.lang.Thread.run(Thread.java:595)

             

            15:31:36,734 ERROR [Http11Protocol] Error starting endpoint

             

            java.net.BindException: Address already in use: JVM_Bind:8090

             

                    at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:500)

             

                    at org.apache.tomcat.util.net.JIoEndpoint.start(JIoEndpoint.java:514)

             

                    at org.apache.coyote.http11.Http11Protocol.start(Http11Protocol.java:203

             

            )

             

                    at org.apache.catalina.connector.Connector.start(Connector.java:1146)

             

                    at org.jboss.web.tomcat.service.JBossWeb.startConnectors(JBossWeb.java:5

             

            84)

             

                    at org.jboss.web.tomcat.service.JBossWeb.handleNotification(JBossWeb.jav

             

            a:621)

             

                    at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)

             

                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces

             

            sorImpl.java:25)

             

                    at java.lang.reflect.Method.invoke(Method.java:585)

             

                    at org.jboss.mx.notification.NotificationListenerProxy.invoke(Notificati

             

            onListenerProxy.java:153)

             

                    at $Proxy38.handleNotification(Unknown Source)

             

                    at org.jboss.mx.util.JBossNotificationBroadcasterSupport.handleNotificat

             

            ion(JBossNotificationBroadcasterSupport.java:127)

             

                    at org.jboss.mx.util.JBossNotificationBroadcasterSupport.sendNotificatio

             

            n(JBossNotificationBroadcasterSupport.java:108)

             

                    at org.jboss.system.server.ServerImpl.sendNotification(ServerImpl.java:9

             

            16)

             

                    at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:497)

             

                    at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)

             

                    at org.jboss.Main.boot(Main.java:200)

             

                    at org.jboss.Main$1.run(Main.java:508)

             

                    at java.lang.Thread.run(Thread.java:595)

             

            15:31:36,734 WARN  [JBossWeb] Failed to startConnectors

             

            LifecycleException:  service.getName(): "jboss.web";  Protocol handler start fai

             

            led: java.net.BindException: Address already in use: JVM_Bind:8090

             

                    at org.apache.catalina.connector.Connector.start(Connector.java:1153)

             

                    at org.jboss.web.tomcat.service.JBossWeb.startConnectors(JBossWeb.java:5

             

            84)

             

                    at org.jboss.web.tomcat.service.JBossWeb.handleNotification(JBossWeb.jav

             

            a:621)

             

                    at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)

             

                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces

             

            sorImpl.java:25)

             

                    at java.lang.reflect.Method.invoke(Method.java:585)

             

                    at org.jboss.mx.notification.NotificationListenerProxy.invoke(Notificati

             

            onListenerProxy.java:153)

             

                    at $Proxy38.handleNotification(Unknown Source)

             

                    at org.jboss.mx.util.JBossNotificationBroadcasterSupport.handleNotificat

             

            ion(JBossNotificationBroadcasterSupport.java:127)

             

                    at org.jboss.mx.util.JBossNotificationBroadcasterSupport.sendNotificatio

             

            n(JBossNotificationBroadcasterSupport.java:108)

             

                    at org.jboss.system.server.ServerImpl.sendNotification(ServerImpl.java:9

             

            16)

             

                    at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:497)

             

                    at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)

             

                    at org.jboss.Main.boot(Main.java:200)

             

                    at org.jboss.Main$1.run(Main.java:508)

             

                    at java.lang.Thread.run(Thread.java:595)

             

            15:31:36,734 INFO  [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBos

             

            s_4_2_2_GA date=200710221139)] Started in 35s:344ms

            • 3. Re: Regarding classpath
              Peter Johnson Master

              Word of advice: it is usually better to say "I ran into this problem" and then describe the problem, rather than asking a general question. You will get help quicker, and from people who understand the issue.

               

              Anyway, it appears that you are running into port binding issues:

               

              15:31:36,734 WARN  [JBossWeb] Failed to startConnectorsLifecycleException:  service.getName(): "jboss.web";  Protocol handler start failed: java.net.BindException: Address already in use: JVM_Bind:8090

               

              (This is an assumption - I would really need to see the first error and exception stack trace in the console log to know for sure. What you posted is the deployment report which often does not identify the root cause of the issues.)

               

              See this to help resolve the port binding issues: https://community.jboss.org/wiki/DebugBindException

              • 4. Re: Regarding classpath
                Peter Johnson Master

                I also see this:

                 

                Reason: java.sql.SQLException: The database is already in use by another process: org.hsqldb.persist.NIOLockFile@8a2161f0[file =C:\jboss\jboss-4.2.2.GA\server\default\data\hypersonic\localDB.lck, exists=true, locked=false, valid=false, fl=null]:

                 

                which leads me to believe that you made some kind of configuration change regarding the database. Would you care to expalin exactly what you did and what changes you made?

                • 5. Re: Regarding classpath
                  Peter Johnson Master

                  Actually, another possibility on that database lock error is that you ran JBoss AS twice. That could also explain the port binding errors.

                  • 6. Re: Regarding classpath
                    vijaya chanumolu Newbie

                    Thxs for the advice.I follow as you said.

                    Regarding error I have checked whether another application is running on the same port .But it is not.I have installed jboss into newly formatted machine.

                    But I ran into the above errors.

                    And one more question is do we need to connect jboss to any database.As errors are showing that database is used by other process?

                     

                    Thxs,

                    vijaya