• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Jboss doesn't start - hangs on resource:jboss-log4j.xml

 
Greenhorn
Posts: 16
1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,

I've just installed Jboss EAP 4.3 and am trying to start up the production server via run.sh. The only thing I've changed was to set my JAVA to use JDK 1.6.0_22. However, I am finding that it is hanging on the line below (via the console):

14:11:10,833 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml

In my server.log, I see it doing this over and over again. I have not configured JMS, I just want to start the production server to verify the installation.

2011-01-19 14:40:04,574 DEBUG [org.jboss.jms.server.recovery.MessagingXAResourceWrapper] Recover java:/DefaultJMSProvider

Does anyone have any thoughts?
 
Sheriff
Posts: 10445
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
It's not hanging. The EAP version's production profile has CONSOLE logging disabled (via JBOSS_HOME/server/production/confi/jboss-log4j.xml). That's why you don't see any log messages after that message. Try accessing the URL http://localhost:8080/jmx-console after a few seconds from that message - that way you can test whether server is up.

 
Matt Herrington
Greenhorn
Posts: 16
1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for the reply. I've edited that log4j file and now I see extra information on the console. Why does the EAP version do this?

I am also unable to load the JMX Console. I go to my URL (I haven't changed the port so 8080 it is in server.xml) but the page cannot be found. If there is a port conflict or something (this is a server machine that others may be using), I would expect Jboss to tell me?
 
Jaikiran Pai
Sheriff
Posts: 10445
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Matt Herrington wrote:Thanks for the reply. I've edited that log4j file and now I see extra information on the console. Why does the EAP version do this?


The production profile is customized to improve performance. Console logging isn't really useful in production environments, so it's disabled.

Matt Herrington wrote:
I am also unable to load the JMX Console. I go to my URL (I haven't changed the port so 8080 it is in server.xml) but the page cannot be found. If there is a port conflict or something (this is a server machine that others may be using), I would expect Jboss to tell me?



Do you see any errors in the server.log? What's the exact command that you use to start the server and what exactly is the URL you are using to access jmx-console?


 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic