> - The servlet in tomcat is talking to the same tomcat > instance. [-?- The servlet running in tomcat will get it's > data from a physically different server -?-]
Unless the error message is heavily missleading the servlet/axis is talking to a webserver. If it isn't the iis on server B it must be a different one. One possible candidate is the local tomcat. To verify/falsify that, check the access log of tomcat for a 404 error. > But 404 just makes no sense, for these reasons: Again if the message no garbage, there is a webserver that generates it. If it is generated by iis you have to find out what causes this error. Possible actions: - check the tomcat access log on server B for a 404 error - check the iis access log on server B for a 404 error - patch axis to provide more information about the environment in the stacktrace. (e.g. the response headers) - or debug the servlet - or watch the network traffic with a sniffer to verify if there really was a 404 response. > -----Original Message----- > From: KRUEGER MICHAEL [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 21, 2004 2:37 PM > To: Tomcat Users List > Subject: AW: Problem invoking webservice from within servlets service > method. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
