What about updating the statement that caused the duplicate key violation to be
a warning by changing the following:
in clustered-mysql-persistence-service.xml:
POPULATE.TABLES.1=INSERT INTO JBM_USER (USER_ID,PASSWD,CLIENTID) VALUES
('dilbert','dogbert','dilbert-id')
to:
POPULATE.TABLES.1=INSERT IGNORE INTO JBM_USER (USER_ID,PASSWD,CLIENTID) VALUES
('dilbert','dogbert','dilbert-id')
which allows MySQL to return an warning instead of returning an error and
aborting the statement.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056123#4056123
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056123
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
