[JUDDI-481] Bug? One of the last "2" businesses deleted, recreated the business and received juddi.rootPartition error!

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.0.4
• Fix Version/s: 3.1.0
• Component/s: juddi-tomcat
• Environment: jUDDI version 3.0.4; juddi.authenticate.Inquiry=false; juddi.authenticator = org.apache.juddi.v3.auth.JUDDIAuthenticator; Scout version 1.2.2; JDK 1.6.0 u16; Windows XP Pro 64-bit
• Assignee: Kurt Stam
• Reporter: Cli Dc
• Created: 19/May/11 05:04
• Updated: 25/May/11 12:46
• Resolved: 25/May/11 12:46

Description

I have explained this to Kurt Stam over e-mail. He encouraged to open a JIRA issue to look closely into this, and possibly resolve this bug! We need a resolution at a very high priority.

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 having "2" businesses in UDDI registry – one is our own and second is jUDDI's default business "An Apache jUDDI Node".

Then, we our delete own 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.

At that point, the new business is not created. Instead we receive an error as below 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 temporarily overcome the above error:
=================================
We overcome, for now, 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 for a possible patch to jUDDI 3.0.4 app.