JBoss.orgCommunity Documentation

Chapter 10. Troubleshooting jUDDI

Table of Contents

10.1. jUDDI Web Services, juddiv3.war
10.1.1. Enable debugging logging
10.2. jUDDI GUI, juddi-gui.war
10.3. jUDDI Client Java
10.3.1. Enable debugging logging
10.4. jUDDI Client .NET
10.5. Getting help

Here are some tips to help you troubleshoot problems with jUDDI, jUDDI-GUI, jUDDI Client and more.

Problem: Can’t authentication from juddi-gui’s top right hand side login box to juddiv3.war services Solutions:

Components based on jUDDI’s Client for the .NET Framework can configure logging from their application’s config file. This is usually app.config or web.config. To configure logging, the following three settings must appear in the configuration/appSetttings section.

	<add key="org.apache.juddi.v3.client.log.level" value="INFO" />
    <!-- options are CONSOLE, EVENTLOG, FILE multiple values can be specified, comma delimited.
		Notes for EVENTLOG, you must run the juddi-installer as admin before running-->
    <add key="org.apache.juddi.v3.client.log.target" value="CONSOLE" />
	<!-- only used when target=FILE -->
    <add key="org.apache.juddi.v3.client.log.logger.file" value="pathToOutputFile" />

If nothing is defined, the default log level is "WARN" and the target is "CONSOLE" which is standard out.

There are many different ways to get help with your jUDDI instance. Please refer to the following URLs for more information.