java kills test3 dead?

[Sessoms, Mack]

nope, locked up again.  can't even ssh to it.

Sessoms, Mack wrote:

> fixed this by disabling SELinux under System Settings->Security 
> Level->SELinux tab.  Set it to disabled and fc2t3 doesn't lockup when 
> I start tomcat.  I went back and it showed Active again but the system 
> seems to be working.  I'll run my performance tests.
>
> Sessoms, Mack wrote:
>
>> just did a fresh install of fc2t3, ibm java 2 sdk 1.4.1 sr2 and 
>> tomcat 5.0.19.  started tomcat and fc2t3 is locked, no response from 
>> keyboard or mouse.  this stack worked well on fc2t2, performance was 
>> awesome.  with fc2t2 and this stack, i had older hardware out running 
>> newer hardware which had fc1 (2.4.22) loaded.
>>
>> Keith Irwin wrote:
>>
>>> Folks--
>>>
>>> I've installed sun's 1.4.2_4 SDK on my test3 system, then run a big ole
>>> "maven" build a few times, and have jboss running, all from within my
>>> normal user account (no SELinux).
>>>
>>> Seems that running java a lot can take down the system. It "feels" like
>>> a kernel problem, because it happens whether or not I'm in X.
>>>
>>> Anyway, I was wondering if ANYONE else around here has had this 
>>> problem?
>>>
>>> I wrote about it here:
>>>
>>> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=121902
>>>
>>> I have similar problems with test2, but thought it was just some weird
>>> SELinux interaction.
>>>
>>> Any confirmation?
>>>
>>> Keith
>>>
>>>
>>>  
>>>
>>
>>
>
>