Bug 779540 (SOA-1917) - Unable to start two instances of SOA-P using shared database because of jUDDI conflicts.
Summary: Unable to start two instances of SOA-P using shared database because of jUDDI...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1917
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Documentation, jUDDI - within SOA
Version: 5.0.0 ER6,5.0.0 ER7
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.1.0 GA
Assignee: Dana Mison
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-03 15:31 UTC by Marek Baluch
Modified: 2011-11-09 08:54 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-09 08:54:43 UTC
Type: Bug

Attachments (Terms of Use)
server.err2.log (135.98 KB, text/plain)
2010-02-03 15:31 UTC, Marek Baluch 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 779207 0 urgent CLOSED jUDDI does not come with SQL scripts 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 779972 0 high CLOSED Review existing clustering-related documentation - expand on existing docs' discussion of clustering JMS to cover genera... 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-1917 0 None None None Never

Internal Links: 779207 779972

Description Marek Baluch 2010-02-03 15:31:18 UTC 
project_key: SOA

When using a shared database for platform instances then I am unable to start two server instances at the same time. I must wait till the first instance finished starting then I can start the second instance.

During the initialization of a clean database it may happen that juddi 2 tries to insert data about the "root" publisher but the data is already there. The was inserted by juddi 1. If this happens then we get a ConstraintViolationException as can be seen in the attached log.
Comment 1 Marek Baluch 2010-02-03 15:31:51 UTC 
Attachment: Added: server.err2.log
Comment 2 Marek Baluch 2010-02-03 15:32:50 UTC 
Link: Added: This issue is related to SOA-1600
Comment 3 Len DiMaggio 2010-09-20 16:09:48 UTC 
Link: Added: This issue related SOA-2332
Comment 4 Anne-Louise Tangring 2010-09-21 19:37:12 UTC 
Candidate for SOA 5.1.0 Documentation.
Comment 6 Dana Mison 2011-01-05 00:12:17 UTC 
Writer: Added: Darrin
Comment 7 Dana Mison 2011-02-07 03:47:53 UTC 
added to "running more than one instance" section in the SOA GSG

"Starting multiple servers at the same time, with the same database configuration can result in database errors if the database has not been initialized previously. Database initialization is performed by the server when it is launched for the first time with a new database. If more than one server attempts to do this at the same time then errors can occur. This can be avoided by waiting until one instance has finished startup and initialized the databases before starting other instances. This only has to be done the first time that the servers are started."
Comment 8 Dana Mison 2011-02-07 03:47:53 UTC 
Release Notes Docs Status: Added: Not Required
Comment 9 Marek Baluch 2011-11-09 08:54:43 UTC 
Verified in the release notes.
Note You need to log in before you can comment on or make changes to this bug.