axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joaquim Carvalho <joaq...@dei.uc.pt>
Subject Re: Axis-Tomcat meltdown fixed!
Date Fri, 05 Oct 2001 07:41:30 GMT
Adding the for axis jars to the tomcat classpath solved the problem. 
Everything works now.

Thanks Mark,
Joaquim


On Friday, October 5, 2001, at 08:16 AM, Joaquim Carvalho wrote:

> Mark,
>
> I think I have the same problem as you, except I never saw it work on 
> the server (installed first time from Oct 1st distribution)
>
> My situation is:
>
> 1) I can see the Axis servlet running at 
> localhost:8080/axis/servlet/AxisServlet ( Hi there.. etc.)
> 2) The admin servlet at localhost:8080/axis/servlet/AdminServlet says 
> the server is running with two links "start server" and "stop server".
> 3) No server examples work. For example for the Calculator example for 
> the uguide  gives me:
>
> ---------------------------------------------------------------
> java -cp .:$AXIS_CP CalcClient -p8080 add 2 5
> Exception in thread "main" AxisFault
>   faultCode: null
>   faultString: The Axis engine couldn't find a target service to 
> invoke! targetService is
>   faultActor: null
>   faultDetails: null
>
>         at 
> org.apache.axis.message.SOAPFaultElement.getAxisFault(SOAPFaultElement.java:
> 132)
>         at 
> org.apache.axis.message.SOAPFaultBuilder.<init>(SOAPFaultBuilder.java:90)
>         at 
> org.apache.axis.message.BodyBuilder.onStartChild(BodyBuilder.java:77)
>      ... etc ....
>         at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:148)
>         at 
> org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:
> 981)
>         at javax.xml.parsers.SAXParser.parse(SAXParser.java:374)
>         at 
> org.apache.axis.encoding.DeserializationContext.parse
> (DeserializationContext.java:160)
>         at org.apache.axis.Message.getAsSOAPEnvelope(Message.java:319)
>         at 
> org.apache.axis.client.ServiceClient.invoke(ServiceClient.java:588)
>         at 
> org.apache.axis.client.ServiceClient.invoke(ServiceClient.java:494)
>         at CalcClient.main(CalcClient.java:84)
> ---------------------------------------------------------------
> TCPMonitor trace:
>
> ---------------------------------------------------------------
> POST /axis/Calculator.jws HTTP/1.0
> Content-Length: 363
> Host: 192.168.0.10
> Content-Type: text/xml; charset=utf-8
> SOAPAction: "/add"
>
> <?xml version="1.0" encoding="UTF-8"?>
> <SOAP-ENV:Envelope xmlns:SOAP-
> ENV="http://schemas.xmlsoap.org/soap/envelope/" 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>  <SOAP-ENV:Body>
>   <add>
>    <arg0 xsi:type="xsd:int">2</arg0>
>    <arg1 xsi:type="xsd:int">5</arg1>
>   </add>
>  </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
> ---------------------------------------------------------------
> HTTP/1.0 500 Internal Server Error
> Content-Type: text/xml; charset=utf-8
> Content-Length: 545
> Set-Cookie2: JSESSIONID=0m90060nf1;Version=1;Discard;Path="/axis"
> Set-Cookie: JSESSIONID=0m90060nf1;Path=/axis
> Servlet-Engine: Tomcat Web Server/3.2.1 (JSP 1.1; Servlet 2.2; Java 
> 1.3.0; Mac OS X 10.0 ppc; java.vendor=Apple Computer, Inc.)
>
> <?xml version="1.0" encoding="UTF-8"?>
> <SOAP-ENV:Envelope xmlns:SOAP-
> ENV="http://schemas.xmlsoap.org/soap/envelope/" 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>  <SOAP-ENV:Body>
>   <SOAP-ENV:Fault>
>    <SOAP-ENV:faultcode 
> xmlns:ns4="http://xml.apache.org/axis/">ns4:Server.NoService</SOAP-
> ENV:faultcode>
>    <SOAP-ENV:faultstring>The Axis engine couldn&apos;t find a target 
> service to invoke! targetService is </SOAP-ENV:faultstring>
>   </SOAP-ENV:Fault>
>  </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
> ---------------------------------------------------------------
> Note that the name of the target service is missing from the error 
> message.
>
> If I  point the browser to http://localhost:8080/axis/Calculator.jws I 
> get the "Hi, this is an Axis service!" page. So this means Axis is 
> running at the server and mapping of jws files is working.
>
> 4) AdminClient seems to find nothing at the server:
>
> ---------------------------------------------------------------
> java -cp $AXIS_CP org.apache.axis.client.AdminClient list
> Doing a list
> <ns1:Fault xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/">
>    <ns1:faultcode 
> xmlns:ns4="http://xml.apache.org/axis/">ns4:Server.NoService</ns1:faultcode>
>    <ns1:faultstring>The Axis engine couldn't find a target service to 
> invoke! targetService is AdminService</ns1:faultstring>
>   </ns1:Fault>
> ---------------------------------------------------------------
>
>
> So what you think?
>
> Joaquim
>
>
> On Thursday, October 4, 2001, at 09:09 AM, Mark Young wrote:
>
>> I should have added that I was able to invoke services before, and now 
>> none at all.  This includes the admin service that lists services, and 
>> lets you deploy them.  Major bummer.  I also should have said that I 
>> am running Linux.
>>  
>> From looking at the source code, I'm guessing that the Axis servlet 
>> gets service information from WEB-INF/server-config.xml.  But I'm very 
>> sure that the non-source code drops don't include this file.  So I 
>> don't know if my system ever had it, or how it got there if it did 
>> have it.  I copied the one over from a source code drop.  This did not 
>> seem to help at all.
>>  
>> Can someone who understands how/where Axis keeps track of the deployed 
>> services (what file it is kept in, if there is one, and how that file 
>> is supposed to get created/installed) please give a short 
>> explanation?  Or point me to something that explains it?
>>  
>> BTW Joaquim, I had other problems getting the server side to work 
>> before I ran into this.  Are you seeing a SOAP fault message coming 
>> back with the string I mentioned?  If you're having a different 
>> problem that I already solved, I'd be glad to tell you how.
>>  
>> Mark Young
>> mark@kamiak.com
>>  
>>
>> ----- Original Message -----
>> From: Joaquim Carvalho
>> To: axis-user@xml.apache.org
>> Sent: Thursday, October 04, 2001 1:31 AM
>> Subject: Re: Axis-Tomcat meltdown
>>
>> Same problem. Just installed Axis (1-Oct-2001) for the first time and 
>> can't make the server side work.
>>
>> Client side works perfectly with other SOAP services -- very nice API.
>>
>> Joaquim Carvalho
>> Portugal
>>
>> On Wednesday, October 3, 2001, at 07:12 PM, Mark Young wrote:
>>
>> Has anyone out there run into (and hopefully solved) this problem?  I 
>> must have done something terrible to my Tomcat 3.2.2/Axis 
>> installation, because now when I try to invoke any Axis service, I get 
>> a soap message with a fault string: "The Axis engine couldn't find a 
>> target service to invoke! ...."
>>  
>> I've tried many things (since I don't have a good idea about what the 
>> real problem is), including replacing webapps/axis with a fresh copy 
>> of the original stuff.  That didn't work.
>>  
>> Any clues?
>>  
>> Thanks,
>>  
>> Mark Young
>>  
>>

Mime
View raw message