Application Server Solutions for Microsoft IIS and ASP.NET
       solutions   products   partners   company   support   downloads         store
View Interest List Message Details
<< Back to Search Results

Date: 09/27/2005
From: jitesh.h.amin@lmco.com
Subject: RE: [ServletExec] Java Web Services on SE 5.0
Most of the time localhost would not work locally on a browser is
because the proxies are set to manual and not automatic. Change your
proxies to automatic and localhost will work fine (same as what Matt
suggested in below email).

-----Original Message-----
From: servletexec-interest-owner@mail.newatlanta.com
[mailto:servletexec-interest-owner@mail.newatlanta.com] On Behalf Of
matt@newatlanta.com
Sent: Monday, September 26, 2005 2:15 PM
To: servletexec-interest@mail.newatlanta.com
Subject: Re: [ServletExec] Java Web Services on SE 5.0

The only way I know to check to see if localhost is disabled is to put
an html file in the document root of the webserver and try to request it
using localhost and then request it using some other hostname.
If it fails with localhost but works with the other hostname then I'd
conclude that localhost is somehow disabled, blocked, messed up, not
working, etc...

You may want to talk with your network engineer, or whoever set up your
network.
They may be able to tell you about why localhost does not work on your
machine.

Well I just thought of 1 possible way that localhost might get
disabled...
If the hosts file were edited to remove the "localhost" entry or to
point to some other server.
I'm not sure why anyone would do that.

The file I'm talking about is (on my machine):
C:\WINDOWS\SYSTEM32\DRIVERS\ETC\HOSTS

I would not recommend that you mess with that file unless you fully
understand it.
Edits to that file typcially require a reboot to be "seen" by         
Windows.

Yes, if localhost does not work for you, then yes... you'll need to edit
the example so that it does not try to use localhost (or any other
hostname that fails to function for you).
Or you might try to figure out why your localhost is disabled, and then
take steps to re-enable it.

Another possible way that localhost might be disabled is if your browser
requests are going through a proxy server.
The proxy server might not really know what you mean by "localhost".
If that were the case, then maybe you could configure your browser so
that requests for localhost do not go through the proxy server at all,
thus "cutting out the middle man" :-)

If you place HelloWorld.jsp at C:/ServletExec AS/se-GIFT, and it is
served, then that seems very odd to me.
The C:\ServletExec AS\se-GIFT\ folder would not be a document root (for
any context) by default.

Are you sure you don't have a HelloWorld.jsp sitting at
...\Inetpub\GIFT\ ?

Anyway, I'm glad to know that you are able to access the SE admin pages
when you use the right hostname.
Take care.

Matt McGinty
Software Engineer
New Atlanta Communications, LLC
http://www.newatlanta.com 



Kelly, Michael (DSI) wrote:

>>Michael,
>>Sorry that you had to rename some files to get our batch files to 
>>work.
>>I guess Axis is a moving target, and we'll need to get the         
examples 
>>updated.
>>I'm glad to know that you were able to move past that obstacle.
>>
>>    
>>
>No problem. That was the easy part.
>  
>
>>No, you don't just create a folder
>>called axis under webapps, and just
>>put the code there.
>>You need to deploy a webapp using the SE admin pages.
>>So... you're having trouble accessing the SE admin pages?
>>
>>What is the full and complete URL that you are using?
>>
>>    
>>
>The full URL to the Web Server (IIS) is 128.147.226.48:80
>
>IIS redirects any jsp references to this URL to 127.0.0.1:8889, which 
>is where a SE instance called GIFT is listening.
>
>  
>
>>Since you mentioned that you are using:
>>Start | Programs | New Atlanta | ServletExec 5.0 AS | ServletExec
>>    
>>
>Admin
>  
>
>>I'm guessing that the URL that gets requested is:
>>
>>http://localhost/servletexec/admin
>>
>>right?
>>
>>    
>>
>That is correct.
>
>  
>
>>If so, and that does not work,
>>
>>    
>>
>It does not.
>
>But looking ahead at some of your other questions I tried:
>http://128.147.226.48/servletexec/admin
>and that DID work!!! This also leads me to thing that wherever 
>localhost appears in any of the files/code in the examples, I will need

