Profller Generates Thousands of Files in 10 minutes

[nickman]

I have been profiling an application on JBoss 3.2.6 on Solaris 9 using Java 1.4.2_06. The profiler generated about 55,000 files during a ten minute period, and during that time reported thousands of errors saying that the file could not be opened.

The result was about 54,950 zero sized files.

I am not sure why the files could not be opened, but I suspect a kernel configuration limitation on the number of open files.

However, I am puzzled by the number of files. I assume there is one file created per thread. If this is so, are there simply a ridiculous number of threads being created and destroyed, or is the profiler creating new files because it cannot open the ones it has created already ?

Thanks !

//Nicholas

[clebert.suconic]

It opens one file per thread.

As there is a thread pool inside JBoss, you shouldn't have so many threads opened.

Also, I have to do that, as I don't want to have synchronization between threads inside the DLL.

Also, I close the file when the thread is finished. (At least I should do it, and it would be a bug if it's not doing it. I will check it anyway)

[nickman]

As I understand it, this issue is not being observed on Windows, where the profiler generates only about 250 files for the same application under the same load. So I am wondering if the new Solaris 9 1:1 threading model is the cause of the difference. Perhaps in Windows, the LWP multiplex into a lower number of actual native threads......

At any rate, this is what we see in the standard out (several thousand times):

********************************************************
ERROR: Cannot open file /export/home/jboss/profileData/serverspy_743_thread_1110469628357_79971957197600_470.log.gz
********************************************************

Any ideas ?

[clebert.suconic]

No...

I will have to test it in Solaris.

We will have a new Solaris box installed in couple days. I will be working on it.

http://jira.jboss.com/jira/browse/JBPROFILER-11


Clebert

[olivier_etienne]

Same problem on Linux RedHat 4