Increasing log verbosity

Generating verbose log output is a critical aid in troubleshooting of the WS RLS and is useful when communicating problems to Globus support lists. To increase logging detail, add the following lines to the $GLOBUS_LOCATION/container-log4j.properties file.

...
log4j.category.org.globus.replica.location=DEBUG
log4j.category.org.globus.replica.rls=DEBUG
...
            

Error: java.lang.NullPointerException

When invoking the WS RLS command-line clients, a system-level exception like the one above may be encountered. The admin should check the container logs for the exact error.

Error: A server error occured while processing the request.

When invoking the WS RLS command-line clients, a server error like the one above may be encountered. The admin should check the container logs for the exact error.

java.lang.UnsatisfiedLinkError

...
Unexpected error during request processing
java.lang.UnsatisfiedLinkError: init
        at org.globus.replica.rls.RLSClient.init(Native Method)
...
            

An java.lang.UnsatisfiedLinkError exception when using the WS RLS may indicate that the native RLS libraries that WS RLS depends on could not be located. To correct this problem, ensure that the $GLOBUS_LOCATION/lib directory is in the library search path (on some systems this is the LD_LIBRARY_PATH variable).

Unable to connect to localhost:39281

...
Error: java.rmi.RemoteException: globus_rls_client: Globus I/O error: 
globus_xio: Unable to connect to localhost:39281; nested exception is:
        org.globus.replica.location.CatalogInternalException: globus_rls_client:
 Globus I/O error: globus_xio: Unable to connect to localhost:39281
...
            

The WS RLS is an interface layer that depends on the RLS for the replica location functionality. You must install and run RLS and configure WS RLS to use the RLS via its JNDI configuration. Check that RLS is installed, running, and check that the WS RLS JNDI configuration uses the correct hostname and port to connect to the RLS.

org.globus.common.ChainedIOException: Failed to initialize security context

An org.globus.common.ChainedIOException exception when using the WS RLS may indicate that the user's proxy is invalid.

...
Error: ; nested exception is:
        org.globus.common.ChainedIOException: Failed to initialize security 
context [Caused by: Defective credential detected [Caused by: Proxy file 
(/tmp/x509up_u1234) not found.]]
...
            

To correct the error, the user must properly initialize the user proxy. See grid-proxy-init for more information on proxy initialization.

Error: org.xml.sax.SAXException: Unregistered type: class org.globus.replica.location.generated.ObjectEnumerationType

An org.xml.sax.SAXException: Unregistered type: class XXX exception when using the WS RLS may indicate that an Axis generated XML type, defined by the WS RLS XSD, was not properly registered. While all the XML types should get registered upon deployment without intervention by the user, sometimes they do not. To remedy the situation add a typeMapping to the $GLOBUS_LOCATION/etc/globus_wsrf_replicalocation_service/server-config.wsdd file. Note that this exception is not limited to the org.globus.replica.location.generated.ObjectEnumerationType type.

...
    <typeMapping.
        encodingStyle="".
        qname="ns1:ObjectEnumerationType".
        deserializer="org.apache.axis.encoding.ser.SimpleDeserializerFactory".
        serializer="org.apache.axis.encoding.ser.SimpleSerializerFactory"
        type="java:org.globus.replica.location.generated.ObjectEnumerationType"
        xmlns:ns1="http://www.globus.org/namespaces/2005/08/replica/location" />
...