Service Pack 1 has (fortunately, in my view) been upheld by a serious bug on SMP
machines that causes intermittent, bogus "Too many concurrent requests" messages
to be sent to a client even when there aren't really too many requests. We are
trying to get this fixed, but it's hard to reproduce reliably, though we have
access to a customer's machine where it is quite reliable. I'm kind of
surprised no one has reported this problem here.
Anyway, this may be good news for the service pack because we have some time to
try to fix more bugs. So the latter two bugs (and others that have come up on
this list recently) listed below are being looked at. The first one is unclear
to me. I don't recall what that one's referring to ("can't handle external
entity . . ."), so if you can refresh my memory, Geoff, I'll look into it.
Scott S.
> -----Original Message-----
> From: Geoff Soutter [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 22, 2000 5:33 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Service Pack for JRun 3.0?
>
>
> my "few things" were:
>
> - can't handle external entity as per spec in the web.xml file
> - admin UI gets "confused: (can't save to directory 'null') if your servlet
> is the same name as your webapp
> - implementation of Request.getDateHeader() is broken for If-Modified-Since
> header (and breaks Servlet.getLastModified() if your servlet uses that)
>
> Are you having the same problems or did you find a set of new ones?
>
> geoff
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
