Bugs item #664635, was opened at 2003-01-08 15:33
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=664635&group_id=22866

Category: None
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Paul Morris (rpmorris)
Assigned to: Scott M Stark (starksm)
Summary: Too many open files causes JBoss 3.0  to crash 

Initial Comment:
OS: Linux 7.1
JDK: Occurs with Sun j2SDK 1.4.0 and IBM Java2 1.4

Occurs on JBoss v 3.0.0 & 3.0.4

The JVM process ends with the message "too many 
open files".  It can be recreated simply by opening 
and closing files for a long enough period of time .  
Once a file handle is allocated it doesn't appear to 
go away.  I've attached the console output as 
requestd in the bug report instructions.

I have captured the output from the lsof command 
showing system file handles at various stages of 
my JBoss app operation.  This output indicates that 
file handles don't go way even when the files are 
closed or deleted.  I can send this lsof output to 
whoever investigates this problem (the web form 
only allows one file to be attached to the bug 
report).

A number of developers have reported similar 
problems in the forum.  For an example see

http://www.jboss.org/forums/thread.jsp?
forum=61&thread=24687

----------------------------------------------------------------------

>Comment By: Paul Morris (rpmorris)
Date: 2003-01-14 10:12

Message:
Logged In: YES 
user_id=683772

I wrote a testcase as suggested and discovered that the code
didn't cause a file handle leak either in the JVM alone or
in the JBoss environment.  On further investigation, I
discovered that a 3rd party, native code library we are
using was failing to close a file which was the cause of our
problem.  

I never really understood how JBoss could be the source of
the problem, but I was out of ideas when I wrote the bug.  
Writing the test case jarred my brain enough to think of
other possible causes.  Thanks.

As far as my case is concerned this problem is resolved.

----------------------------------------------------------------------

Comment By: Scott M Stark (starksm)
Date: 2003-01-10 14:31

Message:
Logged In: YES 
user_id=175228

That should be fine.

----------------------------------------------------------------------

Comment By: Michael Kloster (mikekloster)
Date: 2003-01-10 14:03

Message:
Logged In: YES 
user_id=685435

Scott M Stark,

You wrote:
"If you have a sample program that runs in a standalone VM 
fine, but fails when deployed to JBoss using the same VM 
then submit that."

I have a a sample web application that can reproduce this
problem (over time).  The application consists only of JSP
pages and images and has no dynamic content (unless you
count the use of server side jsp includes).  If I can show
that this web application runs fine under Tomcat 4.x alone
or JBoss 2.4, but does have the cause the submitters problem
in JBoss 3.0.x will that satify your above stated
requirement that this must be shown, in fact, to be a JBoss
issue?

If so, I will take the time to create and document this
senario for you.

thank you for your time and effort.  Jboss is a wonderful
product!
Michael Kloster

----------------------------------------------------------------------

Comment By: Paul Morris (rpmorris)
Date: 2003-01-10 11:18

Message:
Logged In: YES 
user_id=683772

Of course, you're right Scott.  I didn't provide nearly 
enough information.  My first hunch was that this is a 
JVM problem so I switch from the Sun to the IBM JVM.  It 
occurs with both the Sun and the IBM JVM (versions 
1.4).  Perhaps they share some common code, I don't 
know.  I checked the Sun and IBM sites and no such bug 
has been reported for either JVM.    That said, I'll will 
right a test case, as Scott suggested.

In the meantime, here are more details of what my JBoss 
app is doing.  I have a stateful session bean which 
opens a temporary file during its processing.  The 
stream is declared transient.  The stream is closed on 
passivate and reopened on activate.  At the end of the 
bean's life the stream is closed and the temp file is 
deleted.  The code releases it reference to the File 
instance, so it can be garbage collected.

The file handles to the deleted files just don't go away 
(according to the lsof command output).   Every thread 
in the process has a handle to every deleted file.

I don't know if this helps, at this point.  I'll report back 
with the results of the JVM test you suggested.

----------------------------------------------------------------------

Comment By: Scott M Stark (starksm)
Date: 2003-01-08 16:16

Message:
Logged In: YES 
user_id=175228

How is the fact that opening and closing files files still leaves 
the descriptor open a JBoss problem? We don't do anything 
to intercept filesystem calls so the issue seems VM related. 
If you have a sample program that runs in a standalone VM 
fine, but fails when deployed to JBoss using the same VM 
then submit that. 

----------------------------------------------------------------------

Comment By: Paul Morris (rpmorris)
Date: 2003-01-08 15:46

Message:
Logged In: YES 
user_id=683772

The lsof out files mentioned in the previous comment 
are too large to upload to sourceforge.  They are 1, 4, & 
8 MBs.

----------------------------------------------------------------------

Comment By: Paul Morris (rpmorris)
Date: 2003-01-08 15:42

Message:
Logged In: YES 
user_id=683772

I'm going to attach 3 files lsofstart.out, lsotmid.out, and 
lsoflate.out.  They contain output from the lsof 
command during the operation of our jboss app (start, 
mid, and late, respectively.)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=664635&group_id=22866


-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to