Bugs item #518958, was opened at 2002-02-18 04:52
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=518958&group_id=22866
Category: JBossServer
Group: v2.4 (stable)
Status: Closed
Resolution: Invalid
Priority: 5
Submitted By: James Manning (jmm)
Assigned to: Nobody/Anonymous (nobody)
Summary: fetch of / off 8080 breaks server
Initial Comment:
-Fetched bundled 2.4.4 w/ tomcat 4.0.1
-started up
-hit port 8080, got exception on console and 500
Internal Server Error http response
-hit control-c to attempt to kill jboss
-tons of jboss threads spawn, causing "fork: resource
temporarily unavailable" for other processes of same
user.
Linux 2.4.9-7 (std. RH 7.2 box)
Server 2.4.4
Sun's JDK 1.3.1
I'll attach the server log (with stack traces) to this
bug.
----------------------------------------------------------------------
Comment By: Eddie Chan (ecc2)
Date: 2002-04-08 17:05
Message:
Logged In: YES
user_id=185272
hi,
Very strange, I've got a similar problem with JBoss2.4.4-
Jetty3.1.7 in production. When a JSP trying to lookup an
EJB Home Interface using JNDI, it waits for a long time
before returning (many minutes). It do not happen with
JBoss2.4.3-Jetty-3.1.3 (my previous JBoss setup on the same
machine).
However, this problem goes away if I change
the /etc/hosts as described below, so that the hostname now
127.0.0.1 instead of the real ip address.
Please note this doesn't happen in development (win2k &
linux). It maybe to do with the IPTable rules install on
the production machine?
So what JNDI changes was made berween 2.4.3->2.4.4?
eddie
----------------------------------------------------------------------
Comment By: James Manning (jmm)
Date: 2002-02-18 20:54
Message:
Logged In: YES
user_id=11485
Yup - that was it *sigh*
I changed my /etc/hosts so my default hostname would map to
127.0.0.1 instead of 192.168.1.1 and now it works like a champ.
----------------------------------------------------------------------
Comment By: James Manning (jmm)
Date: 2002-02-18 20:38
Message:
Logged In: YES
user_id=11485
Ok, digging a little deeper it looks like it might be a
local networking issue.
tcp 0 0 0.0.0.0:57817
0.0.0.0:* LISTEN 31049/java
tcp 0 1 192.168.1.1:57886
192.168.1.1:57817 SYN_SENT 31049/java
tcp 0 1 192.168.1.1:57888
192.168.1.1:57817 SYN_SENT 31049/java
Not sure why those are happening, but the timeout is taking
forever:
interest-client:
[java] Got context
[java] javax.naming.CommunicationException [Root
exception is java.rmi.ConnectException: Connection refused
to host: 192.168.1.1; nested exception is:
[java] java.net.ConnectException: Connection timed
out]
I'll keep poking around, but this is starting to look like
an issue outside of jboss-space given the above connection
during TCP handshaking :(
----------------------------------------------------------------------
Comment By: James Manning (jmm)
Date: 2002-02-18 07:41
Message:
Logged In: YES
user_id=11485
If I change run.sh to force -classic for the VM mode, I
don't get the resource problems (of course), but things are
still broken (client doesn't work, hangs at Got context,
the server doesn't shutdown, etc)
I've confirmed this with 2.4.4 and tomcat 4.0.1,
2.4.4 and tomcat 3.2.3, and 2.4.1 and tomcat 3.2.3
----------------------------------------------------------------------
Comment By: James Manning (jmm)
Date: 2002-02-18 06:09
Message:
Logged In: YES
user_id=11485
Breaks the same way with JDK 1.4.0
----------------------------------------------------------------------
Comment By: James Manning (jmm)
Date: 2002-02-18 06:08
Message:
Logged In: YES
user_id=11485
Breaks the same way with JDK 1.4.0
----------------------------------------------------------------------
Comment By: James Manning (jmm)
Date: 2002-02-18 05:31
Message:
Logged In: YES
user_id=11485
I added this to conf/default/log4j.properties but it didn't
result in any additional output to the console or
rollingfile appenders
log4j.category.org.jboss.ejb=TRACE#org.jboss.logging.TracePr
iority
I'd love to provide better information here, but I'm not
sure how since the above (which seems to be what the
properties file would indicate to do) isn't working
----------------------------------------------------------------------
Comment By: James Manning (jmm)
Date: 2002-02-18 05:04
Message:
Logged In: YES
user_id=11485
Even worse - when I just start up the server and then run
the InterestClient using the ant target, all I get is "Got
context" on the client output (stuck at the JNDI lookup)
and the same effect of tons of threads spawned and resource
temp. unavailable errors elsewhere - can't even do a jar
tvf because the jvm startup gives OutOfMemoryError. If I
kill the client, though, everything's fine.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=518958&group_id=22866
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development