You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@juddi.apache.org by Lars Pedersen <s9...@com.dtu.dk> on 2004/08/19 05:01:43 UTC

Setup problems: juddi returns faultstring every time

Hi, I feel I am really close to getting jUDDI to work. Still, there's
one little problem... I have looked through every post on this list to
work it out, but no luck!

I use jUDDI 0.9 with Tomcat 4.1.3 and MySQL.

The problem is this: the client programs, both the UDDI4J ones and Sun's
JAXR examples including the registry browser, only get this SOAP message
when calling jUDDI:

<?xml version="1.0" encoding="utf-8"?>
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <soapenv:Body><Fault><faultstring/></Fault> </soapenv:Body>
</soapenv:Envelope>

The UDDI4J programs translate this message into an exception like this:

Get authtoken
	at org.uddi4j.UDDIElement.<init>(Unknown Source)
	at org.uddi4j.response.AuthToken.<init>(Unknown Source)
	at org.uddi4j.client.UDDIProxy.get_authToken(Unknown Source)
	at BusinessEntityExample.run(BusinessEntityExample.java:76)

The jwsdp1.3 example programs give me this:

javax.xml.registry.JAXRException: javax.xml.bind.UnmarshalException
 - with linked exception:
[org.xml.sax.SAXParseException: unexpected root element (uri:"",
local:"Fault"). Expected elements are
<{urn:uddi-org:api_v2}relatedBusinessInfo>,<{urn:uddi-org:api_v2}email>,
<{urn:uddi-org:api_v2}authInfo>,	 ...
<{urn:uddi-org:api_v2}get_tModelDetail>]
	at
com.sun.xml.registry.uddi.Processor.processResponseJAXB(Unknown Source)
	at
com.sun.xml.registry.uddi.Processor.processRequestJAXB(Unknown Source)
	at
com.sun.xml.registry.uddi.UDDIMapper.getAuthorizationToken(Unknown
Source)
	at
com.sun.xml.registry.uddi.ConnectionImpl.setCredentials(Unknown Source)
	at
SaveOrganizationTest.executeTest(SaveOrganizationTest.java:68)

The happiness page has no errors. That must mean the database is
connected, right? It has a user: juddi, password: juddi with all
privileges.

I want to look at the juddi.log file to see what is going wrong. But for
some reason, I do not have a the file on my system. Even though my
Log4j.properties file contains this line:
	log4j.appender.LOGFILE.File=juddi.log

But Tomcat's log file, which I find in \Tomcat 4.1\logs, contains no
errors as far as I can see:

.....
2004-08-19 04:38:01 StandardContext[/juddi]: Mapping
contextPath='/juddi' with requestURI='/juddi/publish' and
relativeURI='/publish'
2004-08-19 04:38:01 StandardContext[/juddi]:   Trying exact match
2004-08-19 04:38:01 StandardContext[/juddi]:  Mapped to servlet
'jUDDIPublishServlet' with servlet path '/publish' and path info 'null'
and update=true

I hope this rings a bell with someone???

/Lars