Diagnosing Axis problems

Server side

Common server-side problems are:

  1. missing libraries
  2. libraries not in the right place
  3. XML parser not 100% compatible with Axis. SeeXML Parser Notes for details.
  4. Multiple XML parsers in the classpath. Just plain trouble.

Admin Client

A lot of people have problems with this, compounded by difficulty making sense of the error code.

The Admin Client app uses SOAP to talk to the (localhost) copy of Axis. By default it talks to http://localhost:8080/axis/services/Admin . If your application server is on a different port, or Axis is hosted under a different webapp name than Axis, you are going to get an error. Probably an HTTP error code like 404 or 302, all bundled up in a dump of the AxisFault exception raised.

Point your web browser at the "endpoint" that you expect the client to run against it. If you dont get the 'there is a service here' message, the AdminClient wont run.

Client

The common client problems are

Setting up the classpath. Remember to include mail.jar and activation.jar when you want attachments, and get the right XML parser. See XML Parser Notes for details. Setting up the proxy. You need to set the properties http.proxyHost and http.proxyPort to point to the host:port configuration of the system. See How to Configure a Proxy for further tips.

FrontPage/Axis/Diagnostics (last edited 2009-09-20 22:47:41 by localhost)