You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Pete Helgren <pe...@timptech.com> on 2006/03/07 20:00:57 UTC

Sorting out a 404 error

I have an axis application that I created (in MyEclipse) and run on my 
local PC.  I created a .net client application that uses SOAP, again on 
my local machine using VS2005, and I tested it and it works great.

I then wanted to test the .net client from another machine on the 
network.  I changed the WSDL file to use the actual address of the PC 
running tomcat from 'localhost' so that now the address is the local 
address of the machine.  Again, I tested the client locally and it works.

So I deployed the client application to another PC on the network.  When 
I run client application I get a "The request failed with HTTP status 
404: /SOAServices/services/DBIO" error.  So, I decided to run the URL 
from a browser and see what I got. I get: "DBIO Hi there, this is an 
AXIS service! Perhaps there will be a form for invoking the service 
here... "

So that tells me that the server is available and is happy with the URL 
(which I copied and pasted from the WSDL file so I know it is 
accurate).  I get a very similar message from a client I wrote in RPGLE 
(IBM midrange hardware running i5/OS) so I think it has to do with a 
configuration issue at the server, although I can't say for sure.

So the questions are:  What should I do next to determine what is 
causing the error? What is the most like cause? Is there a tool I can 
use to view the request that Axis receives os perhaps see that HTTP 
request being sent?  I have been working on this problem all morning 
(and Googling like crazy) and haven't found a solution.

Thanks.

Pete Helgren


Re: Sorting out a 404 error

Posted by "Gonia, Philip T" <Ph...@grc.nasa.gov>.
I for one am very grateful that you have commented on your resolution.

Glad to see you have everything running now.

Philip

On Mar 8, 2006, at 11:04 AM, Pete Helgren wrote:

> Thanks Philip.
>
> Yes, the first the place I go is the documentation, then the forum  
> (to search) and then Google.  If I am stumped, then I bother a  
> human (first at my company and then post a question).  We are all  
> busy people and answering a question that has been already answered  
> isn't very productive.  However, Googling can be both blessing and  
> curse.
>
> However, I did identify and fix the problem while I was waiting for  
> a post back. The fact that the URL got a positive response back  
> from Axis told me that all was well at the  installation end.   
> The .net client issue was a little more challenging.  Turns out  
> there is a file that has a .config extension that has the host name/ 
> address and port.  It is buried with a bunch of other configuration  
> files so I had updated the wrong one.  When I finally changed the  
> correct file to use the correct host name, the .net client began to  
> work.  The 404 error was gone.
>
> The IBM RPGLE program was a bit more of a challenge.  It was  
> contacting the Axis application server but Axis (Tomcat) was  
> returning an HTTP 500 message.  Using TCPMon (which is a great tool  
> that could use some slightly better documentation) I discovered  
> that the XML was improperly formatted.   Once that was corrected,  
> the 500 error was gone.
>
> So it was just tracking down the causes for each client app error,  
> rather than an Axis problem.
>
> I am a bit new to web services so I am still in learning curve  
> mode.  I am documenting this here is case anyone else runs into  
> newbie issues like this...
>
> Pete
>
> Gonia, Philip T wrote:

Re: Sorting out a 404 error

Posted by Pete Helgren <pe...@timptech.com>.
Thanks Philip.

Yes, the first the place I go is the documentation, then the forum (to 
search) and then Google.  If I am stumped, then I bother a human (first 
at my company and then post a question).  We are all busy people and 
answering a question that has been already answered isn't very 
productive.  However, Googling can be both blessing and curse.

However, I did identify and fix the problem while I was waiting for a 
post back. The fact that the URL got a positive response back from Axis 
told me that all was well at the  installation end.  The .net client 
issue was a little more challenging.  Turns out there is a file that has 
a .config extension that has the host name/address and port.  It is 
buried with a bunch of other configuration files so I had updated the 
wrong one.  When I finally changed the correct file to use the correct 
host name, the .net client began to work.  The 404 error was gone.

The IBM RPGLE program was a bit more of a challenge.  It was contacting 
the Axis application server but Axis (Tomcat) was returning an HTTP 500 
message.  Using TCPMon (which is a great tool that could use some 
slightly better documentation) I discovered that the XML was improperly 
formatted.   Once that was corrected, the 500 error was gone.

So it was just tracking down the causes for each client app error, 
rather than an Axis problem.

I am a bit new to web services so I am still in learning curve mode.  I 
am documenting this here is case anyone else runs into newbie issues 
like this...

Pete
 

Gonia, Philip T wrote:

> Hi Pete,
>
> Did you by change read these two documents?
>
> The big ONE:
>
> Installation: http://ws.apache.org/axis/java/install.html
>
> Then this one: http://ws.apache.org/axis/java/user-guide.html
>
> If by chance you have not I recommend you take some time to go  
> through these.
> There is indeed a bit of reading here but well worth the time. It was  
> for me anyway.
>
> It is a challenge to help you out at this point not knowing exactly  
> what you have and have not done
> by way of configuration. So it is important that you take some time  
> and work through these
> two documents. They are really good documents and someone spent a  
> great deal of time on
> them to make them so. If you still have problems after following  
> these, drop a line back here.
>
> Philip
>

Re: Sorting out a 404 error

Posted by "Gonia, Philip T" <Ph...@grc.nasa.gov>.
Hi Pete,

Did you by change read these two documents?

The big ONE:

Installation: http://ws.apache.org/axis/java/install.html

Then this one: http://ws.apache.org/axis/java/user-guide.html

If by chance you have not I recommend you take some time to go  
through these.
There is indeed a bit of reading here but well worth the time. It was  
for me anyway.

It is a challenge to help you out at this point not knowing exactly  
what you have and have not done
by way of configuration. So it is important that you take some time  
and work through these
two documents. They are really good documents and someone spent a  
great deal of time on
them to make them so. If you still have problems after following  
these, drop a line back here.

Philip

On Mar 7, 2006, at 2:00 PM, Pete Helgren wrote:

> I have an axis application that I created (in MyEclipse) and run on  
> my local PC.  I created a .net client application that uses SOAP,  
> again on my local machine using VS2005, and I tested it and it  
> works great.
>
> I then wanted to test the .net client from another machine on the  
> network.  I changed the WSDL file to use the actual address of the  
> PC running tomcat from 'localhost' so that now the address is the  
> local address of the machine.  Again, I tested the client locally  
> and it works.
>
> So I deployed the client application to another PC on the network.   
> When I run client application I get a "The request failed with HTTP  
> status 404: /SOAServices/services/DBIO" error.  So, I decided to  
> run the URL from a browser and see what I got. I get: "DBIO Hi  
> there, this is an AXIS service! Perhaps there will be a form for  
> invoking the service here... "
>
> So that tells me that the server is available and is happy with the  
> URL (which I copied and pasted from the WSDL file so I know it is  
> accurate).  I get a very similar message from a client I wrote in  
> RPGLE (IBM midrange hardware running i5/OS) so I think it has to do  
> with a configuration issue at the server, although I can't say for  
> sure.
>
> So the questions are:  What should I do next to determine what is  
> causing the error? What is the most like cause? Is there a tool I  
> can use to view the request that Axis receives os perhaps see that  
> HTTP request being sent?  I have been working on this problem all  
> morning (and Googling like crazy) and haven't found a solution.
>
> Thanks.
>
> Pete Helgren
>
>