Bugs item #832880, was opened at 2003-10-30 00:19
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=832880&group_id=22866
Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Brian Hogue (thetooth)
Assigned to: Nobody/Anonymous (nobody)
Summary: JNDI lookup does not return after/under moderate load
Initial Comment:
After upgrading from 2.4.4 to 3.2.1(Tomcat bundle) our
client applications began failing when attempting a jndi
Context lookup via, Object ref = (myHome)
jndiContext.lookup("foo/myData"); where jndiContext is
an InitialContext derived from
("java.naming.factory.initial", "org.jnp.interfaces.NamingC
ontextFactory");
("java.naming.provider.url", "myServer:1099");
("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp
.interfaces");
The application makes heavy use of SLSB's accessed
from remote clients, of which the above mentioned line
of code handles the lookup.
The failure is manifested by the above call not returning
after the server has been up for a few hours and has
experienced moderate load. The 2.4.4 server *never*
exhibited this behavior under extreme load. The only
changes with the upgrade was 3.2.1 JBoss and 1.4.2
java. The call does not seem to timeout but rather
to 'hang'. We are attempting to upgrade to 3.2.2,
hoping for a fix.
This is occuring on multiple servers; (compaq DL-380's)
running RH Linux 7.3 (Linux 2.4.18-19.7.xsmp) with
Hotspot VM (1.4.2_01). Apache is integrated via
mod_jk . The servers have 2 GB of ram with 1.5
available and dedicated to the VM.
The server socket on 1099 goes into and stays in a
SYN_RECV state. To remove the LAN/WAN as a possible
culprit we have replicated the problem (once the
problem starts occuring on a server) by trying to do the
context lookup from the server itself to itself, using
127.0.0.1 to make sure nothing is externally routed.
There are no memory consumption issues within the JVM
or at the OS level. CPU usage and load points are very
low. HTTP/servlet request servicing remains unaffected
when JBoss gets into the described state. Once JBoss is
restarted, it will behave normally for a time.
We are using the 'Standard Stateless SessionBean'
container with the ssl-invoker.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=832880&group_id=22866
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
