0 Replies Latest reply on Jan 16, 2008 4:46 PM by Joe Nibert

    Cold Deploy of War hangs JBoss. (JBoss Life Thread not creat

    Joe Nibert Newbie

      Issue: JBOSS 4.2.2 on Windows XP using JDK 1.5. We have a war file which we have a listener to populate data when the war is deployed. This war file works if JBoss is up and running and the war is Hot Deployed. When we shutdown JBoss and leave our war file in the deploy directory and startup JBoss, JBoss fails to start and just hangs. Things we have noticed. Some threads do not get created when doing “Cold� deploy mechanism (having the war file in the deploy directory, before starting JBoss). Listed below is what we see when we start JBoss without the war files in the deploy directory, and the second set is when the war file is in the war directory.

      In the cold deploy JBoss Life Thread is not created...Not sure if this means anything.

      Thanks,

      SUCCESSFUL STARTUP ------------------------------------------------

      Partial end list of the threads that are run when JBoss successfully starts.

      ...
      Thread [UILServerILService Accept Thread] (Running)
      Thread [JBossLifeThread] (Running)
      Thread [Thread-6] (Running)
      Daemon Thread [http-127.0.0.1-8080-Acceptor-0] (Running)
      Daemon Thread [ajp-127.0.0.1-8009-Acceptor-0] (Running)


      This partial output from console is when Jboss actually starts .

      ...
      [UILServerILService] JBossMQ UIL service available at : /127.0.0.1:8093
      15:57:47,411 INFO [DLQ] Bound to JNDI name: queue/DLQ
      15:57:47,676 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
      15:57:47,723 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
      15:57:48,301 INFO [DefaultEndpointRegistry] register: jboss.ws:context=ssdi-ssdr,endpoint=ssdi-ssdr
      15:57:48,426 INFO [TomcatDeployer] deploy, ctxPath=/ssdi-ssdr, warUrl=.../tmp/deploy/tmp2628ssdi-ssdr-exp.war/
      15:57:52,160 INFO [WSDLFilePublisher] WSDL published to: file:/C:/Program Files/JBoss4.2.2/jboss-4.2.2.GA/server/default/data/wsdl/abcd-abcd.war/abcdRegistryService2629.wsdl
      15:57:52,395 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
      15:57:52,441 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
      15:57:52,457 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 27s:371ms

      UNSUCCESSFUL START OF JBOSS 4.2.2
      Partial End List of threads: There are not any threads after the UILServerILService thread (which it appears that the Successful start of JBoss has more threads started).
      Thread [UILServerILService Accept Thread] (Running)
      Partial list of console from UNSUCCESSFUL start:
      ...
      16:11:37,055 INFO [UILServerILService] JBossMQ UIL service available at : /127.0.0.1:8093
      16:11:37,133 INFO [DLQ] Bound to JNDI name: queue/DLQ
      16:11:37,383 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
      16:11:37,430 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
      16:11:38,148 INFO [DefaultEndpointRegistry] register: jboss.ws:context=abcd-abcd,endpoint=ABCD
      16:11:38,289 INFO [TomcatDeployer] deploy, ctxPath=/abcd-abcd, warUrl=.../tmp/deploy/tmp8051abcd-abcd-exp.war/