2 Replies Latest reply on Nov 27, 2006 4:10 PM by me bob

    Jboss 4.0.5GA Exception on startup

    me bob Newbie

      Hello,

      First off I want to apologize - I'm not sure that this belongs here but I'm not really sure what the problem at hand is...

      I've been using jboss for about 6 months now with some degrees of success. Recently I've wanted to try to use the jboss "all" configuration as a deployment platform for our application - primarily because I intend on using jboss aop 1.5 (which i have successfully got to work on my local machine).

      Upon trying to run the all configuration I get a number of deployment exceptions and messages that I and somewhat confused about. They seem to be related to snmp - perhaps some type of port conflict...

      I have tried this with jboss AS 4.0.4GA and jboss AS 4.0.5.GA

      The exceptions are as follows.


      2006-11-27 11:45:19,080 DEBUG [org.jboss.system.ServiceController] starting service jboss.jmx:name=SnmpAgent,service=snmp,type=adaptor
      2006-11-27 11:45:19,080 DEBUG [org.jboss.jmx.adaptor.snmp.agent.SnmpAgentService] Starting

      jboss.jmx:name=SnmpAgent,service=snmp,type=adaptor
      2006-11-27 11:45:19,082 DEBUG [org.jboss.jmx.adaptor.snmp.agent.SnmpAgentService] Instantiating trap emitter ...
      2006-11-27 11:45:19,088 DEBUG [org.jboss.jmx.adaptor.snmp.agent.SnmpAgentService] Starting trap emitter ...
      2006-11-27 11:45:19,089 DEBUG [org.jboss.jmx.adaptor.snmp.agent.TrapEmitter] Reading resource: '/managers.xml'
      2006-11-27 11:45:19,115 DEBUG [org.jboss.jmx.adaptor.snmp.agent.TrapEmitter] Found 1 monitoring managers
      2006-11-27 11:45:19,128 WARN [org.jboss.jmx.adaptor.snmp.agent.TrapEmitter] Error enabling monitoring manager: [address=localhost,

      port=1162, localAddress=null, loc
      alPort=0, version=1]
      java.net.BindException: Cannot assign requested address
      at java.net.PlainDatagramSocketImpl.bind0(Native Method)
      at java.net.PlainDatagramSocketImpl.bind(PlainDatagramSocketImpl.java:82)
      at java.net.DatagramSocket.bind(DatagramSocket.java:368)
      at java.net.DatagramSocket.<init>(DatagramSocket.java:210)
      at java.net.DatagramSocket.<init>(DatagramSocket.java:261)
      at org.opennms.protocols.snmp.SnmpPortal.<init>(SnmpPortal.java:295)
      at org.opennms.protocols.snmp.SnmpSession.<init>(SnmpSession.java:696)
      at org.opennms.protocols.snmp.SnmpSession.<init>(SnmpSession.java:667)
      at org.jboss.jmx.adaptor.snmp.agent.ManagerRecord.openSession(ManagerRecord.java:169)
      at org.jboss.jmx.adaptor.snmp.agent.TrapEmitter.load(TrapEmitter.java:284)
      at org.jboss.jmx.adaptor.snmp.agent.TrapEmitter.start(TrapEmitter.java:104)
      at org.jboss.jmx.adaptor.snmp.agent.SnmpAgentService.startService(SnmpAgentService.java:491)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
      at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:417)
      at org.jboss.system.ServiceController.start(ServiceController.java:435)
      at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
      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 $Proxy4.start(Unknown Source)
      at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)


      ##########################################################3



      2006-11-27 11:45:20,254 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=DefaultPartition
      2006-11-27 11:45:20,255 DEBUG [org.jboss.ha.framework.server.ClusterPartition] Starting jboss:service=DefaultPartition
      2006-11-27 11:45:20,257 DEBUG [org.jboss.ha.framework.server.ClusterPartition] Starting ClusterPartition: DefaultPartition
      2006-11-27 11:45:20,258 ERROR [org.jgroups.JChannel] exception: java.lang.Exception: exception caused by UDP.start():

      java.lang.Exception: UDP.createSockets(): canno
      t list on any port in range 0-1
      2006-11-27 11:45:20,259 DEBUG [org.jboss.ha.framework.server.ClusterPartition] Starting failed jboss:service=DefaultPartition
      ChannelException: java.lang.Exception: exception caused by UDP.start(): java.lang.Exception: UDP.createSockets(): cannot list on any

      port in range 0-1
      at org.jgroups.JChannel.connect(JChannel.java:328)
      at org.jboss.ha.framework.server.ClusterPartition.startService(ClusterPartition.java:336)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
      at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:417)
      at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
      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 $Proxy4.start(Unknown Source)
      at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)


      #################################################3


      2006-11-27 11:45:23,137 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:

      --- Packages waiting for a deployer ---
      org.jboss.deployment.DeploymentInfo@2cd21853 { url=file:/usr/local/jboss-4.0.5.GA/server/all/deploy/httpha-invoker.sar/invoker.war/ }
      deployer: null
      status: Starting
      state: INIT_WAITING_DEPLOYER
      watch: file:/usr/local/jboss-4.0.5.GA/server/all/deploy/httpha-invoker.sar/invoker.war/
      altDD: null
      lastDeployed: 1164653121397
      lastModified: 1161063702000
      mbeans:

      org.jboss.deployment.DeploymentInfo@fc45b69b { url=file:/usr/local/jboss-4.0.5.GA/server/all/deploy/jbossweb-tomcat55.sar/ROOT.war/ }
      deployer: null
      status: Starting
      state: INIT_WAITING_DEPLOYER
      watch: file:/usr/local/jboss-4.0.5.GA/server/all/deploy/jbossweb-tomcat55.sar/ROOT.war/
      altDD: null
      lastDeployed: 1164653121397
      lastModified: 1161648022000
      mbeans:

      org.jboss.deployment.DeploymentInfo@c150cd99 { url=file:/usr/local/jboss-4.0.5.GA/server/all/deploy/jbossws14.sar/jbossws-context.war }
      deployer: null
      status: Starting
      state: INIT_WAITING_DEPLOYER
      watch: file:/usr/local/jboss-4.0.5.GA/server/all/deploy/jbossws14.sar/jbossws-context.war
      altDD: null
      lastDeployed: 1164653121398
      lastModified: 1164653118000
      mbeans:

      org.jboss.deployment.DeploymentInfo@7490ad7 { url=file:/usr/local/jboss-4.0.5.GA/server/all/deploy/juddi-service.sar/juddiws.war/ }
      deployer: null
      status: Starting
      state: INIT_WAITING_DEPLOYER
      watch: file:/usr/local/jboss-4.0.5.GA/server/all/deploy/juddi-service.sar/juddiws.war/
      altDD: null
      lastDeployed: 1164653121398
      lastModified: 1161647998000
      mbeans:

      org.jboss.deployment.DeploymentInfo@23289e47 {

      url=file:/usr/local/jboss-4.0.5.GA/server/all/deploy/management/console-mgr.sar/web-console.war/ }
      deployer: null
      status: Starting
      state: INIT_WAITING_DEPLOYER
      watch: file:/usr/local/jboss-4.0.5.GA/server/all/deploy/management/console-mgr.sar/web-console.war/
      altDD: null
      lastDeployed: 1164653121399
      lastModified: 1161648010000
      mbeans:

      org.jboss.deployment.DeploymentInfo@fa4802df { url=file:/usr/local/jboss-4.0.5.GA/server/all/deploy/jmx-console.war/ }
      deployer: null
      status: null
      state: INIT_WAITING_DEPLOYER
      watch: file:/usr/local/jboss-4.0.5.GA/server/all/deploy/jmx-console.war/
      altDD: null
      lastDeployed: 1164653123091
      lastModified: 1161647996000
      mbeans:
      --- Incompletely deployed packages ---
      org.jboss.deployment.DeploymentInfo@fa4802df { url=file:/usr/local/jboss-4.0.5.GA/server/all/deploy/jmx-console.war/ }
      deployer: null
      status: null
      state: INIT_WAITING_DEPLOYER
      watch: file:/usr/local/jboss-4.0.5.GA/server/all/deploy/jmx-console.war/
      altDD: null
      lastDeployed: 1164653123091
      lastModified: 1161647996000
      mbeans:

      --- MBeans waiting for other MBeans ---
      ObjectName: jboss.web:service=WebServer
      State: CONFIGURED
      I Depend On:
      jboss.security:service=JaasSecurityManager
      jboss.cache:service=TomcatClusteringCache
      jboss:service=TransactionManager
      jboss.jca:service=CachedConnectionManager
      Depends On Me:
      jboss.ws:service=WebServiceDeployerJSE
      jboss:service=FarmMember,partition=DefaultPartition

      ObjectName: jboss.ws:service=WebServiceDeployerJSE
      State: CONFIGURED
      I Depend On:
      jboss.web:service=WebServer
      Depends On Me:
      jboss.ws:service=DeployerInterceptorNestedJSE

      ObjectName: jboss.ws:service=DeployerInterceptorNestedJSE
      State: CONFIGURED
      I Depend On:
      jboss.system:service=MainDeployer
      jboss.ws:service=WebServiceDeployerJSE

      ObjectName: jboss.cache:service=TomcatClusteringCache
      State: FAILED
      Reason: ChannelException: java.lang.Exception: exception caused by UDP.start(): java.lang.Exception: UDP.createSockets(): cannot list

      on any port in range 0-1
      I Depend On:
      jboss:service=Naming
      jboss:service=TransactionManager
      jboss.aop:service=AspectDeployer
      Depends On Me:
      jboss.web:service=WebServer

      ObjectName: jboss:service=DefaultPartition
      State: FAILED
      Reason: ChannelException: java.lang.Exception: exception caused by UDP.start(): java.lang.Exception: UDP.createSockets(): cannot list

      on any port in range 0-1
      I Depend On:
      jboss:service=Naming
      Depends On Me:
      jboss:service=HASessionState
      jboss:service=HAJNDI
      jboss.cache:service=InvalidationBridge,type=JavaGroups
      jboss.ha:service=HASingletonDeployer
      jboss:service=FarmMember,partition=DefaultPartition

      ObjectName: jboss.ha:service=HASingletonDeployer
      State: CONFIGURED
      I Depend On:
      jboss:service=DefaultPartition
      jboss.system:service=MainDeployer

      ObjectName: jboss:service=FarmMember,partition=DefaultPartition
      State: CONFIGURED
      I Depend On:
      jboss:service=DefaultPartition
      jboss.web:service=WebServer
      jboss.system:service=MainDeployer
      --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
      ObjectName: jboss.cache:service=TomcatClusteringCache
      State: FAILED
      Reason: ChannelException: java.lang.Exception: exception caused by UDP.start(): java.lang.Exception: UDP.createSockets(): cannot list

      on any port in range 0-1
      I Depend On:
      jboss:service=Naming
      jboss:service=TransactionManager
      jboss.aop:service=AspectDeployer
      Depends On Me:
      jboss.web:service=WebServer

      ObjectName: jboss:service=DefaultPartition
      State: FAILED
      Reason: ChannelException: java.lang.Exception: exception caused by UDP.start(): java.lang.Exception: UDP.createSockets(): cannot list

      on any port in range 0-1
      I Depend On:
      jboss:service=Naming
      Depends On Me:
      jboss:service=HASessionState
      jboss:service=HAJNDI
      jboss.cache:service=InvalidationBridge,type=JavaGroups
      jboss.ha:service=HASingletonDeployer
      jboss:service=FarmMember,partition=DefaultPartition


      This is just a vanilla jboss install - no customization. There are a few other services running on this machine such as 'flash media server 2' and mysql... nothing too serious. Any help would be much appreciated :)

        • 1. Re: Jboss 4.0.5GA Exception on startup
          Peter Johnson Master

          Are you using "all" only because you want to use AOP? I am using AOP with the "default" configuration (I simply ignore the Catalina-related instrumentation errors.)

          Regarding the error, looks like port 1162 is in use. You can use netstat (or tcpview from www.sysinternals.com if you are running Windows, you never said which OS) to find who is using that port and to stop that app.

          • 2. Re: Jboss 4.0.5GA Exception on startup
            me bob Newbie

            I'm using aop for jdk5 and I was having some issues using the default configuration. If the errors that occur when using aop for jdk5, in the default configuration are really harmless I could just use this (do you know the log4j config settings to ignore these?)

            Thats the conclusion that I came to aswell -that port 1162 was in use. I'm using CentOS linux. netstat -ap reports that its the jboss process that I am trying to use is the one that has the port open. So that is why I posted here - I guess I forgot those critical details. Oddly - i am also running jboss 4.0.5GA on my windows box and it does not give me these ugly errors.

            ~keith