Hello,
The following could be a serious bug with jUDDI 3.0.4. But I am open to taking
a suggestion, if I am wrong.
The following behavior has been very (>95%) consistent.
===========
Error Scenario:
===========
jUDDI version 3.0.4
juddi.authenticate.Inquiry=false
juddi.authenticator = org.apache.juddi.v3.auth.JUDDIAuthenticator
Scout version 1.2.2
With the above settings, we start off by deleting a business in the UDDI
registry. At this point, there is only *one* default business "An Apache jUDDI
Node" in the j3_business_name table.
Then, we go ahead and recreate (save) a new business with the name *same as*
that of the business deleted earlier.
We receive the following error at that time.
=================
Error in Tomcat console:
=================
May 17, 2011 10:54:49 AM org.apache.cxf.phase.PhaseInterceptorChain
doDefaultLogging
INFO: Application
{urn:uddi-org:v3_service}UDDI_Publish_Port#{urn:uddi-org:v3_service}save_business
has thrown exception, unwinding now: org
.apache.juddi.v3.error.FatalErrorException: An error occurred attempting to
retrieve configuration information: juddi.rootPartition
========================
How we overcome the above error:
========================
We overcome the above error by doing this:
1. Shutdown jUDDI 3.0.4 instance.
2. Clean up database, delete database, delete user, recreate database, recreate
user.
3. Start jUDDI 3.0.4 instance.
4. Immediately, shutdown jUDDI 3.0.4 instance.
5. Then, again (yeah, it's crazy), restart jUDDI 3.0.4 instance.
At the end of step #5 above, we are able to recreate the business that we
deleted with no errors.
This is a painful procedure, and may need jUDDI team's immediate attention.
