[
https://jira.jboss.org/jira/browse/JBESB-3286?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-3286:
-------------------------------------
We had "update" in there initially, but were advised not to use it and that we
should change it to "create" instead.
The downside of this is that it does delete the database on startup, which is problematic
in a cluster.
We definitely need to handle this better.
Having the value "create" for the Juddi persistence.xml
"hibernate.hbm2ddl.auto" property breaks the juddi Dabase in a ESB cluster
-----------------------------------------------------------------------------------------------------------------------------------
Key: JBESB-3286
URL:
https://jira.jboss.org/jira/browse/JBESB-3286
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Registry and Repository
Affects Versions: 4.8
Environment: JBoss ESB 4.7 CP1 or 4.8 cluster with at least two JBoss ESB
instances sharing the same Juddi database
Reporter: Maurice Zeijen
In a ESB cluster, with a shared Juddi DB, the value "create" for the Juddi
persistence.xml "hibernate.hbm2ddl.auto" property causes the juddi database to
be recreated after every JBoss ESB Instance is started. This results in the removal of the
service registration of the JBoss ESB that was started first.
The following happens:
- JBoss ESB server 1 starts
- Tables in the Juddi database get created
- Registry entries of JBoss ESB server 1 are created in the Juddi database
- JBoss ESB server 2 starts
- All records in the existing tables of the Juddi database are deleted.
- Registry entries of JBoss ESB server 2 are created in the Juddi database
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira