Please see Appendix B, Running client programs from any directory if a client fails with "Failed to acquire notification consumer home instance from registry. Caused by javax.naming.NameNotFoundException: Name services is not bound in this Context" error.

This warning is logged by the container if the request did not contain the necessary WS-Addressing headers. The client either did not attempt to send those headers at all or is somehow misconfigured. If you using a Java client and launching it directly using the java executable take a look at Appendix B, Running client programs from any directory.

If you see the "java.io.IOException: Token length X > Y" error in the container log it usually means you are trying to connect to HTTPS server using HTTP. For example, the service address specifies 8443 as a port number and http as the protocol name. In general, 8443 port number should be used with the https protocol, and 8080 port number should be used with the http protocol.

If the standalone container appears to hang, for example the list of deployed services is not shown after a while or all requests to the container time out, please see the Debugging hanged Java process section for information on how to diagnose this problem.

The "java.lang.NoSuchFieldError: DOCUMENT" error usually indicates a mismatch between the version of Apache Axis that the code was compiled with and the version of Axis that the code is currently running with. Make sure that the same version of Axis is used at compile time and at runtime.

The "org.globus.wsrf.InvalidResourceKeyException: Argument key is null" (or "org.globus.wsrf.InvalidResourceKeyException: Resource key is missing") error usually indicates that a resource key was not passed with the request or that an invalid resource key was passed with the request (that is, the element QName of the resource key did not match what the service expected).

Make sure that the EPR used to invoke the service contains the appropriate resource key. If you are using some command-line tool make sure to specify the resource key using the -k option or pass a complete EPR from a file using the -e option.

In general, if you want to investigate a problem on your own please see Debugging for details on how to turn on debugging. Also, please note that most of the command line clients have a -debug option that will display more detailed error messages, including the error stack traces. Also, searching the mailing lists such as gt-user@globus.org or jwscore-user@globus.org (before posting a message) can also be very fruitful. Finally, if you think you have found a bug please report it in our Bugzilla system. Please include as much as detail about the problem as possible.