2 Replies Latest reply on Jul 7, 2004 1:00 AM by Albert Fang

    3.2.4 & 3.2.5 startup problem on Fecora Core 2

    Albert Fang Newbie

      I've been using 3.2.3 and it just works fine. But since I upgraded to 3.2.4 ant 3.2.5, I always got this startup problem.
      21:57:32,038 INFO [DLQ] Bound to JNDI name: queue/DLQ
      21:57:32,130 INFO [testTopic] Bound to JNDI name: topic/testTopic
      21:57:32,154 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
      21:57:32,181 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic21:57:32,206 INFO [testQueue] Bound to JNDI name: queue/testQueue
      21:57:32,234 INFO [A] Bound to JNDI name: queue/A
      21:57:32,263 INFO [B] Bound to JNDI name: queue/B
      21:57:32,287 INFO [C] Bound to JNDI name: queue/C
      21:57:32,312 INFO [D] Bound to JNDI name: queue/D
      21:57:32,337 INFO [ex] Bound to JNDI name: queue/ex
      21:57:33,296 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=file:/usr/jboss-3.2.5/server/default/deploy/jmx-console.war/
      21:57:34,073 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=file:/usr/jboss-3.2.5/server/default/tmp/deploy/tmp2370web-console.war/
      21:57:36,139 INFO [Server] JBoss (MX MicroKernel) [3.2.5 (build: CVSTag=JBoss_3_2_5 date=200406251954)] Started in 33s:826ms
      21:57:36,140 INFO [Tomcat5] Saw org.jboss.system.server.started notification, starting connectors
      21:57:36,219 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
      21:57:36,748 INFO [ChannelSocket] JK2: ajp13 listening on /0.0.0.0:8009
      21:57:36,774 INFO [JkMain] Jk running ID=0 time=0/54 config=null

      It just stuck there.

      My platform is Fedora Core 2 and I tried j2sdk 1.4.2_04 and 1.4.2_05, It just did'nt work.

      Can someone help me out there ?