>to change it to 128.147.226.48.
>
>  
>
>>then what happens if you create a simple helloWorld.html file, drop it

>>into the doc root of your IIS website
>>    
>>
>and
>  
>
>>then request it like this:
>>http://localhost/helloWorld.html
>>
>>    
>>
>I would put the document into the GIFT doc root at Inetpub/GIFT. Then 
>referencing the document as http://128.147.226.48/HelloWorld.html
>I would get served the page. 
>If I put HelloWorld.jsp at
>C:/ServletExec AS/se-GIFT
>And referenced the doc as
>http://128.147.226.48/HelloWorld.jsp
>I would also get the jsp served up. 
>Hopefully this answers some questions about my current configuration. 
>
>I have no idea where http://localhost would refer to. 
>
>
>  
>
>>is it served?
>>
>>If yes, then maybe go through all the steps given in SE FAQ #7:
>>
>>    
>>
>http://www.newatlanta.com/c/products/servletexec/self_help/faq/detail?f
>a
>qId=7
>  
>
>>and let me know what you find.
>>
>>If no, then what if you use some other hostname?
>>Maybe "localhost" is disabled on your server machine.
>>
>>On what port does your website listen?
>>Is it port 80?
>>
>>    
>>
>Se above. How would I find out if localhost is disabled? How do you 
>disable localhost.
>
>  
>
>>Matt McGinty
>>Software Engineer
>>New Atlanta Communications, LLC
>>http://www.newatlanta.com
>>
>>    
>>
>Thank you for your response, Matt. I sure needed someone to talk these 
>things through with.
>
>-----------------------------------------------------------------------
>-- ServletExec-Interest. For archives and unsubscribe instructions, 
>visit:
>
>    http://www.newatlanta.com/servletexec-interest.jsp
>  
>

------------------------------------------------------------------------
-
ServletExec-Interest. For archives and unsubscribe instructions, visit:

   http://www.newatlanta.com/servletexec-interest.jsp
-------------------------------------------------------------------------
ServletExec-Interest. For archives and unsubscribe instructions, visit:

    http://www.newatlanta.com/servletexec-interest.jsp

Message Thread
Date Subject Author
09/26/2005 Re: [ServletExec] Java Web Services on SE 5.0 matt@newatlanta.com
09/26/2005 RE: [ServletExec] Java Web Services on SE 5.0 kellymt@upmc.edu
09/26/2005 Re: [ServletExec] Java Web Services on SE 5.0 matt@newatlanta.com
09/26/2005 RE: [ServletExec] Java Web Services on SE 5.0 kellymt@upmc.edu
09/26/2005 Re: [ServletExec] Java Web Services on SE 5.0 matt@newatlanta.com
09/27/2005 RE: [ServletExec] Java Web Services on SE 5.0 jitesh.h.amin@lmco.com
09/27/2005 RE: [ServletExec] Java Web Services on SE 5.0 kellymt@upmc.edu
09/27/2005 RE: [ServletExec] Java Web Services on SE 5.0 jitesh.h.amin@lmco.com
09/27/2005 RE: [ServletExec] Java Web Services on SE 5.0 kellymt@upmc.edu
09/27/2005 RE: [ServletExec] Java Web Services on SE 5.0 kellymt@upmc.edu
09/27/2005 Re: [ServletExec] Java Web Services on SE 5.0 matt@newatlanta.com
09/28/2005 RE: [ServletExec] Java Web Services on SE 5.0 kellymt@upmc.edu
09/28/2005 Re: [ServletExec] Java Web Services on SE 5.0 matt@newatlanta.com
09/26/2005 [ServletExec] Java Web Services on SE 5.0 kellymt@upmc.edu
<< Back to Search Results


   
company media information terms of use privacy policy contact us