That was my evaluation. The error handling looked distinctly fragile to me.
To be honest, it looks like Sun have tightened up their state-checking with
the nio package (good) and exposed some weaknesses in the tomcat code (bad).
But then I have strong opinions on error handling (i.e. you should define a
policy for it in your coding standard). It seems too often that it's just
left to individual coders to make arbitrary decisions on which errors ignore
and which to escalate... seems to be a frequent cause of 'unexpected'
behaviour!
david
----- Original Message -----
From: "Jeff Larsen" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Friday, March 22, 2002 7:04 PM
Subject: Re: RE : java.lan.OutOfMemoryError
> OK, so I missed the part where they found that it was a Tomcat
> problem. But I stand by my point on avoiding first edition JDK
> releases. And I'm not necessarily flaming Sun here. If I didn't
> think Java was a godsend, I wouldn't be reading this list. It's just
> the reality of software that new major releases have greater potential
> for bugs. That's why they have maintenance releases. In general, I avoid
> ALL vendor's x.0 releases unless they have features I absolutely need. As
> far as I'm concerned, JDK 1.4.0 is not a "must have".
>
> My $0.02
>
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
