Larry,
When Access Apache content everything works fine. Also when access
the examples directly through tomcat's http server (the embedded one)
everything works fine. It is only going through the mod_jk that croaks.
That is why I leaning towards some configuration with mod_jk or something.
but everything else works fine.
We're not crazy or anything, the does work on other people machine
right? mod_jk on AIX ?
Thanks Again,
Jay
Larry Isaacs
<Larry.Isaacs@ To: 'Tomcat Users List'
<[EMAIL PROTECTED]>
sas.com> cc:
Subject: RE: Tomcat 3.3a and mod_jk on
AIX 4.3.3 built OK, but not sending requests
03/29/2002
10:15 AM
Please respond
to "Tomcat
Users List"
Jay,
What happens if you try to access Apache content, such as
with just http://host:8080/? Does Apache successfully serve
content, or does these requests hang too?
Larry
> -----Original Message-----
> From: Jay Balunas [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 29, 2002 10:01 AM
> To: Tomcat Users List
> Subject: RE: Tomcat 3.3a and mod_jk on AIX 4.3.3 built OK,
> but not sending requests
>
>
>
> Larry,
>
> Thanks for the info on the ajp12.id file. We may have
> started tomcat
> twice or something. We'll keep an eye out for that.
>
> The Tomcat log shows this at the end of the log after
> initialization.
> that looks good compared to other OSes that we have this running on.
>
> 2002-03-29 08:59:54 - Http10Interceptor: Starting on 8081
> 2002-03-29 08:59:54 - Ajp12Interceptor: Starting on 8007
> 2002-03-29 08:59:55 - Ajp13Interceptor: Starting on 8009
>
> The test request we are trying is the tomcat Examples so
> "http://host:8080/examples"; Where 8080 is the port apache is
> on. All
> that happens on the AIX box when we do this is the browser
> hangs, waiting
> for a response.
>
> On one of the Solaris boxes I turned the log level up to
> "debug" on
> mod_jk, and saw all alot more information from where the AIX
> box mod_jk log
> stopped. I also saw it checking all of the requests like you
> said , it is
> actually pretty cool. So here it what I think we are
> missing in the AIX
> mod_jk log that is showing up on the Solaris box.
>
> [Fri Mar 29 09:44:23 2002] [jk_uri_worker_map.c (368)]:
> Attempting to
> map URI '/examples/'
> [Fri Mar 29 09:44:23 2002] [jk_uri_worker_map.c (391)]:
> jk_uri_worker_map_t::map_uri_to_worker, Found a context match ajp13 ->
> /examples/
> [Fri Mar 29 09:44:23 2002] [jk_worker.c (123)]: Into
> wc_get_worker_for_name ajp13
> [Fri Mar 29 09:44:23 2002] [jk_worker.c (127)]:
> wc_get_worker_for_name, done found a worker
> [Fri Mar 29 09:44:23 2002] [jk_ajp13_worker.c (865)]: Into
> jk_worker_t::get_endpoint
> [Fri Mar 29 09:44:23 2002] [jk_ajp13_worker.c (775)]: Into
> jk_endpoint_t::service
> [Fri Mar 29 09:44:23 2002] [jk_ajp13.c (403)]: Into
> ajp13_marshal_into_msgb
> [Fri Mar 29 09:44:23 2002] [jk_ajp13.c (537)]:
> ajp13_marshal_into_msgb - Done
> [Fri Mar 29 09:44:23 2002] [jk_ajp13_worker.c (206)]: sending to
> ajp13 #190
> [Fri Mar 29 09:44:23 2002] [jk_ajp13_worker.c (645)]:
> send_request 2:
> request body to send 0 - request body to resend 0
> [Fri Mar 29 09:44:23 2002] [jk_ajp13_worker.c (258)]:
> received from
> ajp13 #28
> [Fri Mar 29 09:44:23 2002] [jk_ajp13.c (584)]:
> ajp13_unmarshal_response: status = 200
> [Fri Mar 29 09:44:23 2002] [jk_ajp13.c (591)]:
> ajp13_unmarshal_response: Number of headers is = 1
> [Fri Mar 29 09:44:23 2002] [jk_ajp13.c (634)]:
> ajp13_unmarshal_response: Header[0] [Content-Type] = [text/html]
> [Fri Mar 29 09:44:23 2002] [jk_ajp13_worker.c (258)]:
> received from
> ajp13 #1276
> [Fri Mar 29 09:44:23 2002] [jk_ajp13_worker.c (258)]:
> received from
> ajp13 #2
> [Fri Mar 29 09:44:23 2002] [jk_ajp13_worker.c (549)]: Into
> jk_endpoint_t::done
>
> So something on the AIX is not letting the mod_jk get to
> these logs. On
> AIX we never get the "sending to ajp13 #190" message or the
> "received from
> ajp13 #28".
>
> We are going to try some other stuff, as well as another
> clean install and
> see if that helps. Please let me know if you have any other idea?
>
> Thanks for all your help,
> Jay
>
>
>
>
>
>
>
> Larry Isaacs
>
>
> <Larry.Isaacs@ To: 'Tomcat
> Users List' <[EMAIL PROTECTED]>
>
> sas.com> cc:
>
>
> Subject: RE:
> Tomcat 3.3a and mod_jk on AIX 4.3.3 built OK, but not sending
> requests
> 03/29/2002
>
>
> 09:34 AM
>
>
> Please respond
>
>
> to "Tomcat
>
>
> Users List"
>
>
>
>
>
>
>
>
>
>
>
>
> The ajp12.id file is used only for shutdown. It isn't used
> at all by mod_jk. However, a "bug/feature" in tomcat.sh
> would delete this file if Tomcat was started two time in
> a row, making it necessary to specify the Ajp12 port in the
> shutdown command. I'm not sure if this is what is occurring,
> or the absence of ajp12.id is an indication that Tomcat did
> not start successfully.
>
> Does the Tomcat log show that the Interceptors are starting
> successfully on ports 8080,8007, and 8009?
>
> Also, what is the "test" request you are trying to execute
> in your browser? What is the response you get? With
> JkLogLevel set to debug, you should see evidence in mod_jk's
> log of its inspection of every request that Apache receives.
> I'm not sure why you would see any indication of the requests
> Apache is receiving.
>
> Cheers,
> Larry
>
> > -----Original Message-----
> > From: Jay Balunas [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, March 29, 2002 9:09 AM
> > To: Tomcat Users List
> > Subject: RE: Tomcat 3.3a and mod_jk on AIX 4.3.3 built OK,
> > but not sending requests
> >
> >
> >
> > Larry,
> >
> > Thanks for the response.
> >
> > I'm Seeing two different things. When the "ajp12.id"
> file is not
> > working correctly we get this in the log
> > [jk_connect.c (108)]: Into jk_open_socket
> > [jk_connect.c (115)]: jk_open_socket, try to
> > connect socket = 6
> > [jk_connect.c (124)]: jk_open_socket, after
> connect ret = -1
> > [jk_connect.c (143)]: jk_open_socket, connect()
> > failed errno = 79
> >
> > We think this is because ajp12.id file does not get
> > created correctly
> > or is deleted automatically. So mod_jk has issues with the
> connection.
> >
> > When the ajp.id file is working correctly we see:
> >
> > [jk_worker.c (177)]: wc_create_worker, done
> > [jk_worker.c (223)]: build_worker_map, removing
> old ajp13
> > worker
> > [jk_worker.c (235)]: build_worker_map, done
> > [jk_worker.c (102)]: wc_open, done
> > [jk_uri_worker_map.c (345)]: Into
> > jk_uri_worker_map_t::map_uri_to_worker
> > [jk_uri_worker_map.c (407)]:
> > jk_uri_worker_map_t::map_uri_to_worker, Found a match ajp13
> > [jk_worker.c (123)]: Into wc_get_worker_for_name ajp13
> > [jk_worker.c (127)]: wc_get_worker_for_name, done
> > found a worker
> > [jk_ajp13_worker.c (654)]: Into jk_worker_t::get_endpoint
> > [jk_ajp13_worker.c (539)]: Into jk_endpoint_t::service
> > [jk_ajp13.c (346)]: Into ajp13_marshal_into_msgb
> > [jk_ajp13.c (480)]: ajp13_marshal_into_msgb - Done
> > [jk_connect.c (108)]: Into jk_open_socket
> > [jk_connect.c (115)]: jk_open_socket, try to
> > connect socket = 6
> > [jk_connect.c (124)]: jk_open_socket, after
> connect ret = 0
> > [jk_connect.c (132)]: jk_open_socket, set
> TCP_NODELAY to on
> > [jk_connect.c (140)]: jk_open_socket, return, sd = 6
> > [jk_ajp13_worker.c (167)]: In
> > jk_endpoint_t::connect_to_tomcat,
> > connected sd = 6
> >
> >
> > This is the end of that log (set on debug). I do not
> > actually see
> > where is says it passes on to Tomcat, and tomcat never gets
> > the request.
> > We are not sure what is causing either of these problems.
> Is there a
> > particular user that tomcat or apache must be started as?
> Do the file
> > permission's/groups have something to so with it. We are
> > starting as a
> > special user but all of the files under Apache, and tomcat
> > are awned by it.
> >
> > Thanks for any help,
> > Jay
> >
> >
> >
> >
> >
> >
> >
> > Larry Isaacs
> >
> >
> > <Larry.Isaacs@ To: 'Tomcat
> > Users List' <[EMAIL PROTECTED]>
> >
> > sas.com> cc:
> >
> >
> > Subject: RE:
> > Tomcat 3.3a and mod_jk on AIX 4.3.3 built OK, but not sending
> > requests
> > 03/29/2002
> >
> >
> > 08:34 AM
> >
> >
> > Please respond
> >
> >
> > to "Tomcat
> >
> >
> > Users List"
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Ajp13 should be the one to use. Does the mod_jk.log indicate
> > that the request is or isn't being forwarded to Tomcat?
> >
> > Cheers,
> > Larry
> >
> > > -----Original Message-----
> > > From: Jay Balunas [mailto:[EMAIL PROTECTED]]
> > > Sent: Thursday, March 28, 2002 4:24 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: Tomcat 3.3a and mod_jk on AIX 4.3.3 built OK, but
> > > not sending requests
> > >
> > >
> > > The mod_jk has been built successfully, and everything starts
> > > but mod_jk
> > > does not seem to be sending requests through. This exact same
> > > configuration and mod_jk.conf files work on Solaris, and
> HP, with no
> > > problems.
> > >
> > > Pages served directly through Apache work fine, as well as
> > > pages served
> > > directly through tomcat. When we access a page that goes
> > > through Apache
> > > and then uses the mod_jk to route to Tomcat we have problems.
> > > The requests
> > > just never seem to make it to the servlets. even the Tomcat
> > > examples do
> > > not work.
> > >
> > > Logs do not really show anything even when turned up. Also
> > > the ajp12.id
> > > file seems to get deleted randomly, but this could be
> > something else.
> > > Should ajp13 work fine in AIX 4.3.3 or should we use ajp12.
> > >
> > > Any idea would be great and Thanks,
> > > Jay
> > >
> > >
> > >
> > > --
> > > To unsubscribe:
> > <mailto:tomcat-user-> [EMAIL PROTECTED]>
> > > For
> > additional commands:
> > <mailto:[EMAIL PROTECTED]>
> > > Troubles with the list:
> > <mailto:[EMAIL PROTECTED]>
> > >
> >
> > --
> > To
> > unsubscribe: <mailto:[EMAIL PROTECTED]>
> > For additional commands:
> <mailto:[EMAIL PROTECTED]>
> > Troubles with
> the list: <mailto:[EMAIL PROTECTED]>
> >
> >
> >
> >
> >
> >
> > --
> > To unsubscribe:
> <mailto:tomcat-user-> [EMAIL PROTECTED]>
> > For
> additional commands:
> <mailto:[EMAIL PROTECTED]>
> > Troubles with the list:
> <mailto:[EMAIL PROTECTED]>
> >
>
> --
> To
> unsubscribe: <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>
>
>
>
>
>
>
> --
> To unsubscribe: <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>
>
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
