Why are the jUDDI v3 tables recreated at each SOA-P startup?

Issue

• JBoss is creating new schema objects each time the SOA-P 5 server is restarted. Why is this happening and how can it be prevented?

• We have a 2 node SOA-P cluster with all the same services, both running jUDDI and both using the same database for jUDDI. As each node starts up it overwrites the jUDDI repository with only its endpoints.