You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "c." <ch...@gmail.com> on 2007/03/23 17:47:47 UTC
Tomcat mod_proxy_ajp and jk exceptions
Hello,
I'm using mod_proxy_ajp as my link b/w tomcat and apache. Things are
working well with the exception of getting the following error:
2007-03-22 20:02:42,875 [TP-Processor51] WARN
org.apache.jk.core.MsgContext - Error sending end packet
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518)
at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:112)
at org.apache.jk.core.MsgContext.action(MsgContext.java:293)
at org.apache.coyote.Response.action(Response.java:182)
at org.apache.coyote.Response.finish(Response.java:304)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:204)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754)
at org.apache.jk.common.ChannelSocket.processConnection(
ChannelSocket.java:684)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(
ChannelSocket.java:876)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(
ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
2007-03-22 20:02:42,875 [TP-Processor51] WARN
org.apache.jk.common.ChannelSocket - processCallbacks status 2
a few times a day.
This is from a medium traffic e-commerce site (approx. 1000 trans a day) and
it seems to occur when the user is on the secure checkout page and hits the
order button. They complain of being presented with a blank page after
hitting the purchase button.
Pertinent details from the servlet.xml:
<Connector address="139.0.0.1"
port="8009"
enableLookups="false"
protocol="AJP/1.3"
minSpareThreads="20"
maxSpareThreads="200"
maxThreads="1024"
connectionTimeout="600000"
/>
Any ideas as to why this is happening?
Thanks,
Chris.
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
Christopher Schultz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Chris,
>
> c. wrote:
>
>> Filip, thanks for the info, I'll listen to anyone with good advice. So you
>> recommend mod_proxy_http over mod_jk?
>>
>
> That's a good question. In two successive messages, he recommended each
> over the other. <shrug>
>
>
>> Is it the same basic setup as mod_proxy_ajp? Looking at the doc (
>> http://httpd.apache.org/docs/2.0/mod/mod_proxy_http.html) it doesn't give
>> much info.
>>
>
> That's because there isn't much info (at least, the last time I checked)
> out there. Use of mod_proxy_ajp is much simpler than mod_jk. Basically,
> use the same syntax for mod_proxy to proxy HTTP connections but instead
> you use a target URL like this:
>
> ajp://host:port/path/to/webapp
>
> While mod_proxy_ajp is easier to configure, I believe that it is
> severely limited by it's syntax, limiting your configuration
> possibilities. We can't use it because we have two workers for the same
> URL space, and cannot configure mod_proxy_ajp to do this.
>
> I'm not sure why Filip suggested that debugging mod_proxy_ajp would be
> easier than mod_jk.
>
you need to read the posts :), I'm recommending mod_proxy_http over both
AJP modules.
AJP is not a favorable protocol at all
Filip
> - -chris
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFGBEbJ9CaO5/Lv0PARAvETAJ4sdY+O+FPnFPH2SCtlP+tO3r/A2QCfaTbL
> wmRoxXK2uwhQrnYi26dK7xU=
> =hLqF
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chris,
c. wrote:
> Filip, thanks for the info, I'll listen to anyone with good advice. So you
> recommend mod_proxy_http over mod_jk?
That's a good question. In two successive messages, he recommended each
over the other. <shrug>
> Is it the same basic setup as mod_proxy_ajp? Looking at the doc (
> http://httpd.apache.org/docs/2.0/mod/mod_proxy_http.html) it doesn't give
> much info.
That's because there isn't much info (at least, the last time I checked)
out there. Use of mod_proxy_ajp is much simpler than mod_jk. Basically,
use the same syntax for mod_proxy to proxy HTTP connections but instead
you use a target URL like this:
ajp://host:port/path/to/webapp
While mod_proxy_ajp is easier to configure, I believe that it is
severely limited by it's syntax, limiting your configuration
possibilities. We can't use it because we have two workers for the same
URL space, and cannot configure mod_proxy_ajp to do this.
I'm not sure why Filip suggested that debugging mod_proxy_ajp would be
easier than mod_jk.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGBEbJ9CaO5/Lv0PARAvETAJ4sdY+O+FPnFPH2SCtlP+tO3r/A2QCfaTbL
wmRoxXK2uwhQrnYi26dK7xU=
=hLqF
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by "c." <ch...@gmail.com>.
Filip, I know this isn't the httpd forum, but how did you get the ssl
working using mod_proxy_http?
Chris.
On 3/23/07, c. <ch...@gmail.com> wrote:
>
> Filip, thanks for the info, I'll listen to anyone with good advice. So
> you recommend mod_proxy_http over mod_jk?
>
> Is it the same basic setup as mod_proxy_ajp? Looking at the doc (http://httpd.apache.org/docs/2.0/mod/mod_proxy_http.html)
> it doesn't give much info.
>
> c.
>
> On 3/23/07, Filip Hanik - Dev Lists < devlists@hanik.com> wrote:
> >
> > Christopher Schultz wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > Filip,
> > >
> > > Filip Hanik - Dev Lists wrote:
> > >
> > >> I'd recommend moving to mod_proxy_http, it will be easier for you to
> > debug.
> > >>
> > >
> > > Bah! :(
> > >
> > that sounds knowledgeable :)
> > >
> > >> the error below seems to be more of a problem with apache
> > (mod_proxy_ajp)
> > >> then with tomcat, tomcat is simply trying to write a message, but the
> > >> connection is no longer valid.
> > >>
> > >
> > > The problem is that the connection has been closed at some point. It's
> > > usually because the user hit the STOP button on their browser and
> > closed
> > > the connection.
> > >
> > > You can pretty much ignore these errors.
> > >
> > yes, and instead filling up the logs
> > > No need to switch connectors.
> > >
> > actually, if you are gonna use AJP, use mod_jk, mod_proxy_ajp is not
> > moving in the same pace.
> > however, I'd recommend using HTTP, the HTTP connectors on tomcat are
> > finely tuned,
> > if there ever is a problem in the communication, you'll just put in a
> > sniffer and can see it direct.
> >
> > but hey, don't listen to me :)
> > Filip
> > > - -chris
> > >
> > > -----BEGIN PGP SIGNATURE-----
> > > Version: GnuPG v1.4.7 (MingW32)
> > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> > >
> > > iD8DBQFGBA1E9CaO5/Lv0PARAqGMAJ90+P79Kt1Vhhm+a+aeNvdupzhJ4QCcDhzn
> > > 58umlhiChNndLXSputpG5rk=
> > > =IxYN
> > > -----END PGP SIGNATURE-----
> > >
> > > ---------------------------------------------------------------------
> > > To start a new topic, e-mail: users@tomcat.apache.org
> > > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> > > For additional commands, e-mail: users-help@tomcat.apache.org
> > >
> > >
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To start a new topic, e-mail: users@tomcat.apache.org
> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: users-help@tomcat.apache.org
> >
> >
>
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
sent it directly to your email address
Filip
c. wrote:
> seriously? if so can you send me the link?
>
> if not just call me gullible.
>
> On 3/26/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
>>
>> Mladen Turk wrote:
>> > Filip Hanik - Dev Lists wrote:
>> >> or simply set a few headers in httpd when the request came in over
>> >> SSL, and then have a filter read those headers
>> >>
>> >
>> > OK, by now, I think everyone are aware that you
>> > don't like the AJP protocol.
>>
>> being on the support side of it has not been fun :)
>> mod_jk -> mod_webapp -> mod_jk2 ->back to mod_jk
>>
>> > You should blog about that :)
>> there is a webinar on wednesday coming up
>>
>> Filip
>>
>> >
>> > Regards,
>> > Mladen.
>> >
>> > ---------------------------------------------------------------------
>> > To start a new topic, e-mail: users@tomcat.apache.org
>> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> > For additional commands, e-mail: users-help@tomcat.apache.org
>> >
>> >
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.18/733 - Release Date: 3/25/2007 11:07 AM
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by "c." <ch...@gmail.com>.
seriously? if so can you send me the link?
if not just call me gullible.
On 3/26/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
>
> Mladen Turk wrote:
> > Filip Hanik - Dev Lists wrote:
> >> or simply set a few headers in httpd when the request came in over
> >> SSL, and then have a filter read those headers
> >>
> >
> > OK, by now, I think everyone are aware that you
> > don't like the AJP protocol.
>
> being on the support side of it has not been fun :)
> mod_jk -> mod_webapp -> mod_jk2 ->back to mod_jk
>
> > You should blog about that :)
> there is a webinar on wednesday coming up
>
> Filip
>
> >
> > Regards,
> > Mladen.
> >
> > ---------------------------------------------------------------------
> > To start a new topic, e-mail: users@tomcat.apache.org
> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: users-help@tomcat.apache.org
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
Mladen Turk wrote:
> Filip Hanik - Dev Lists wrote:
>> or simply set a few headers in httpd when the request came in over
>> SSL, and then have a filter read those headers
>>
>
> OK, by now, I think everyone are aware that you
> don't like the AJP protocol.
being on the support side of it has not been fun :)
mod_jk -> mod_webapp -> mod_jk2 ->back to mod_jk
> You should blog about that :)
there is a webinar on wednesday coming up
Filip
>
> Regards,
> Mladen.
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by Mladen Turk <ml...@gmail.com>.
Filip Hanik - Dev Lists wrote:
> or simply set a few headers in httpd when the request came in over SSL,
> and then have a filter read those headers
>
OK, by now, I think everyone are aware that you
don't like the AJP protocol.
You should blog about that :)
Regards,
Mladen.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
or simply set a few headers in httpd when the request came in over SSL,
and then have a filter read those headers
Filip
Rainer Jung wrote:
> Usually there are SSL problems with (reverse) proxying concerning URLs
> for redirects, since the Tomcat side doesn't "know" any longer that
> SSL has been spoken originally. So self-referencing URLs use http as
> the protocol. AJP fixes this, which is the correct interpretation of
> AJP supporting SSL (forwarding protocol information including ciphers
> etc.).
>
> To work around the URL problem, you need to set some attributes on
> your Tomcat httpd connector in server.xml, especially "proxyName",
> "proxyPort" and "scheme", maybe also "secure".
>
> See.
>
> http://tomcat.apache.org/tomcat-5.5-doc/config/http.html
>
> Regards,
>
> Rainer
>
> Filip Hanik - Dev Lists wrote:
>> c. wrote:
>>> so would it make sense to assume that since SSL worked without any
>>> extra
>>> config changes when I added the AJP config that it should work
>>> without any
>>> changes when using mod_proxy_http?
>> correct, the info I gave you is for when you want SSL between apache
>> and tomcat, you are obviously talking about SSL between the browser
>> and the apache httpd server.
>>
>> if you don't need SSL between apache and tomcat (which you obviously
>> don't need since you ran AJP before) then don't bother with SSL for
>> mod_proxy either
>>
>> Filip
>>>
>>> On 3/23/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
>>>>
>>>> AJP doesn't use SSL, never has, so I'm not sure what the problem
>>>> would be
>>>> the only way to get SSL between apache and tomcat, is to use mod_proxy
>>>> Filip
>>>>
>>>>
>>>> c. wrote:
>>>> > Thanks Filip,
>>>> >
>>>> > We've always had the need for SSL, and our config worked without any
>>>> > changes
>>>> > when I put AJP in the mix. It doesn't, however, work with proxy
>>>> http.
>>>> >
>>>> > On 3/23/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
>>>> >>
>>>> >> in my last email I forgot one
>>>> >>
>>>> >> SSLProxyMachineCertificateFile <--
>>>> >> SSLProxyEngine
>>>> >> SSLProxyMachineCertificatePath
>>>> >> SSLEngine
>>>> >> SSLProxyProtocol,
>>>> >> SSLProxyCipherSuite
>>>> >>
>>>> >> c. wrote:
>>>> >> > Filip, thanks for the info, I'll listen to anyone with good
>>>> advice.
>>>> >> > So you
>>>> >> > recommend mod_proxy_http over mod_jk?
>>>> >> >
>>>> >> > Is it the same basic setup as mod_proxy_ajp? Looking at the
>>>> doc (
>>>> >> > http://httpd.apache.org/docs/2.0/mod/mod_proxy_http.html) it
>>>> doesn't
>>>> >> give
>>>> >> > much info.
>>>> >> >
>>>> >> > c.
>>>> >> >
>>>> >> > On 3/23/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
>>>> >> >>
>>>> >> >> Christopher Schultz wrote:
>>>> >> >> > -----BEGIN PGP SIGNED MESSAGE-----
>>>> >> >> > Hash: SHA1
>>>> >> >> >
>>>> >> >> > Filip,
>>>> >> >> >
>>>> >> >> > Filip Hanik - Dev Lists wrote:
>>>> >> >> >
>>>> >> >> >> I'd recommend moving to mod_proxy_http, it will be easier for
>>>> >> you to
>>>> >> >> debug.
>>>> >> >> >>
>>>> >> >> >
>>>> >> >> > Bah! :(
>>>> >> >> >
>>>> >> >> that sounds knowledgeable :)
>>>> >> >> >
>>>> >> >> >> the error below seems to be more of a problem with apache
>>>> >> >> (mod_proxy_ajp)
>>>> >> >> >> then with tomcat, tomcat is simply trying to write a
>>>> message, but
>>>> >> the
>>>> >> >> >> connection is no longer valid.
>>>> >> >> >>
>>>> >> >> >
>>>> >> >> > The problem is that the connection has been closed at some
>>>> point.
>>>> >> It's
>>>> >> >> > usually because the user hit the STOP button on their
>>>> browser and
>>>> >> >> closed
>>>> >> >> > the connection.
>>>> >> >> >
>>>> >> >> > You can pretty much ignore these errors.
>>>> >> >> >
>>>> >> >> yes, and instead filling up the logs
>>>> >> >> > No need to switch connectors.
>>>> >> >> >
>>>> >> >> actually, if you are gonna use AJP, use mod_jk, mod_proxy_ajp
>>>> is not
>>>> >> >> moving in the same pace.
>>>> >> >> however, I'd recommend using HTTP, the HTTP connectors on
>>>> tomcat are
>>>> >> >> finely tuned,
>>>> >> >> if there ever is a problem in the communication, you'll just
>>>> put in
>>>> a
>>>> >> >> sniffer and can see it direct.
>>>> >> >>
>>>> >> >> but hey, don't listen to me :)
>>>> >> >> Filip
>>>> >> >> > - -chris
>>>> >> >> >
>>>> >> >> > -----BEGIN PGP SIGNATURE-----
>>>> >> >> > Version: GnuPG v1.4.7 (MingW32)
>>>> >> >> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>>>> >> >> >
>>>> >> >> >
>>>> iD8DBQFGBA1E9CaO5/Lv0PARAqGMAJ90+P79Kt1Vhhm+a+aeNvdupzhJ4QCcDhzn
>>>> >> >> > 58umlhiChNndLXSputpG5rk=
>>>> >> >> > =IxYN
>>>> >> >> > -----END PGP SIGNATURE-----
>>>> >> >> >
>>>> >> >> >
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by Rainer Jung <ra...@kippdata.de>.
Usually there are SSL problems with (reverse) proxying concerning URLs
for redirects, since the Tomcat side doesn't "know" any longer that SSL
has been spoken originally. So self-referencing URLs use http as the
protocol. AJP fixes this, which is the correct interpretation of AJP
supporting SSL (forwarding protocol information including ciphers etc.).
To work around the URL problem, you need to set some attributes on your
Tomcat httpd connector in server.xml, especially "proxyName",
"proxyPort" and "scheme", maybe also "secure".
See.
http://tomcat.apache.org/tomcat-5.5-doc/config/http.html
Regards,
Rainer
Filip Hanik - Dev Lists wrote:
> c. wrote:
>> so would it make sense to assume that since SSL worked without any extra
>> config changes when I added the AJP config that it should work without
>> any
>> changes when using mod_proxy_http?
> correct, the info I gave you is for when you want SSL between apache and
> tomcat, you are obviously talking about SSL between the browser and the
> apache httpd server.
>
> if you don't need SSL between apache and tomcat (which you obviously
> don't need since you ran AJP before) then don't bother with SSL for
> mod_proxy either
>
> Filip
>>
>> On 3/23/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
>>>
>>> AJP doesn't use SSL, never has, so I'm not sure what the problem
>>> would be
>>> the only way to get SSL between apache and tomcat, is to use mod_proxy
>>> Filip
>>>
>>>
>>> c. wrote:
>>> > Thanks Filip,
>>> >
>>> > We've always had the need for SSL, and our config worked without any
>>> > changes
>>> > when I put AJP in the mix. It doesn't, however, work with proxy http.
>>> >
>>> > On 3/23/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
>>> >>
>>> >> in my last email I forgot one
>>> >>
>>> >> SSLProxyMachineCertificateFile <--
>>> >> SSLProxyEngine
>>> >> SSLProxyMachineCertificatePath
>>> >> SSLEngine
>>> >> SSLProxyProtocol,
>>> >> SSLProxyCipherSuite
>>> >>
>>> >> c. wrote:
>>> >> > Filip, thanks for the info, I'll listen to anyone with good advice.
>>> >> > So you
>>> >> > recommend mod_proxy_http over mod_jk?
>>> >> >
>>> >> > Is it the same basic setup as mod_proxy_ajp? Looking at the doc (
>>> >> > http://httpd.apache.org/docs/2.0/mod/mod_proxy_http.html) it
>>> doesn't
>>> >> give
>>> >> > much info.
>>> >> >
>>> >> > c.
>>> >> >
>>> >> > On 3/23/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
>>> >> >>
>>> >> >> Christopher Schultz wrote:
>>> >> >> > -----BEGIN PGP SIGNED MESSAGE-----
>>> >> >> > Hash: SHA1
>>> >> >> >
>>> >> >> > Filip,
>>> >> >> >
>>> >> >> > Filip Hanik - Dev Lists wrote:
>>> >> >> >
>>> >> >> >> I'd recommend moving to mod_proxy_http, it will be easier for
>>> >> you to
>>> >> >> debug.
>>> >> >> >>
>>> >> >> >
>>> >> >> > Bah! :(
>>> >> >> >
>>> >> >> that sounds knowledgeable :)
>>> >> >> >
>>> >> >> >> the error below seems to be more of a problem with apache
>>> >> >> (mod_proxy_ajp)
>>> >> >> >> then with tomcat, tomcat is simply trying to write a
>>> message, but
>>> >> the
>>> >> >> >> connection is no longer valid.
>>> >> >> >>
>>> >> >> >
>>> >> >> > The problem is that the connection has been closed at some
>>> point.
>>> >> It's
>>> >> >> > usually because the user hit the STOP button on their browser
>>> and
>>> >> >> closed
>>> >> >> > the connection.
>>> >> >> >
>>> >> >> > You can pretty much ignore these errors.
>>> >> >> >
>>> >> >> yes, and instead filling up the logs
>>> >> >> > No need to switch connectors.
>>> >> >> >
>>> >> >> actually, if you are gonna use AJP, use mod_jk, mod_proxy_ajp
>>> is not
>>> >> >> moving in the same pace.
>>> >> >> however, I'd recommend using HTTP, the HTTP connectors on
>>> tomcat are
>>> >> >> finely tuned,
>>> >> >> if there ever is a problem in the communication, you'll just
>>> put in
>>> a
>>> >> >> sniffer and can see it direct.
>>> >> >>
>>> >> >> but hey, don't listen to me :)
>>> >> >> Filip
>>> >> >> > - -chris
>>> >> >> >
>>> >> >> > -----BEGIN PGP SIGNATURE-----
>>> >> >> > Version: GnuPG v1.4.7 (MingW32)
>>> >> >> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>>> >> >> >
>>> >> >> > iD8DBQFGBA1E9CaO5/Lv0PARAqGMAJ90+P79Kt1Vhhm+a+aeNvdupzhJ4QCcDhzn
>>> >> >> > 58umlhiChNndLXSputpG5rk=
>>> >> >> > =IxYN
>>> >> >> > -----END PGP SIGNATURE-----
>>> >> >> >
>>> >> >> >
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
c. wrote:
> so would it make sense to assume that since SSL worked without any extra
> config changes when I added the AJP config that it should work without
> any
> changes when using mod_proxy_http?
correct, the info I gave you is for when you want SSL between apache and
tomcat, you are obviously talking about SSL between the browser and the
apache httpd server.
if you don't need SSL between apache and tomcat (which you obviously
don't need since you ran AJP before) then don't bother with SSL for
mod_proxy either
Filip
>
> On 3/23/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
>>
>> AJP doesn't use SSL, never has, so I'm not sure what the problem
>> would be
>> the only way to get SSL between apache and tomcat, is to use mod_proxy
>> Filip
>>
>>
>> c. wrote:
>> > Thanks Filip,
>> >
>> > We've always had the need for SSL, and our config worked without any
>> > changes
>> > when I put AJP in the mix. It doesn't, however, work with proxy http.
>> >
>> > On 3/23/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
>> >>
>> >> in my last email I forgot one
>> >>
>> >> SSLProxyMachineCertificateFile <--
>> >> SSLProxyEngine
>> >> SSLProxyMachineCertificatePath
>> >> SSLEngine
>> >> SSLProxyProtocol,
>> >> SSLProxyCipherSuite
>> >>
>> >> c. wrote:
>> >> > Filip, thanks for the info, I'll listen to anyone with good advice.
>> >> > So you
>> >> > recommend mod_proxy_http over mod_jk?
>> >> >
>> >> > Is it the same basic setup as mod_proxy_ajp? Looking at the doc (
>> >> > http://httpd.apache.org/docs/2.0/mod/mod_proxy_http.html) it
>> doesn't
>> >> give
>> >> > much info.
>> >> >
>> >> > c.
>> >> >
>> >> > On 3/23/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
>> >> >>
>> >> >> Christopher Schultz wrote:
>> >> >> > -----BEGIN PGP SIGNED MESSAGE-----
>> >> >> > Hash: SHA1
>> >> >> >
>> >> >> > Filip,
>> >> >> >
>> >> >> > Filip Hanik - Dev Lists wrote:
>> >> >> >
>> >> >> >> I'd recommend moving to mod_proxy_http, it will be easier for
>> >> you to
>> >> >> debug.
>> >> >> >>
>> >> >> >
>> >> >> > Bah! :(
>> >> >> >
>> >> >> that sounds knowledgeable :)
>> >> >> >
>> >> >> >> the error below seems to be more of a problem with apache
>> >> >> (mod_proxy_ajp)
>> >> >> >> then with tomcat, tomcat is simply trying to write a
>> message, but
>> >> the
>> >> >> >> connection is no longer valid.
>> >> >> >>
>> >> >> >
>> >> >> > The problem is that the connection has been closed at some
>> point.
>> >> It's
>> >> >> > usually because the user hit the STOP button on their browser
>> and
>> >> >> closed
>> >> >> > the connection.
>> >> >> >
>> >> >> > You can pretty much ignore these errors.
>> >> >> >
>> >> >> yes, and instead filling up the logs
>> >> >> > No need to switch connectors.
>> >> >> >
>> >> >> actually, if you are gonna use AJP, use mod_jk, mod_proxy_ajp
>> is not
>> >> >> moving in the same pace.
>> >> >> however, I'd recommend using HTTP, the HTTP connectors on
>> tomcat are
>> >> >> finely tuned,
>> >> >> if there ever is a problem in the communication, you'll just
>> put in
>> a
>> >> >> sniffer and can see it direct.
>> >> >>
>> >> >> but hey, don't listen to me :)
>> >> >> Filip
>> >> >> > - -chris
>> >> >> >
>> >> >> > -----BEGIN PGP SIGNATURE-----
>> >> >> > Version: GnuPG v1.4.7 (MingW32)
>> >> >> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>> >> >> >
>> >> >> > iD8DBQFGBA1E9CaO5/Lv0PARAqGMAJ90+P79Kt1Vhhm+a+aeNvdupzhJ4QCcDhzn
>> >> >> > 58umlhiChNndLXSputpG5rk=
>> >> >> > =IxYN
>> >> >> > -----END PGP SIGNATURE-----
>> >> >> >
>> >> >> >
>> >> ---------------------------------------------------------------------
>> >> >> > To start a new topic, e-mail: users@tomcat.apache.org
>> >> >> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> >> >> > For additional commands, e-mail: users-help@tomcat.apache.org
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> ---------------------------------------------------------------------
>> >> >> To start a new topic, e-mail: users@tomcat.apache.org
>> >> >> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> >> >> For additional commands, e-mail: users-help@tomcat.apache.org
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> ------------------------------------------------------------------------
>> >> >
>> >> > No virus found in this incoming message.
>> >> > Checked by AVG Free Edition.
>> >> > Version: 7.5.446 / Virus Database: 268.18.17/730 - Release Date:
>> >> 3/22/2007 7:44 AM
>> >> >
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To start a new topic, e-mail: users@tomcat.apache.org
>> >> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> >> For additional commands, e-mail: users-help@tomcat.apache.org
>> >>
>> >>
>> >
>> >
>> ------------------------------------------------------------------------
>> >
>> > No virus found in this incoming message.
>> > Checked by AVG Free Edition.
>> > Version: 7.5.446 / Virus Database: 268.18.17/730 - Release Date:
>> 3/22/2007 7:44 AM
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.17/731 - Release Date: 3/23/2007 3:27 PM
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by "c." <ch...@gmail.com>.
so would it make sense to assume that since SSL worked without any extra
config changes when I added the AJP config that it should work without any
changes when using mod_proxy_http?
On 3/23/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
>
> AJP doesn't use SSL, never has, so I'm not sure what the problem would be
> the only way to get SSL between apache and tomcat, is to use mod_proxy
> Filip
>
>
> c. wrote:
> > Thanks Filip,
> >
> > We've always had the need for SSL, and our config worked without any
> > changes
> > when I put AJP in the mix. It doesn't, however, work with proxy http.
> >
> > On 3/23/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
> >>
> >> in my last email I forgot one
> >>
> >> SSLProxyMachineCertificateFile <--
> >> SSLProxyEngine
> >> SSLProxyMachineCertificatePath
> >> SSLEngine
> >> SSLProxyProtocol,
> >> SSLProxyCipherSuite
> >>
> >> c. wrote:
> >> > Filip, thanks for the info, I'll listen to anyone with good advice.
> >> > So you
> >> > recommend mod_proxy_http over mod_jk?
> >> >
> >> > Is it the same basic setup as mod_proxy_ajp? Looking at the doc (
> >> > http://httpd.apache.org/docs/2.0/mod/mod_proxy_http.html) it doesn't
> >> give
> >> > much info.
> >> >
> >> > c.
> >> >
> >> > On 3/23/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
> >> >>
> >> >> Christopher Schultz wrote:
> >> >> > -----BEGIN PGP SIGNED MESSAGE-----
> >> >> > Hash: SHA1
> >> >> >
> >> >> > Filip,
> >> >> >
> >> >> > Filip Hanik - Dev Lists wrote:
> >> >> >
> >> >> >> I'd recommend moving to mod_proxy_http, it will be easier for
> >> you to
> >> >> debug.
> >> >> >>
> >> >> >
> >> >> > Bah! :(
> >> >> >
> >> >> that sounds knowledgeable :)
> >> >> >
> >> >> >> the error below seems to be more of a problem with apache
> >> >> (mod_proxy_ajp)
> >> >> >> then with tomcat, tomcat is simply trying to write a message, but
> >> the
> >> >> >> connection is no longer valid.
> >> >> >>
> >> >> >
> >> >> > The problem is that the connection has been closed at some point.
> >> It's
> >> >> > usually because the user hit the STOP button on their browser and
> >> >> closed
> >> >> > the connection.
> >> >> >
> >> >> > You can pretty much ignore these errors.
> >> >> >
> >> >> yes, and instead filling up the logs
> >> >> > No need to switch connectors.
> >> >> >
> >> >> actually, if you are gonna use AJP, use mod_jk, mod_proxy_ajp is not
> >> >> moving in the same pace.
> >> >> however, I'd recommend using HTTP, the HTTP connectors on tomcat are
> >> >> finely tuned,
> >> >> if there ever is a problem in the communication, you'll just put in
> a
> >> >> sniffer and can see it direct.
> >> >>
> >> >> but hey, don't listen to me :)
> >> >> Filip
> >> >> > - -chris
> >> >> >
> >> >> > -----BEGIN PGP SIGNATURE-----
> >> >> > Version: GnuPG v1.4.7 (MingW32)
> >> >> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> >> >> >
> >> >> > iD8DBQFGBA1E9CaO5/Lv0PARAqGMAJ90+P79Kt1Vhhm+a+aeNvdupzhJ4QCcDhzn
> >> >> > 58umlhiChNndLXSputpG5rk=
> >> >> > =IxYN
> >> >> > -----END PGP SIGNATURE-----
> >> >> >
> >> >> >
> >> ---------------------------------------------------------------------
> >> >> > To start a new topic, e-mail: users@tomcat.apache.org
> >> >> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> >> >> > For additional commands, e-mail: users-help@tomcat.apache.org
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >>
> ---------------------------------------------------------------------
> >> >> To start a new topic, e-mail: users@tomcat.apache.org
> >> >> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> >> >> For additional commands, e-mail: users-help@tomcat.apache.org
> >> >>
> >> >>
> >> >
> >> >
> >>
> ------------------------------------------------------------------------
> >> >
> >> > No virus found in this incoming message.
> >> > Checked by AVG Free Edition.
> >> > Version: 7.5.446 / Virus Database: 268.18.17/730 - Release Date:
> >> 3/22/2007 7:44 AM
> >> >
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To start a new topic, e-mail: users@tomcat.apache.org
> >> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> >> For additional commands, e-mail: users-help@tomcat.apache.org
> >>
> >>
> >
> > ------------------------------------------------------------------------
> >
> > No virus found in this incoming message.
> > Checked by AVG Free Edition.
> > Version: 7.5.446 / Virus Database: 268.18.17/730 - Release Date:
> 3/22/2007 7:44 AM
> >
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
AJP doesn't use SSL, never has, so I'm not sure what the problem would be
the only way to get SSL between apache and tomcat, is to use mod_proxy
Filip
c. wrote:
> Thanks Filip,
>
> We've always had the need for SSL, and our config worked without any
> changes
> when I put AJP in the mix. It doesn't, however, work with proxy http.
>
> On 3/23/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
>>
>> in my last email I forgot one
>>
>> SSLProxyMachineCertificateFile <--
>> SSLProxyEngine
>> SSLProxyMachineCertificatePath
>> SSLEngine
>> SSLProxyProtocol,
>> SSLProxyCipherSuite
>>
>> c. wrote:
>> > Filip, thanks for the info, I'll listen to anyone with good advice.
>> > So you
>> > recommend mod_proxy_http over mod_jk?
>> >
>> > Is it the same basic setup as mod_proxy_ajp? Looking at the doc (
>> > http://httpd.apache.org/docs/2.0/mod/mod_proxy_http.html) it doesn't
>> give
>> > much info.
>> >
>> > c.
>> >
>> > On 3/23/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
>> >>
>> >> Christopher Schultz wrote:
>> >> > -----BEGIN PGP SIGNED MESSAGE-----
>> >> > Hash: SHA1
>> >> >
>> >> > Filip,
>> >> >
>> >> > Filip Hanik - Dev Lists wrote:
>> >> >
>> >> >> I'd recommend moving to mod_proxy_http, it will be easier for
>> you to
>> >> debug.
>> >> >>
>> >> >
>> >> > Bah! :(
>> >> >
>> >> that sounds knowledgeable :)
>> >> >
>> >> >> the error below seems to be more of a problem with apache
>> >> (mod_proxy_ajp)
>> >> >> then with tomcat, tomcat is simply trying to write a message, but
>> the
>> >> >> connection is no longer valid.
>> >> >>
>> >> >
>> >> > The problem is that the connection has been closed at some point.
>> It's
>> >> > usually because the user hit the STOP button on their browser and
>> >> closed
>> >> > the connection.
>> >> >
>> >> > You can pretty much ignore these errors.
>> >> >
>> >> yes, and instead filling up the logs
>> >> > No need to switch connectors.
>> >> >
>> >> actually, if you are gonna use AJP, use mod_jk, mod_proxy_ajp is not
>> >> moving in the same pace.
>> >> however, I'd recommend using HTTP, the HTTP connectors on tomcat are
>> >> finely tuned,
>> >> if there ever is a problem in the communication, you'll just put in a
>> >> sniffer and can see it direct.
>> >>
>> >> but hey, don't listen to me :)
>> >> Filip
>> >> > - -chris
>> >> >
>> >> > -----BEGIN PGP SIGNATURE-----
>> >> > Version: GnuPG v1.4.7 (MingW32)
>> >> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>> >> >
>> >> > iD8DBQFGBA1E9CaO5/Lv0PARAqGMAJ90+P79Kt1Vhhm+a+aeNvdupzhJ4QCcDhzn
>> >> > 58umlhiChNndLXSputpG5rk=
>> >> > =IxYN
>> >> > -----END PGP SIGNATURE-----
>> >> >
>> >> >
>> ---------------------------------------------------------------------
>> >> > To start a new topic, e-mail: users@tomcat.apache.org
>> >> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> >> > For additional commands, e-mail: users-help@tomcat.apache.org
>> >> >
>> >> >
>> >> >
>> >> >
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To start a new topic, e-mail: users@tomcat.apache.org
>> >> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> >> For additional commands, e-mail: users-help@tomcat.apache.org
>> >>
>> >>
>> >
>> >
>> ------------------------------------------------------------------------
>> >
>> > No virus found in this incoming message.
>> > Checked by AVG Free Edition.
>> > Version: 7.5.446 / Virus Database: 268.18.17/730 - Release Date:
>> 3/22/2007 7:44 AM
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.17/730 - Release Date: 3/22/2007 7:44 AM
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by "c." <ch...@gmail.com>.
Thanks Filip,
We've always had the need for SSL, and our config worked without any changes
when I put AJP in the mix. It doesn't, however, work with proxy http.
On 3/23/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
>
> in my last email I forgot one
>
> SSLProxyMachineCertificateFile <--
> SSLProxyEngine
> SSLProxyMachineCertificatePath
> SSLEngine
> SSLProxyProtocol,
> SSLProxyCipherSuite
>
> c. wrote:
> > Filip, thanks for the info, I'll listen to anyone with good advice.
> > So you
> > recommend mod_proxy_http over mod_jk?
> >
> > Is it the same basic setup as mod_proxy_ajp? Looking at the doc (
> > http://httpd.apache.org/docs/2.0/mod/mod_proxy_http.html) it doesn't
> give
> > much info.
> >
> > c.
> >
> > On 3/23/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
> >>
> >> Christopher Schultz wrote:
> >> > -----BEGIN PGP SIGNED MESSAGE-----
> >> > Hash: SHA1
> >> >
> >> > Filip,
> >> >
> >> > Filip Hanik - Dev Lists wrote:
> >> >
> >> >> I'd recommend moving to mod_proxy_http, it will be easier for you to
> >> debug.
> >> >>
> >> >
> >> > Bah! :(
> >> >
> >> that sounds knowledgeable :)
> >> >
> >> >> the error below seems to be more of a problem with apache
> >> (mod_proxy_ajp)
> >> >> then with tomcat, tomcat is simply trying to write a message, but
> the
> >> >> connection is no longer valid.
> >> >>
> >> >
> >> > The problem is that the connection has been closed at some point.
> It's
> >> > usually because the user hit the STOP button on their browser and
> >> closed
> >> > the connection.
> >> >
> >> > You can pretty much ignore these errors.
> >> >
> >> yes, and instead filling up the logs
> >> > No need to switch connectors.
> >> >
> >> actually, if you are gonna use AJP, use mod_jk, mod_proxy_ajp is not
> >> moving in the same pace.
> >> however, I'd recommend using HTTP, the HTTP connectors on tomcat are
> >> finely tuned,
> >> if there ever is a problem in the communication, you'll just put in a
> >> sniffer and can see it direct.
> >>
> >> but hey, don't listen to me :)
> >> Filip
> >> > - -chris
> >> >
> >> > -----BEGIN PGP SIGNATURE-----
> >> > Version: GnuPG v1.4.7 (MingW32)
> >> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> >> >
> >> > iD8DBQFGBA1E9CaO5/Lv0PARAqGMAJ90+P79Kt1Vhhm+a+aeNvdupzhJ4QCcDhzn
> >> > 58umlhiChNndLXSputpG5rk=
> >> > =IxYN
> >> > -----END PGP SIGNATURE-----
> >> >
> >> > ---------------------------------------------------------------------
> >> > To start a new topic, e-mail: users@tomcat.apache.org
> >> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> >> > For additional commands, e-mail: users-help@tomcat.apache.org
> >> >
> >> >
> >> >
> >> >
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To start a new topic, e-mail: users@tomcat.apache.org
> >> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> >> For additional commands, e-mail: users-help@tomcat.apache.org
> >>
> >>
> >
> > ------------------------------------------------------------------------
> >
> > No virus found in this incoming message.
> > Checked by AVG Free Edition.
> > Version: 7.5.446 / Virus Database: 268.18.17/730 - Release Date:
> 3/22/2007 7:44 AM
> >
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
in my last email I forgot one
SSLProxyMachineCertificateFile <--
SSLProxyEngine
SSLProxyMachineCertificatePath
SSLEngine
SSLProxyProtocol,
SSLProxyCipherSuite
c. wrote:
> Filip, thanks for the info, I'll listen to anyone with good advice.
> So you
> recommend mod_proxy_http over mod_jk?
>
> Is it the same basic setup as mod_proxy_ajp? Looking at the doc (
> http://httpd.apache.org/docs/2.0/mod/mod_proxy_http.html) it doesn't give
> much info.
>
> c.
>
> On 3/23/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
>>
>> Christopher Schultz wrote:
>> > -----BEGIN PGP SIGNED MESSAGE-----
>> > Hash: SHA1
>> >
>> > Filip,
>> >
>> > Filip Hanik - Dev Lists wrote:
>> >
>> >> I'd recommend moving to mod_proxy_http, it will be easier for you to
>> debug.
>> >>
>> >
>> > Bah! :(
>> >
>> that sounds knowledgeable :)
>> >
>> >> the error below seems to be more of a problem with apache
>> (mod_proxy_ajp)
>> >> then with tomcat, tomcat is simply trying to write a message, but the
>> >> connection is no longer valid.
>> >>
>> >
>> > The problem is that the connection has been closed at some point. It's
>> > usually because the user hit the STOP button on their browser and
>> closed
>> > the connection.
>> >
>> > You can pretty much ignore these errors.
>> >
>> yes, and instead filling up the logs
>> > No need to switch connectors.
>> >
>> actually, if you are gonna use AJP, use mod_jk, mod_proxy_ajp is not
>> moving in the same pace.
>> however, I'd recommend using HTTP, the HTTP connectors on tomcat are
>> finely tuned,
>> if there ever is a problem in the communication, you'll just put in a
>> sniffer and can see it direct.
>>
>> but hey, don't listen to me :)
>> Filip
>> > - -chris
>> >
>> > -----BEGIN PGP SIGNATURE-----
>> > Version: GnuPG v1.4.7 (MingW32)
>> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>> >
>> > iD8DBQFGBA1E9CaO5/Lv0PARAqGMAJ90+P79Kt1Vhhm+a+aeNvdupzhJ4QCcDhzn
>> > 58umlhiChNndLXSputpG5rk=
>> > =IxYN
>> > -----END PGP SIGNATURE-----
>> >
>> > ---------------------------------------------------------------------
>> > To start a new topic, e-mail: users@tomcat.apache.org
>> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> > For additional commands, e-mail: users-help@tomcat.apache.org
>> >
>> >
>> >
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.17/730 - Release Date: 3/22/2007 7:44 AM
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
c. wrote:
> Filip, thanks for the info, I'll listen to anyone with good advice.
> So you
> recommend mod_proxy_http over mod_jk?
>
> Is it the same basic setup as mod_proxy_ajp? Looking at the doc (
> http://httpd.apache.org/docs/2.0/mod/mod_proxy_http.html) it doesn't give
> much info.
Ah, it's straight forward, although why the sudden need for SSL, AJP
doesn't support it :)
http://httpd.apache.org/docs/2.2/mod/mod_proxy.html
just set up your paths to be https:// instead of http://...
then you need to set up the certificate that mod_proxy is gonna use,
these are some, maybe not all
SSLProxyEngine
SSLProxyMachineCertificatePath
SSLEngine on
SSLProxyProtocol,
SSLProxyCipherSuite
Filip
> c.
>
> On 3/23/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
>>
>> Christopher Schultz wrote:
>> > -----BEGIN PGP SIGNED MESSAGE-----
>> > Hash: SHA1
>> >
>> > Filip,
>> >
>> > Filip Hanik - Dev Lists wrote:
>> >
>> >> I'd recommend moving to mod_proxy_http, it will be easier for you to
>> debug.
>> >>
>> >
>> > Bah! :(
>> >
>> that sounds knowledgeable :)
>> >
>> >> the error below seems to be more of a problem with apache
>> (mod_proxy_ajp)
>> >> then with tomcat, tomcat is simply trying to write a message, but the
>> >> connection is no longer valid.
>> >>
>> >
>> > The problem is that the connection has been closed at some point. It's
>> > usually because the user hit the STOP button on their browser and
>> closed
>> > the connection.
>> >
>> > You can pretty much ignore these errors.
>> >
>> yes, and instead filling up the logs
>> > No need to switch connectors.
>> >
>> actually, if you are gonna use AJP, use mod_jk, mod_proxy_ajp is not
>> moving in the same pace.
>> however, I'd recommend using HTTP, the HTTP connectors on tomcat are
>> finely tuned,
>> if there ever is a problem in the communication, you'll just put in a
>> sniffer and can see it direct.
>>
>> but hey, don't listen to me :)
>> Filip
>> > - -chris
>> >
>> > -----BEGIN PGP SIGNATURE-----
>> > Version: GnuPG v1.4.7 (MingW32)
>> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>> >
>> > iD8DBQFGBA1E9CaO5/Lv0PARAqGMAJ90+P79Kt1Vhhm+a+aeNvdupzhJ4QCcDhzn
>> > 58umlhiChNndLXSputpG5rk=
>> > =IxYN
>> > -----END PGP SIGNATURE-----
>> >
>> > ---------------------------------------------------------------------
>> > To start a new topic, e-mail: users@tomcat.apache.org
>> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> > For additional commands, e-mail: users-help@tomcat.apache.org
>> >
>> >
>> >
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.17/730 - Release Date: 3/22/2007 7:44 AM
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by "c." <ch...@gmail.com>.
Filip, thanks for the info, I'll listen to anyone with good advice. So you
recommend mod_proxy_http over mod_jk?
Is it the same basic setup as mod_proxy_ajp? Looking at the doc (
http://httpd.apache.org/docs/2.0/mod/mod_proxy_http.html) it doesn't give
much info.
c.
On 3/23/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
>
> Christopher Schultz wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Filip,
> >
> > Filip Hanik - Dev Lists wrote:
> >
> >> I'd recommend moving to mod_proxy_http, it will be easier for you to
> debug.
> >>
> >
> > Bah! :(
> >
> that sounds knowledgeable :)
> >
> >> the error below seems to be more of a problem with apache
> (mod_proxy_ajp)
> >> then with tomcat, tomcat is simply trying to write a message, but the
> >> connection is no longer valid.
> >>
> >
> > The problem is that the connection has been closed at some point. It's
> > usually because the user hit the STOP button on their browser and closed
> > the connection.
> >
> > You can pretty much ignore these errors.
> >
> yes, and instead filling up the logs
> > No need to switch connectors.
> >
> actually, if you are gonna use AJP, use mod_jk, mod_proxy_ajp is not
> moving in the same pace.
> however, I'd recommend using HTTP, the HTTP connectors on tomcat are
> finely tuned,
> if there ever is a problem in the communication, you'll just put in a
> sniffer and can see it direct.
>
> but hey, don't listen to me :)
> Filip
> > - -chris
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.7 (MingW32)
> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> >
> > iD8DBQFGBA1E9CaO5/Lv0PARAqGMAJ90+P79Kt1Vhhm+a+aeNvdupzhJ4QCcDhzn
> > 58umlhiChNndLXSputpG5rk=
> > =IxYN
> > -----END PGP SIGNATURE-----
> >
> > ---------------------------------------------------------------------
> > To start a new topic, e-mail: users@tomcat.apache.org
> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: users-help@tomcat.apache.org
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
Christopher Schultz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Filip,
>
> Filip Hanik - Dev Lists wrote:
>
>> I'd recommend moving to mod_proxy_http, it will be easier for you to debug.
>>
>
> Bah! :(
>
that sounds knowledgeable :)
>
>> the error below seems to be more of a problem with apache (mod_proxy_ajp)
>> then with tomcat, tomcat is simply trying to write a message, but the
>> connection is no longer valid.
>>
>
> The problem is that the connection has been closed at some point. It's
> usually because the user hit the STOP button on their browser and closed
> the connection.
>
> You can pretty much ignore these errors.
>
yes, and instead filling up the logs
> No need to switch connectors.
>
actually, if you are gonna use AJP, use mod_jk, mod_proxy_ajp is not
moving in the same pace.
however, I'd recommend using HTTP, the HTTP connectors on tomcat are
finely tuned,
if there ever is a problem in the communication, you'll just put in a
sniffer and can see it direct.
but hey, don't listen to me :)
Filip
> - -chris
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFGBA1E9CaO5/Lv0PARAqGMAJ90+P79Kt1Vhhm+a+aeNvdupzhJ4QCcDhzn
> 58umlhiChNndLXSputpG5rk=
> =IxYN
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Filip,
Filip Hanik - Dev Lists wrote:
> I'd recommend moving to mod_proxy_http, it will be easier for you to debug.
Bah! :(
> the error below seems to be more of a problem with apache (mod_proxy_ajp)
> then with tomcat, tomcat is simply trying to write a message, but the
> connection is no longer valid.
The problem is that the connection has been closed at some point. It's
usually because the user hit the STOP button on their browser and closed
the connection.
You can pretty much ignore these errors.
No need to switch connectors.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGBA1E9CaO5/Lv0PARAqGMAJ90+P79Kt1Vhhm+a+aeNvdupzhJ4QCcDhzn
58umlhiChNndLXSputpG5rk=
=IxYN
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
I'd recommend moving to mod_proxy_http, it will be easier for you to debug.
the error below seems tobe more of a problem with apache (mod_proxy_ajp)
then with tomcat, tomcat is simply trying to write a message, but the
connection is no longer valid.
Filip
c. wrote:
> Hello,
>
> I'm using mod_proxy_ajp as my link b/w tomcat and apache. Things are
> working well with the exception of getting the following error:
>
> 2007-03-22 20:02:42,875 [TP-Processor51] WARN
> org.apache.jk.core.MsgContext - Error sending end packet
> java.net.SocketException: Broken pipe
> at java.net.SocketOutputStream.socketWrite0(Native Method)
> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
> at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
> at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518)
> at
> org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:112)
> at org.apache.jk.core.MsgContext.action(MsgContext.java:293)
> at org.apache.coyote.Response.action(Response.java:182)
> at org.apache.coyote.Response.finish(Response.java:304)
> at
> org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:204)
> at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
> at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754)
> at org.apache.jk.common.ChannelSocket.processConnection(
> ChannelSocket.java:684)
> at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(
> ChannelSocket.java:876)
> at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(
> ThreadPool.java:684)
> at java.lang.Thread.run(Thread.java:595)
> 2007-03-22 20:02:42,875 [TP-Processor51] WARN
> org.apache.jk.common.ChannelSocket - processCallbacks status 2
>
> a few times a day.
>
> This is from a medium traffic e-commerce site (approx. 1000 trans a
> day) and
> it seems to occur when the user is on the secure checkout page and
> hits the
> order button. They complain of being presented with a blank page after
> hitting the purchase button.
>
> Pertinent details from the servlet.xml:
>
> <Connector address="139.0.0.1"
> port="8009"
> enableLookups="false"
> protocol="AJP/1.3"
> minSpareThreads="20"
> maxSpareThreads="200"
> maxThreads="1024"
> connectionTimeout="600000"
> />
>
> Any ideas as to why this is happening?
>
> Thanks,
>
> Chris.
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by "c." <ch...@gmail.com>.
On top of the previous error in the log tomcat log file, the following error
shows up in the httpd error log:
[Thu Mar 22 19:55:23 2007] [error] (70007)The timeout specified has expired:
ajp_ilink_receive() can't receive header
[Thu Mar 22 19:55:23 2007] [error] ajp_read_header: ajp_ilink_receive failed
[Thu Mar 22 19:55:23 2007] [error] (120006)APR does not understand this
error code: proxy: read response failed from 139.0.0.1:8009 (139.0.0.1)
On 3/23/07, c. <ch...@gmail.com> wrote:
>
> Looking at the server.xml connectionTimeout, I've set the value to 600000,
> 600 seconds not 60 seconds, could I be holding onto the connection for too
> long? The reason I'm asking is 'cause I don't think adding another five
> seconds to the 600 will make a difference, adding five seconds to 60 could
> be relevant.
>
> chris.
>
> On 3/23/07, c. <ch...@gmail.com> wrote:
> >
> > I'll try upping the connection timeouts, but aside from the problem of
> > dropped connections what I'm really confused about is why there is a jk
> > exception (org.apache.jk.common.ChannelSo
> > >
> > > cket.send(ChannelSocket.java:518)) when I'm using mod_proxy_ajp, NOT
> > > mod_jk.
> >
> >
> >
> > Chris.
> >
> >
> >
> > On 3/23/07, Christopher Schultz <ch...@christopherschultz.net> wrote:
> > >
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > Martin,
> > >
> > > Martin Gainty wrote:
> > > > broken pipe means that at one end (more than likely the DB listener
> > > you're connecting to somehow dropped)
> > >
> > > Unlikely:
> > >
> > > >> java.net.SocketException: Broken pipe
> > > >> at java.net.SocketOutputStream.socketWrite0(Native Method)
> > > >> at java.net.SocketOutputStream.socketWrite(
> > > SocketOutputStream.java:92)
> > > >> at java.net.SocketOutputStream.write(SocketOutputStream.java
> > > :136)
> > > >> at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java
> > > :518)
> > >
> > > Looks like the JK connector to me, not some database connection.
> > >
> > > > A quick fix is to bump the connectionTimeout up by 5 sec
> > > > If not bump the mod_proxy.proxytimeout up by 5 secs
> > > > http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxytimeout
> > >
> > > Note that the OP was asking about mod_jk, and you are suggesting a fix
> > > for mod_proxy_ajp :(
> > >
> > > - -chris
> > >
> > > -----BEGIN PGP SIGNATURE-----
> > > Version: GnuPG v1.4.7 (MingW32)
> > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> > >
> > > iD8DBQFGBA2W9CaO5/Lv0PARApNPAKCMQVsbqgUN0cr7Ln3hLBv2jkriPgCggr3e
> > > i7V9vlv9xaAWtA1bl7PH3fo=
> > > =7dhr
> > > -----END PGP SIGNATURE-----
> > >
> > > ---------------------------------------------------------------------
> > > To start a new topic, e-mail: users@tomcat.apache.org
> > > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> > > For additional commands, e-mail: users-help@tomcat.apache.org
> > >
> > >
> >
>
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by "c." <ch...@gmail.com>.
Looking at the server.xml connectionTimeout, I've set the value to 600000,
600 seconds not 60 seconds, could I be holding onto the connection for too
long? The reason I'm asking is 'cause I don't think adding another five
seconds to the 600 will make a difference, adding five seconds to 60 could
be relevant.
chris.
On 3/23/07, c. <ch...@gmail.com> wrote:
>
> I'll try upping the connection timeouts, but aside from the problem of
> dropped connections what I'm really confused about is why there is a jk
> exception (org.apache.jk.common.ChannelSo
> >
> > cket.send(ChannelSocket.java:518)) when I'm using mod_proxy_ajp, NOT
> > mod_jk.
>
>
>
> Chris.
>
>
>
> On 3/23/07, Christopher Schultz <ch...@christopherschultz.net> wrote:
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Martin,
> >
> > Martin Gainty wrote:
> > > broken pipe means that at one end (more than likely the DB listener
> > you're connecting to somehow dropped)
> >
> > Unlikely:
> >
> > >> java.net.SocketException: Broken pipe
> > >> at java.net.SocketOutputStream.socketWrite0(Native Method)
> > >> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java
> > :92)
> > >> at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
> > >> at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518)
> >
> > Looks like the JK connector to me, not some database connection.
> >
> > > A quick fix is to bump the connectionTimeout up by 5 sec
> > > If not bump the mod_proxy.proxytimeout up by 5 secs
> > > http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxytimeout
> >
> > Note that the OP was asking about mod_jk, and you are suggesting a fix
> > for mod_proxy_ajp :(
> >
> > - -chris
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.7 (MingW32)
> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> >
> > iD8DBQFGBA2W9CaO5/Lv0PARApNPAKCMQVsbqgUN0cr7Ln3hLBv2jkriPgCggr3e
> > i7V9vlv9xaAWtA1bl7PH3fo=
> > =7dhr
> > -----END PGP SIGNATURE-----
> >
> > ---------------------------------------------------------------------
> > To start a new topic, e-mail: users@tomcat.apache.org
> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: users-help@tomcat.apache.org
> >
> >
>
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by Rainer Jung <ra...@kippdata.de>.
As a first approximation this is true. But ProxyPassReverse does not
rewrite the body of responses. So if there is a wrong URL in the body,
then this will not be fixed by ProxyPassReverse. It is mostly (or only?)
for fixing the Location header in http redirects.
Regards,
Rainer
Erik Melkersson wrote:
>> and while we're on the subject, what's the difference b/w proxyPass and
>> ProxyPassReverse in laymens terms?
>
> I think thats a question for the Apache-web server mailinglist but...
>
> ProxyPass "forwards" the request from the user to another web server
> ProxyPassReverse "rewrites" the response from the other server before it
> comes to the user. (domain names in redirect-headers etc)
>
> /Erik Melkersson
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by Erik Melkersson <er...@liu.se>.
> and while we're on the subject, what's the difference b/w proxyPass and
> ProxyPassReverse in laymens terms?
I think thats a question for the Apache-web server mailinglist but...
ProxyPass "forwards" the request from the user to another web server
ProxyPassReverse "rewrites" the response from the other server before it
comes to the user. (domain names in redirect-headers etc)
/Erik Melkersson
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by "c." <ch...@gmail.com>.
no worries, mistakes happen.
Thanks for the clarification on the jk exceptions. Now that you've said it
it seems obvious.
I can get mod_proxy_http to work unsecurely, but once I hit the secure pages
I get internal server error. Why would I not have had to do anything to
enable ssl with mod_proxy_ajp?
and while we're on the subject, what's the difference b/w proxyPass and
ProxyPassReverse in laymens terms?
thanks,
c.
On 3/23/07, Christopher Schultz <ch...@christopherschultz.net> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> All,
>
> Apologies to all. I read mod_proxy_http as mod_proxy_ajp, and made a
> fool of myself. Duh.
>
> - -chris
>
> Christopher Schultz wrote:
> > Chris,
> >
> > c. wrote:
> >> I'll try upping the connection timeouts, but aside from the problem
> >> of dropped connections what I'm really confused about is why there is
> >> a jk exception
> >> (org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518))
> >> when I'm using mod_proxy_ajp, NOT mod_jk.
> >
> > You aren't using mod_jk, but you are still using the JK connector (which
> > implements ajp13) rather than something like the HTTP connector.
> >
> > Whether you use mod_jk or mod_proxy_ajp, you are still using the Jk
> > connector on the Tomcat side.
> >
> > -chris
> >
>
> - ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFGBEcU9CaO5/Lv0PARAo38AJ9fXyeZrcXzs2sBZ/j9XYOfFWd+7ACdFoeE
> FFTdXbES2zNsvwXw5UH0hjE=
> =bXy7
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
All,
Apologies to all. I read mod_proxy_http as mod_proxy_ajp, and made a
fool of myself. Duh.
- -chris
Christopher Schultz wrote:
> Chris,
>
> c. wrote:
>> I'll try upping the connection timeouts, but aside from the problem
>> of dropped connections what I'm really confused about is why there is
>> a jk exception
>> (org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518))
>> when I'm using mod_proxy_ajp, NOT mod_jk.
>
> You aren't using mod_jk, but you are still using the JK connector (which
> implements ajp13) rather than something like the HTTP connector.
>
> Whether you use mod_jk or mod_proxy_ajp, you are still using the Jk
> connector on the Tomcat side.
>
> -chris
>
- ---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGBEcU9CaO5/Lv0PARAo38AJ9fXyeZrcXzs2sBZ/j9XYOfFWd+7ACdFoeE
FFTdXbES2zNsvwXw5UH0hjE=
=bXy7
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chris,
c. wrote:
> I'll try upping the connection timeouts, but aside from the problem
> of dropped connections what I'm really confused about is why there is
> a jk exception
> (org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518))
> when I'm using mod_proxy_ajp, NOT mod_jk.
You aren't using mod_jk, but you are still using the JK connector (which
implements ajp13) rather than something like the HTTP connector.
Whether you use mod_jk or mod_proxy_ajp, you are still using the Jk
connector on the Tomcat side.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGBEWN9CaO5/Lv0PARAq2yAKCzhjjA/X6+3Bz12ULRo6oG4d7mAwCeLljZ
mSNMzq2NM09N6D/4RwVtpFM=
=XKbi
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by "c." <ch...@gmail.com>.
I'll try upping the connection timeouts, but aside from the problem of
dropped connections what I'm really confused about is why there is a jk
exception (org.apache.jk.common.ChannelSo
>
> cket.send(ChannelSocket.java:518)) when I'm using mod_proxy_ajp, NOT
> mod_jk.
Chris.
On 3/23/07, Christopher Schultz <ch...@christopherschultz.net> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Martin,
>
> Martin Gainty wrote:
> > broken pipe means that at one end (more than likely the DB listener
> you're connecting to somehow dropped)
>
> Unlikely:
>
> >> java.net.SocketException: Broken pipe
> >> at java.net.SocketOutputStream.socketWrite0(Native Method)
> >> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java
> :92)
> >> at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
> >> at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518)
>
> Looks like the JK connector to me, not some database connection.
>
> > A quick fix is to bump the connectionTimeout up by 5 sec
> > If not bump the mod_proxy.proxytimeout up by 5 secs
> > http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxytimeout
>
> Note that the OP was asking about mod_jk, and you are suggesting a fix
> for mod_proxy_ajp :(
>
> - -chris
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFGBA2W9CaO5/Lv0PARApNPAKCMQVsbqgUN0cr7Ln3hLBv2jkriPgCggr3e
> i7V9vlv9xaAWtA1bl7PH3fo=
> =7dhr
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martin,
Martin Gainty wrote:
> broken pipe means that at one end (more than likely the DB listener you're connecting to somehow dropped)
Unlikely:
>> java.net.SocketException: Broken pipe
>> at java.net.SocketOutputStream.socketWrite0(Native Method)
>> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
>> at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
>> at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518)
Looks like the JK connector to me, not some database connection.
> A quick fix is to bump the connectionTimeout up by 5 sec
> If not bump the mod_proxy.proxytimeout up by 5 secs
> http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxytimeout
Note that the OP was asking about mod_jk, and you are suggesting a fix
for mod_proxy_ajp :(
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGBA2W9CaO5/Lv0PARApNPAKCMQVsbqgUN0cr7Ln3hLBv2jkriPgCggr3e
i7V9vlv9xaAWtA1bl7PH3fo=
=7dhr
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat mod_proxy_ajp and jk exceptions
Posted by Martin Gainty <mg...@hotmail.com>.
Chris-
broken pipe means that at one end (more than likely the DB listener you're connecting to somehow dropped)
A quick fix is to bump the connectionTimeout up by 5 sec
If not bump the mod_proxy.proxytimeout up by 5 secs
http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxytimeout
Martin-
---------------------------------------------------------------------------
This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited.
---------------------------------------------------------------------------
Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire.
----- Original Message -----
From: "c." <ch...@gmail.com>
To: <us...@tomcat.apache.org>
Sent: Friday, March 23, 2007 12:47 PM
Subject: Tomcat mod_proxy_ajp and jk exceptions
> Hello,
>
> I'm using mod_proxy_ajp as my link b/w tomcat and apache. Things are
> working well with the exception of getting the following error:
>
> 2007-03-22 20:02:42,875 [TP-Processor51] WARN
> org.apache.jk.core.MsgContext - Error sending end packet
> java.net.SocketException: Broken pipe
> at java.net.SocketOutputStream.socketWrite0(Native Method)
> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
> at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
> at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518)
> at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:112)
> at org.apache.jk.core.MsgContext.action(MsgContext.java:293)
> at org.apache.coyote.Response.action(Response.java:182)
> at org.apache.coyote.Response.finish(Response.java:304)
> at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:204)
> at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
> at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754)
> at org.apache.jk.common.ChannelSocket.processConnection(
> ChannelSocket.java:684)
> at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(
> ChannelSocket.java:876)
> at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(
> ThreadPool.java:684)
> at java.lang.Thread.run(Thread.java:595)
> 2007-03-22 20:02:42,875 [TP-Processor51] WARN
> org.apache.jk.common.ChannelSocket - processCallbacks status 2
>
> a few times a day.
>
> This is from a medium traffic e-commerce site (approx. 1000 trans a day) and
> it seems to occur when the user is on the secure checkout page and hits the
> order button. They complain of being presented with a blank page after
> hitting the purchase button.
>
> Pertinent details from the servlet.xml:
>
> <Connector address="139.0.0.1"
> port="8009"
> enableLookups="false"
> protocol="AJP/1.3"
> minSpareThreads="20"
> maxSpareThreads="200"
> maxThreads="1024"
> connectionTimeout="600000"
> />
>
> Any ideas as to why this is happening?
>
> Thanks,
>
> Chris.
>