Hi Kurt,
No, I am not removing/updating the default business. I am not.
Shortly rephrased, we have "2" businesses in UDDI registry -- one is our own
and second is jUDDI's default business.
Then, we start off by deleting our 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 (our own business)
deleted earlier.
At that point, the new business is *not* created. Instead we receive an error
as below:
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
Hope this information makes sense. All this happens about 95% of times. Is
there a patch to address this issue? Can we apply that patch to our jUDDI
3.0.4 installation so that this error won't repeat? Thanks Kurt.
From: Kurt T Stam
Subject: Re: Bug? Last business deleted, recreate business and
juddi.rootPartition error!
To: [email protected]
Cc: [email protected]
Date: Tuesday, May 17, 2011, 12:29 PM
So am I correct in reading that you are removing or updating the
default business?
The jUDDI services themselves are owned by the default business. If
you delete/update that business, you will run into issues (as you
have found out). If you don't like the info associated with the
default business, you can update the root seed data. Then on startup
make sure to start with en empty database so that new root seed data
gets read in.
See also chapter 5 of the user guide:
http://juddi.apache.org/docs/3.0/userguide/html/chap-root_seed_data.html
And yes if you clean out the database, then in your step 5 it
restores all the data from the root seed data and all will work
again..
--Kurt
On 5/17/11 11:18 AM, CLI wrote:
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.
