JBoss Fails to Start on SUSE

Thread view:

timasmith@hotmail.com - 12 May 2006 19:39 GMT

How very frustrating that JBoss runs so easily on Windows XP and it has
been such as battle on linux - SuSe.

What is the error message I hear you cry... here it is...

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

This is a brand new Suse 10 install with Java 1.5 installed , JAVA_HOME
set and the latest JBoss downloded 4.0.4

The port is not in use prior to starting JBoss but is about 1/2 way
through...

After the error I get a ton of scrolling stack traces which can only be
a bad thing...

Reply to this Message

Jon Martin Solaas - 13 May 2006 10:08 GMT

> How very frustrating that JBoss runs so easily on Windows XP and it has
> been such as battle on linux - SuSe.
[quoted text clipped - 11 lines]
> After the error I get a ton of scrolling stack traces which can only be
> a bad thing...

This sounds weird. How do you establish that 8080 is not in use before you
start jboss? What happens if you point a browser to the port before you
start jboss? What happens if you do it after jboss has started (and
complained about the port being already in use)? What happens if you change
the port jboss/tomcat uses to say 8090?

I've run jboss nicely on suse for a long time.

Signature

Jon Martin Solaas

Reply to this Message

timasmith@hotmail.com - 14 May 2006 04:00 GMT

Turns out Oracle was listening on the port.

Now my last remaining error message is

java.net.SocketException: bad argument for IP_MULTICAST_IF: address not

bound to any interface

Reply to this Message

senthsk@gmail.com - 17 May 2006 14:32 GMT

JBoss run's better in
SUSE the under windows as i am using it for nearly 2yrs

check if there any web server running under suse , mostly apache maybe
up

if that doen't help , change the http port under
JBoss\server\default\deploy\jbossweb-tomcat55.sar\server.xml

Reply to this Message

JBoss Fails to Start on SUSE

Free Magazines