You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Jeff Tulley <JT...@novell.com> on 2003/04/01 19:12:32 UTC
Connector issues
There are some real problems with the Coyote Connectors right now.
The main problem biting me (and a few others recently) is bugzilla bug
# 10229 - form parameters not being preserved across a login
redirection.
The answer given on the user list (by me also) is typically, "Use an
non-Coyote connector". Unfortunately that is not a good answer.
If they move back to the deprecated AJP13Connector, they will
experience MBean exceptions that, among other things, make the Tomcat
shutdown not function correctly.
Beyond that they are stuck with not using a webserver plugin and
instead going directly to an HTTP connector (non-Coyote).
I would propose two things:
1) Fix the MBean exception in the Ajp13Connector. I can provide a
patch for this, it is very simple. Even though this is deprecated, the
reality is that people might need to use it due to bugs and/or
unimplemented features in the Coyote connectors. It may be their only
choice, and if we can make it work easily, why not?
2) Fix this form authentication problem in the Coyote connector. I
will look into this and see if it is something that I can do and submit
a patch for.
I actually have similar issues with the native side connector story but
that is for another day.
Anybody know off hand what needs to happen for item #2 above?
Jeff Tulley (jtulley@novell.com)
(801)861-5322
Novell, Inc., The Leading Provider of Net Business Solutions
http://www.novell.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: Connector issues
Posted by "Jess M. Holle" <je...@ptc.com>.
Jeff Tulley wrote:
>There are some real problems with the Coyote Connectors right now.
>The main problem biting me (and a few others recently) is bugzilla bug
># 10229 - form parameters not being preserved across a login
>redirection.
>The answer given on the user list (by me also) is typically, "Use an
>non-Coyote connector". Unfortunately that is not a good answer.
>If they move back to the deprecated AJP13Connector, they will
>experience MBean exceptions that, among other things, make the Tomcat
>shutdown not function correctly.
>Beyond that they are stuck with not using a webserver plugin and
>instead going directly to an HTTP connector (non-Coyote).
>
>I would propose two things:
>1) Fix the MBean exception in the Ajp13Connector. I can provide a
>patch for this, it is very simple. Even though this is deprecated, the
>reality is that people might need to use it due to bugs and/or
>unimplemented features in the Coyote connectors. It may be their only
>choice, and if we can make it work easily, why not?
>
I would be interested in the patch to this. I have no issues with the
Coyote connector at the moment -- but I would like to see the fallback
(i.e. Ajp13Connector) in a more functional state.
>2) Fix this form authentication problem in the Coyote connector. I
>will look into this and see if it is something that I can do and submit
>a patch for.
>
>I actually have similar issues with the native side connector story but
>that is for another day.
>
I was under the impression that mod_jk2 was "not production ready" by
most measures -- and that mod_jk was good enough for most purposes (and
quite production ready)...
--
Jess Holle
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: Connector issues
Posted by Bill Barker <wb...@wilshire.com>.
----- Original Message -----
From: "Jeff Tulley" <JT...@novell.com>
To: <to...@jakarta.apache.org>
Sent: Tuesday, April 01, 2003 9:12 AM
Subject: Connector issues
> There are some real problems with the Coyote Connectors right now.
> The main problem biting me (and a few others recently) is bugzilla bug
> # 10229 - form parameters not being preserved across a login
> redirection.
> The answer given on the user list (by me also) is typically, "Use an
> non-Coyote connector". Unfortunately that is not a good answer.
> If they move back to the deprecated AJP13Connector, they will
> experience MBean exceptions that, among other things, make the Tomcat
> shutdown not function correctly.
> Beyond that they are stuck with not using a webserver plugin and
> instead going directly to an HTTP connector (non-Coyote).
>
> I would propose two things:
> 1) Fix the MBean exception in the Ajp13Connector. I can provide a
> patch for this, it is very simple. Even though this is deprecated, the
> reality is that people might need to use it due to bugs and/or
> unimplemented features in the Coyote connectors. It may be their only
> choice, and if we can make it work easily, why not?
> 2) Fix this form authentication problem in the Coyote connector. I
> will look into this and see if it is something that I can do and submit
> a patch for.
>
> I actually have similar issues with the native side connector story but
> that is for another day.
>
> Anybody know off hand what needs to happen for item #2 above?
Primarily, o.a.c.tc4.CoyoteRequest needs to implement addParameter (at least
more than it does now :). There are probably a few other related methods
that aren't functional as well.
>
> Jeff Tulley (jtulley@novell.com)
> (801)861-5322
> Novell, Inc., The Leading Provider of Net Business Solutions
> http://www.novell.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: Connector issues
Posted by Costin Manolache <cm...@yahoo.com>.
Sorry for the delay.
IMO the right solution is to fix #10229 for coyote.
There are a lot of problems in the old connectors - even if mod_jk2
is not yet as stable as mod_jk1, the java side and coyote are far
better than the old impl.
I'm +0 on fixing the MBean exception - AFAIK upgrading commons-modeler
should fix most of the problems with undeclared mbeans. The real problem
is that the Ajp13Connector has a lot of problems and it's no longer
supported - all work is on the coyote connector, I don't know anyone
testing or supporting Ajp13.
Costin
Jeff Tulley wrote:
> There are some real problems with the Coyote Connectors right now.
> The main problem biting me (and a few others recently) is bugzilla bug
> # 10229 - form parameters not being preserved across a login
> redirection.
> The answer given on the user list (by me also) is typically, "Use an
> non-Coyote connector". Unfortunately that is not a good answer.
> If they move back to the deprecated AJP13Connector, they will
> experience MBean exceptions that, among other things, make the Tomcat
> shutdown not function correctly.
> Beyond that they are stuck with not using a webserver plugin and
> instead going directly to an HTTP connector (non-Coyote).
>
> I would propose two things:
> 1) Fix the MBean exception in the Ajp13Connector. I can provide a
> patch for this, it is very simple. Even though this is deprecated, the
> reality is that people might need to use it due to bugs and/or
> unimplemented features in the Coyote connectors. It may be their only
> choice, and if we can make it work easily, why not?
> 2) Fix this form authentication problem in the Coyote connector. I
> will look into this and see if it is something that I can do and submit
> a patch for.
>
> I actually have similar issues with the native side connector story but
> that is for another day.
>
> Anybody know off hand what needs to happen for item #2 above?
>
> Jeff Tulley (jtulley@novell.com)
> (801)861-5322
> Novell, Inc., The Leading Provider of Net Business Solutions
> http://www.novell.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org