Chapter 7 Troubleshooting

This chapter describes solutions to some problems that you can encounter when using JAXR with Service Registry.

• “Message Send Failed” Error from Service Registry

• Unable to Create ExternalLink or ServiceBinding

• FileNotFoundException for Keystore File

See Known Issues and Bugs in Service Registry 3.1 Release Notes for details about other problems you might encounter, along with workarounds.

“Message Send Failed” Error from Service Registry

If you run a program and get a stack trace with a Message send failed error, the probable reason is that the Registry is not running or that the specified URL is incorrect. The beginning of the stack trace looks like this:

[java] Jul 10, 2006 10:23:09 PM com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection post
[java] SEVERE: SAAJ0009: Message send failed
[java] com.sun.xml.messaging.saaj.SOAPExceptionImpl: java.security.PrivilegedActionException: 
com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed

Make sure that the host name and port in INSTALL/registry-samples/common/build.properties are correct for your installation.

To make sure that the Registry is running, use the command-line or web interface to the Application Server domain for the Registry. For details, see Administering the Application Server Domain for Service Registry in Service Registry 3.1 Administration Guide.

Unable to Create ExternalLink or ServiceBinding

You might get an error in one of the following situations, even if you have specified the system properties http.proxyHost and http.proxyPort:

• When you specify an External URI for an ExternalLink object

• When you specify an Access URI for a ServiceBinding object

The error message looks like this:

The URL: uri is not resolvable. 
Use Absolute Path Format [scheme:][//authority][path][?query][#fragment]

This error means that the administrative task described in Configuring the Java Virtual Machine (JVM) for the Registry Domain in Service Registry 3.1 Administration Guide has not been performed. The Service Registry administrator for your site needs to perform this task and restart the Registry before you can create these objects.

FileNotFoundException for Keystore File

An error like the following indicates that you did not create a keystore file:

[java] Query URL is http://localhost:6480/soar/registry/soap
[java] Created connection to registry
[java] java.io.FileNotFoundException: 
/home/myname/soar/3.0/jaxr-ebxml/security/keystore.jks (No such file or directory)

If you see this error, follow all the procedures described in the section Getting Access to the Registry.