You said you're using Eclipse - if you have Eclipse WTP, it comes with a TCP/IP monitor (Window -> Views -> Debug -> TCP/IP Monitor). You would want to create a monitor for port 8080 on some other port, say, 8081. You then change the test client to send the message to port 8081 instead of 8080. All messages will go through the monitor, and you'll see request and response. The response in this case should have an Axis2 stack trace inside of an Axis2-generated SOAP fault.
Just to be certain - you're getting the binary distribution, running ant on the apache-httpd sample, and deploying that WAR, right? You're not trying to do wsdl2java on the WSDL and then reconstruct the WAR contents manually (by copying files over)? "David Medinets" <[EMAIL PROTECTED]> wrote on 10/28/2006 02:40:57 PM: > On 10/28/06, Daniel Jemiolo <[EMAIL PROTECTED]> wrote: > > When you get this error, it means either there was an Axis2 error or a > > failure at initialization. Check the Muse log file > > (WEB-INF/services/muse/log/) and the Tomcat console or log file. That will > > have the stack trace that is the root cause of the error. If there is no > > error to be found, it is an Axis2 error, and the only way I've been able > > to get those stack traces is via SOAP monitor. > > The Tomcat console has no error messages. > The services/muse directory has no log directory. > The Tomcat error logs show no exceptions. > > Can you elaborate about the SOAP Monitor? My understanding is that the > SOAP Monitor sits between the client and server, watching the SOAP > messages go by. I know what the source message is. And the server > response is most likely empty because of the 500 error? I'm certainly > willing to get the SOAP monitor working and I'm researching how to do > that now but I'm not sure what I'd be using it to find. At this point, > I'd think I would need to examine the > org.apache.muse.core.AbstractResourceClient.invoke method to find out > why the 500 response happened ... not that I want to go digging into > the MUSE source code. > > thanks. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
