Good Morning-
the applicable snippet from jk_ajp_common.c authored by Gal Shachor
<[EMAIL PROTECTED]>

           jk_log(l, JK_LOG_ERROR,
                   "Can't receive the response message from tomcat, "
                   "network problems or tomcat is down (%s), err=%d",
                   jk_dump_hinfo(&ae->worker->worker_inet_addr, buf), rc);

Were you able to verify port 4540 is open and clear of firewalls and or
natted proxies?
>netstat -a | grep 4540
//you should see TC is *listening* on 8080

The default port assignment for non-SSL HTTP/1.1 from
%TOMCAT_HOME%/conf/server.xml is 8080
as illustrated in this example
    <!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
    <Connector port="8080"

These configurations can be difficult to diagnose..please feel free to ping
the group for any questions

HTH
Martin-
----- Original Message -----
Wrom: HMKHJYFMYXOEAIJJPHSCRTNHGSWZIDREXCAXZOWCONEUQZA
To: "Tomcat Users List" <users@tomcat.apache.org>
Cc: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Wednesday, March 26, 2008 8:45 AM
Subject: Re: another apache/tomcat/mod_jk/virtual hosting question/issue


> Thanks for your advice David. I will abandon this forum and try to figure
> it out myself.
> "Tomcat Users List" <users@tomcat.apache.org> on Wednesday, March 26, 2008
> at 7:46 AM -0500 wrote:
> >Bad Gateway wouldn't be generated by tomcat unless your tomcat code was
> >somehow getting content from another site.  Given your most recent log
> >snippets have apparently been from an httpd error log file instead of
> >tomcat's logs (like catalina.out), I'm going to guess your mod_jk setup
> >in httpd isn't working.  JSP compile errors don't show up in the httpd
> >error log and mod_jk errors don't show up in catalina.out under any
> >normal setup.
> >
> >As Chuck points out, there isn't just one problem here, there's
> >several.  Start by making sure your tomcat is working first.  You can do
> >that by making sure a standard http connector is setup to let's say port
> >8080 and then hitting http://ww3.nisonline.org:8080/test.jsp.  When that
> >works, fix your mod_jk setup.
> >
> >--David
> >
> >Tommy Peterson wrote:
> >> When the unable to compile class for JSP error showed up (it isn't
> >> anymore) it would mention the jsp file that I was calling. I
> >intentionally
> >> called several different jsp files to see if it was the coding,
> >althougth
> >> this application works now, and has for years, on a different server
> >just
> >> fine (I need to move it)--so it isn't a code issue. The error points to
> >a
> >> line in that file. I have looked to see if the class is there--it is.
> >> Anyway, this says to me that Java is somehow not being used or
installed
> >> correclty--things can't compile. I verified that Java was installed
> >> correctly. Anyway, what happens now is that the page just sits there
and
> >> then after a few seconds I get a Bad Gateway page. A 502 error. Try it:
> >> ww4.nislonline.org or use the other one that I am now pointing to the
> >> standard jsp examples to test whether Tomcat shows up:
> >ww3.nislonline.org
> >> You'll see the HTML page but try to submit the post: same issue as it
is
> >> posting to a jsp page.
> >>
> >> I don't understand why this has to be this difficult. I have followed
> >the
> >> documentation. And it seems I just keep running into new brick walls.
> >>
> >> Thanks.
> >>
> >> "Tomcat Users List" <users@tomcat.apache.org> on Tuesday, March 25,
2008
> >> at 3:55 PM -0500 wrote:
> >>
> >>> In that case, there should have been some text after
> >>> 'org.apache.jasper.JasperException: Unable to compile class for JSP: '
> >>> citing the line number and problem with the jsp.  Is it really just
> >>> blank where compile error message should be?  Can you try to restart
> >>> tomcat and see if that clears the issue?
> >>>
> >>> --David
> >>>
> >>> Tommy Peterson wrote:
> >>>
> >>>> I went all the way to the top of the error log for the first error;
> >>>>
> >>> there
> >>>
> >>>> were two, one after the other:
> >>>> [error] jk_ajp_common.c (1004): (ajp13) can't receive the response
> >>>>
> >>> message
> >>>
> >>>> from tomcat, tomcat (127.0.0.1:8009) has forced a connection close
for
> >>>> socket 4540
> >>>> [Tue Mar 25 15:02:44.320 2008] [5796:5300] [error] jk_ajp_common.c
> >>>>
> >>> (1766):
> >>>
> >>>> (ajp13) Tomcat is down or refused connection. No response has been
> >sent
> >>>>
> >>> to
> >>>
> >>>> the client (yet)
> >>>>
> >>>> "Tomcat Users List" <users@tomcat.apache.org> on Tuesday, March 25,
> >2008
> >>>> at 2:26 PM -0500 wrote:
> >>>>
> >>>>
> >>>>> From experience, this error is usually the result of an earlier
> >error.
> >>>>>
> >>>>> Look further up your logs to the first error that occurs after you
> >>>>> request this page.  Fix that and this one should go away.
> >>>>>
> >>>>> --David
> >>>>>
> >>>>> Tommy Peterson wrote:
> >>>>>
> >>>>>
> >>>>>> this is the problem with every jsp page I try to hit. does this
mean
> >>>>>>
> >>>>>>
> >>>>> java
> >>>>>
> >>>>>
> >>>>>> can't compile the java beans? I don't get this. I did a search and
> >lot
> >>>>>>
> >>>>>>
> >>>>> of
> >>>>>
> >>>>>
> >>>>>> a ppl seem to have issue but no solutions.
> >>>>>>
> >>>>>> type Exception report
> >>>>>>
> >>>>>> message
> >>>>>>
> >>>>>> description The server encountered an internal error () that
> >prevented
> >>>>>>
> >>>>>>
> >>>>> it
> >>>>>
> >>>>>
> >>>>>> from fulfilling this request.
> >>>>>>
> >>>>>> exception
> >>>>>>
> >>>>>> org.apache.jasper.JasperException: Unable to compile class for JSP:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Stacktrace:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>
> >
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandle
r.java:92)
> >>>
> >>>>>
> >>>>>
> >>>>>
> >>>
> >
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:3
30)
> >>>
> >>>>>
> >>>>>
> >>>>>
> >>>
> >
org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:423)
> >>>
> >>>>>
> >>>>>
> >>>>>> org.apache.jasper.compiler.Compiler.compile(Compiler.java:308)
> >>>>>> org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
> >>>>>> org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)
> >>>>>>
> >>>>>>
> >>>>>>
> >>>
> >
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:5
66)
> >>>
> >>>>>
> >>>>>
> >>>>>
> >>>
> >
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:3
17)
> >>>
> >>>>>
> >>>>>
> >>>>>
> >>>
> > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
> >>>
> >>>>>
> >>>>>
> >>>>>> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
> >>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
> >>>>>>
> >>>>>> "Tomcat Users List" <users@tomcat.apache.org> on Tuesday, March 25,
> >>>>>>
> >>> 2008
> >>>
> >>>>>> at 1:03 PM -0500 wrote:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> Sorry about that.
> >>>>>>> Tomcat 6.0.1.4
> >>>>>>> Apache 2.2.9
> >>>>>>>
> >>>>>>> What is the command to get a module version number listing?
> >>>>>>>
> >>>>>>> If I am on the server and enter localhost:8080/nisl4 or
> >>>>>>> localhost:8080/nisl3 I get a 500 error saying that something can't
> >be
> >>>>>>> compiled. So i guess technicall I can reach the apps.
> >>>>>>>
> >>>>>>> Thanks.
> >>>>>>> "Tomcat Users List" <users@tomcat.apache.org> on Tuesday, March
25,
> >>>>>>>
> >>>>>>>
> >>>>> 2008
> >>>>>
> >>>>>
> >>>>>>> at 11:51 AM -0500 wrote:
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>>> From: Tommy Peterson [mailto:[EMAIL PROTECTED]
> >>>>>>>>> Subject: another apache/tomcat/mod_jk/virtual hosting
> >>>>>>>>>
> >>> question/issue
> >>>
> >>>>>>>>> But I cannot get the Java apps to work.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>> Don't suppose you'd care to give anyone a hint about what
versions
> >>>>>>>>
> >>> of
> >>>
> >>>>>>>> Tomcat, httpd, mod_jk, etc., you happen to be using?
> >>>>>>>>
> >>>>>>>> Can you access the webapps directly (port 8080), bypassing httpd?
> >>>>>>>>
> >>>>>>>> - Chuck
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE
> >>>>>>>>
> >>>>>>>>
> >>>>> PROPRIETARY
> >>>>>
> >>>>>
> >>>>>>>> MATERIAL and is thus for use only by the intended recipient. If
> >you
> >>>>>>>> received this in error, please contact the sender and delete the
> >>>>>>>>
> >>>>>>>>
> >>>>> e-mail
> >>>>>
> >>>>>
> >>>>>>>> and its attachments from all computers.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>> ---------------------------------------------------------------------
> >>>
> >>>>>>>> To start a new topic, e-mail: users@tomcat.apache.org
> >>>>>>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>>>>>>> For additional commands, e-mail: [EMAIL PROTECTED]
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
>
>>>>> ---------------------------------------------------------------------
> >>>>> To start a new topic, e-mail: users@tomcat.apache.org
> >>>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>>>> For additional commands, e-mail: [EMAIL PROTECTED]
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>> ---------------------------------------------------------------------
> >>> To start a new topic, e-mail: users@tomcat.apache.org
> >>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>> For additional commands, e-mail: [EMAIL PROTECTED]
> >>>
> >>>
> >>
> >>
> >>
> >>
> >
> >
> >---------------------------------------------------------------------
> >To start a new topic, e-mail: users@tomcat.apache.org
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
>


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to