Re: Mozilla crashes Tomcat.

[Christopher Mark Balz]

Yes, you are right, excuse me for not supplying the basic info of
several systems I am using.  I'm using:

tomcat 3.2 standalone - yes.
Java SDK 1.4 (includes JSSE)
Sun's JVM standard with SDK 1.4
The problem happens on Win2K and also on Linux RedHat 8.0 (Contains
latest OpenSSL).

I have by now done a fair bit of testing on this, all in the SSL mode. 
The application is stable when accessed by IE 5.5.  When using Mozilla 
1.1, however, the Tomcat Java process is inevitably thrown into a 
memory-allocating behavior (moving by about 10MB every 10 seconds) that 
continues until crash of the Tomcat Java process.  Sometimes this 
behavior is invoked simply by logging in under Mozilla (SSL), and 
sometimes it requires an access or two from Mozilla.  A tell-tale sign 
from Mozilla that the memory allocating behavior has been invoked is 
that a browser alert pops up saying "document contains no data".

I can run the very same accesses, using the very same front-end, from IE 
5.5 with apparently no problem, and the behavior of the servlet is 
exactly the same for both browsers.

I know that Mozilla uses a rather non-sensical security system whereby a 
site is deemed insecure if a window frame it contains is written to by 
JavaScript code from the original secured site.  IE, of course, does not 
do this.  Maybe there is some unfortunate interaction here with Tomcat? 
 For it seems that something in Moz's headers must be confusing Tomcat.

In any case, upgrading to 3.3 is not a bad idea.  I am about at the end 
of my rope with this bug.  I would go to 4.0 but want to stay as far 
away from the bleeding edge as reasonable and hope to avoid the changing 
of my configuration files that moving to 4.0 would necessitate.

I really hope someone out there has some ideas.  It is all too familiar 
a situation to me to have a Netscape product involved in just burning up 
days of my time.

   - CB



Ralph Einfeldt wrote:
> Maybe you should provide the answer to following questions:
>
> - Do you run tomcat stand alone ?
> - If yes which JSSE do you use ?
> - Which jvm do you use ?
> - On which operating system ?
>
> Maybe you should try to profile tomcat with a tool like
> OptimizeIt to see if it is tomcat or the underlying ssl
> implementation that has the leak.
>
> BTW:
>
> tc 3.2 is quite outdated.
> Maybe you should upgrade to 3.3.* or 4.*.
>
>
>>-Original Message-
>>From: Christopher Mark Balz [mailto:[EMAIL PROTECTED]]
>>Sent: Friday, November 29, 2002 9:21 AM
>>To: [EMAIL PROTECTED]
>>Subject: Mozilla crashes Tomcat.
>>
>>I'm pretty sure it's not my code since the leak starts immediately on
>>secure (ssl) session log-in to a static page (no servlet action
>>whatsoever).  If a Moz/N6+ browser is already logged in
>>however, after restarting the Tomcat server it takes a request from
>>Moz1.x/N6 to start the big leak that leads to an eventual JVM shutdown.
>>
>>
>
>
> --
> To unsubscribe, e-mail: 

> For additional commands, e-mail: 

>


--
". . . / This Cabinet is formd of Gold / And Pearl & Crystal shining bright
And within it opens into a World / . . .
Another England there I saw / Another London with its Tower
Another Thames & other Hills / And another pleasant Surrey Bower
. . ."
- from "The Crystal Cabinet", a poem by William Blake.



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Mozilla crashes Tomcat.

[David Brown]

Christopher Mark Balz writes: 

Mozilla 1.x/N6+ causes a devastating memory leak on Tomcat 3.2.4.  In 
side-by-side tests, IE 5.5 causes no such leak, but Moz1.x/N6+ cause 
Tomcat to simply start allocating memory until the heap size limit is 
exceeded by about 20MB, resulting in an eventual shutdown of the JVM. 

I'm pretty sure it's not my code since the leak starts immediately on 
secure (ssl) session log-in to a static page (no servlet action 
whatsoever).  If a Moz/N6+ browser is already logged in however, after 
restarting the Tomcat server it takes a request from Moz1.x/N6 to start 
the big leak that leads to an eventual JVM shutdown. 

I thought that Netscape existed only to torture client-side developers; it 
seems they've got something going on the server-side now!  Of course, it 
would be Tomcat's bug, but it's "funny" how many bugs always surround 
Netscape. 

Since this bug crashes my server, I would very much appreciate help with 
it.  I've seen other postings on the web indicating that this is a problem 
but have not seen anyone address it in a response. 

 - CB 

--
". . . / This Cabinet is formd of Gold / And Pearl & Crystal shining 
bright
And within it opens into a World / . . .
Another England there I saw / Another London with its Tower
Another Thames & other Hills / And another pleasant Surrey Bower
. . ."
- from "The Crystal Cabinet", a poem by William Blake. 


--
To unsubscribe, e-mail:   

For additional commands, e-mail: 
 




Hello Christopher, can u upgrade tc? david. 

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Mozilla crashes Tomcat.

[Ralph Einfeldt]

Maybe you should provide the answer to following questions:

- Do you run tomcat stand alone ?
- If yes which JSSE do you use ?
- Which jvm do you use ?
- On which operating system ?

Maybe you should try to profile tomcat with a tool like 
OptimizeIt to see if it is tomcat or the underlying ssl 
implementation that has the leak.

BTW:

tc 3.2 is quite outdated.
Maybe you should upgrade to 3.3.* or 4.*.

> -Original Message-
> From: Christopher Mark Balz [mailto:[EMAIL PROTECTED]]
> Sent: Friday, November 29, 2002 9:21 AM
> To: [EMAIL PROTECTED]
> Subject: Mozilla crashes Tomcat.
>  
> I'm pretty sure it's not my code since the leak starts immediately on 
> secure (ssl) session log-in to a static page (no servlet action 
> whatsoever).  If a Moz/N6+ browser is already logged in 
> however, after restarting the Tomcat server it takes a request from 
> Moz1.x/N6 to start the big leak that leads to an eventual JVM shutdown.
> 
>

--
To unsubscribe, e-mail:   
For additional commands, e-mail: