Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 58061 invoked from network); 10 Jul 2009 16:39:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Jul 2009 16:39:47 -0000 Received: (qmail 91082 invoked by uid 500); 10 Jul 2009 16:39:54 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 91050 invoked by uid 500); 10 Jul 2009 16:39:53 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 91041 invoked by uid 99); 10 Jul 2009 16:39:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jul 2009 16:39:53 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of chintankachhi@gmail.com designates 74.125.92.149 as permitted sender) Received: from [74.125.92.149] (HELO qw-out-1920.google.com) (74.125.92.149) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jul 2009 16:39:45 +0000 Received: by qw-out-1920.google.com with SMTP id 14so316657qwa.48 for ; Fri, 10 Jul 2009 09:39:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=3mLtq1IPbONMoikO9QMRBSWin9+ZFnyFwQi4ievStv8=; b=aqCjbM70zU0FSCK7xBunibJMcM2X6OU2afIz1rZ2L9e+zgrhum26+BHpiWHJx7iAMC T9bJ8FKrJeZG+DKukkMN2f3hvEoEbPd74iCzYhDCQqN3Q/NDzZmbx43LdN6IFZpLxppg f3WM0fDmCLPNpTz57pGiUY03/FNu4MOwYFczc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=aKofTzCmHAGfiOeckg78/wRSt1Tivhst2e/kmYSyvXuy16YV1kWo10pL0iLd2ByzLm CiT00rxS5K8QMiC+JaIMgNH7zF1LkSPMoNccgKxHtsztNa03SAwHGBRpx8DHWyxev4k0 p8LsJM5y9oK+leMFPU7uTbCuw7IOgk4g0zVkI= MIME-Version: 1.0 Received: by 10.229.80.78 with SMTP id s14mr368647qck.101.1247243964575; Fri, 10 Jul 2009 09:39:24 -0700 (PDT) In-Reply-To: <1404e5910907091354i6e9b0f36x584f445b5e6756c2@mail.gmail.com> References: <4A521B1E.2080807@soco.agilent.com> <4A52693C.7030604@ice-sa.com> <1404e5910907061911g18300033s233b0f96d30d471c@mail.gmail.com> <1404e5910907091354i6e9b0f36x584f445b5e6756c2@mail.gmail.com> Date: Fri, 10 Jul 2009 11:39:24 -0500 Message-ID: From: Chintan Kachhi To: users@httpd.apache.org Content-Type: multipart/alternative; boundary=001636426d4d74f2ac046e5c9d5c X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] Re: How to see/use the response when the apache server is down. --001636426d4d74f2ac046e5c9d5c Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Thanks for the response... I looked through my httpd.conf file and found that the WebSpherePluginConfig was pointing to the wrong plugin directory ( the person who had originally installed WAS had forgotten to update the file to point it to the right directory). I regenerated and propagated the plugin, and now it shows the correct error page, when the app server is down. Now I get back to my main problem which I originally had... So now, my IBM HTTP Server is running, my WebSphere application server is running, but I take down one of the services in the app server. When I try to hit the service from the url, it does not return my custom error message... instead returns something like: SRVE0255E: A WebGroup/Virtual Host to handle /service1 has not been defined. SRVE0255E: A WebGroup/Virtual Host to handle localhost:80 has not been defined. IBM WebSphere Application Server ( where service1 is the service that I take down.) I looked at the http status codes returned through the live http headers and it seems like it returns 404 Not Found... But then I am not sure why it is not redirecting it to my custom error page, because I already have an errordocument directive for 404 error in my httpd.conf file. When I do something like: http://localhost/chintan.html, it shows the custom error page for 404 that I defined.. ( since such a page does not exist.), but when I do something like: http://localhost/myservice, where my service is a service on the app server that I have taken down, it shows the above message instead of my custom error page. Not sure why it does this. On Thu, Jul 9, 2009 at 3:54 PM, Eric Covener wrote: > On Thu, Jul 9, 2009 at 3:48 PM, Chintan Kachhi > wrote: > > [To Dan Poirier] I need to go to Websphere to hit the service and that > > requires the port 9080, hence I do that... but this should work and > return > > the error message I think since the http server is linked to the > Websphere > > through the plugin... someone correct me if I am wrong. > > It's only linked when you ask the WebServer for a page, and it fetches > it from the AppServer. If you ask the AppServer (port 9080) the > webserver isn't involved. > > The message you pasted is generated by the browser when it can't > connect to port 9080, where your AppServer is normally listening. > > > > > As for changing the port plugin-cfg.xml to something not listening, I am > not > > sure how to do that. Do you change something in the plugin.xml file, or > > within the Websphere admin console? > > I did that to illustrate the behavior when the WebSphere Plugin can't > connect to the AppServer. You don't want to change the port. > > > -- > Eric Covener > covener@gmail.com > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See for more info. > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org > " from the digest: users-digest-unsubscribe@httpd.apache.org > For additional commands, e-mail: users-help@httpd.apache.org > > --001636426d4d74f2ac046e5c9d5c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks for the response... I looked through my httpd.conf file and found that the WebSpherePluginConfig was pointing to the wrong plugin directory ( the person who had originally installed WAS had forgotten to update the file to point it to the right directory). I regenerated and propagated the plugin, and now it shows the correct error page, when the app server is down. Now I get back to my main problem which I originally had... So now, my IBM HTTP Server is running, my WebSphere application server is running, but I take down one of the services in the app server. When I try to hit the service from the url, it does not return my custom error message... instead returns something like:


SRVE0255E: A WebGroup/Virtual Host to handle /service1 has not been defined= .

SRVE0255E: A WebGroup/Virtual Host to handle localhost:80 has not been defi= ned.

IBM WebSphere Application Server

( where service1 is the service that I take down.)

I looked at the http status codes returned through the live http headers an= d it seems like it returns 404 Not Found...

But then I am not sure why it is not redirecting it to my custom error page, because I already have an errordocument directive for 404 error in my httpd.conf file.

=A0 When I do something like:=A0=A0 http://localhost/chintan.html, it=A0 shows the custom error page for 404 that I defined.. ( since such a page does not exist.), but
=A0when I do something like: http://= localhost/myservice, where my service is a service on the app server that I have taken down, it shows the above message instead of my custom error page.

Not sure why it does this.


On Thu, Jul 9, 2009 at 3:54 PM, Eric Cov= ener <covener@gmail.com> wrote:
On Thu, Jul = 9, 2009 at 3:48 PM, Chintan Kachhi<chintankachhi@gmail.com> wrote:
> [To Dan Poirier] I need to go to Websphere to hit the service and that=
> requires the port 9080, hence I do that... but this should work and re= turn
> the error message I think since the http server is linked to the Websp= here
> through the plugin...=A0 someone correct me if I am wrong.

It's only linked when you ask the WebServer for a page, and it fe= tches
it from the AppServer. If you ask the AppServer (port 9080) the
webserver isn't involved.

The message you pasted is generated by the browser when it can't
connect to port 9080, where your AppServer is normally listening.

>
> As for changing the port plugin-cfg.xml to something not listening, I = am not
> sure how to do that. Do you change something in the plugin.xml file, o= r
> within the Websphere admin console?

I did that to illustrate the behavior when the WebSphere Plugin can&#= 39;t
connect to the AppServer. You don't want to change the port.


--
Eric Covener
covener@gmail.com

--001636426d4d74f2ac046e5c9d5c--