Chris' nightly test runs have only been failing with these OutOfMemory
exceptions for the last couple of nights. Either it was a recent change
that caused this or a recently added test that brought it into the open
-danch
Hiram Chirino wrote:
> I'm embarased.
>
> I'll look into it right away. Since the JMS client and server stuff is
> running in the same VM when using ASF I should be able to get rid of the
> socket calls and thus free up the threads that are polling the sockets.
>
> I'll also see if I can get rid of the SpySession Threads when using the
> ASF..
>
> Regards,
> Hiram
> ----- Original Message -----
> From: "Scott M Stark" <[EMAIL PROTECTED]>
> To: "JBoss Dev" <[EMAIL PROTECTED]>
> Sent: Thursday, June 21, 2001 8:04 PM
> Subject: [JBoss-dev] JMS thread usage
>
>
>
>> I have been running the jbosstest suite off and on throughout the day
>
> against
>
>> a snapshot of main on linux to look into the issue people have reported
>
> concerning
>
>> running out of processes on linux. I am seeing a steady increase in
>
> threads from
>
>> 32 for the baseline just after startup to 229 after one interation of the
>
> test suite to
>
>> 329 after about 10 iterations of the test suite.
>>
>> Clearly were leaking threads and it could be that the test code is not
>
> cleaning up
>
>> correctly, but I am seeing a large portion of the threads associated with
>
> JMS and I
>
>> question why this should be. Out of the 329 threads there are 266 JMS
>
> associated
>
>> threads.
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
