Costin,

I'm using RedHat 7.3, Apache 2.1.39, TC 4.1.6, mod_jk1, CoyoteJK2.
I build a new mod_jk.so everytime I get a new Tomcat. So it is definetley
recent.

I'm not sure what additional information to provide that hasn't already been
detailed in http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018.

Dave.

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: 01 July 2002 23:54
> To: Tomcat Developers List
> Subject: RE: [4.1.6] New milestone release soon
> 
> On Mon, 1 Jul 2002, David Oxley wrote:
> 
> > Costin,
> >
> > This problem still happens with 4.1.6.
> 
> Ok, I need more details then.
> 
> Are you sure the mod_jk is recent ?  Are you using mod_jk or mod_jk2 ( on
> apache side )?
> Any stack traces or message ?
> 
> As I said, I'm doing large uploads/downloads currently, and it works
> fine.
> 
> Costin
> 
> 
> >
> > Dave.
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > > Sent: 26 June 2002 16:57
> > > To: Tomcat Developers List
> > > Subject: RE: [4.1.6] New milestone release soon
> > >
> > > On Wed, 26 Jun 2002, David Oxley wrote:
> > >
> > > > Remy,
> > > >
> > > > Bug 10018 is pretty serious. Coyote-JK2 won't serve a resource
> (might
> > > apply
> > > > to dynamic content as well as static) that's bigger than 8k.
> > > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018
> > >
> > > Are you using a nightly ? I fixed the bug few days ago, I'm
> > > constantly doing large posts with jk2 in my day job.
> > >
> > > Please let me know ASAP if you still have this problem !
> > >
> > > Costin
> > >
> > >
> > > >
> > > > Dave.
> > > >
> > > > > -----Original Message-----
> > > > > From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
> > > > > Sent: 26 June 2002 12:14
> > > > > To: Tomcat Developers List
> > > > > Subject: [4.1.6] New milestone release soon
> > > > >
> > > > > There are only a few issues remaining:
> > > > > - Updating JNDI resources with the admin webapp is not dynamic
> (for
> > > > > reasons currently beyond my understanding). Doing a stop/start on
> the
> > > > > context allows to pick up the changes, so the bug is only minor.
> > > > > - Nacho's IIS issues with JK 2.
> > > > > - Costin's bug with Jasper 2.
> > > > >
> > > > > None of these are showstoppers IMO, but it would be best to have
> them
> > > > > fixed before the release is tagged (the objective being to get
> back to
> > > > > beta status). By friday maybe ?
> > > > >
> > > > > Remy
> > > > >
> > > > >
> > > > > --
> > > > > To unsubscribe, e-mail:   <mailto:tomcat-dev-
> > > > > [EMAIL PROTECTED]>
> > > > > For additional commands, e-mail: <mailto:tomcat-dev-
> > > > > [EMAIL PROTECTED]>
> > > >
> > > > --
> > > > To unsubscribe, e-mail:   <mailto:tomcat-dev-
> > > [EMAIL PROTECTED]>
> > > > For additional commands, e-mail: <mailto:tomcat-dev-
> > > [EMAIL PROTECTED]>
> > > >
> > > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:   <mailto:tomcat-dev-
> > > [EMAIL PROTECTED]>
> > > For additional commands, e-mail: <mailto:tomcat-dev-
> > > [EMAIL PROTECTED]>
> >
> > --
> > To unsubscribe, e-mail:   <mailto:tomcat-dev-
> [EMAIL PROTECTED]>
> > For additional commands, e-mail: <mailto:tomcat-dev-
> [EMAIL PROTECTED]>
> >
> >
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:tomcat-dev-
> [EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:tomcat-dev-
> [EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to