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=I
I have never used MySQL cluster, but if it is accessed using the normal JDBC
API then JBoss Messaging won't think of it any differently than any other JDBC
implementation - JBM will be completely unaware it is talking to "MySQL
cluster".
If MySQL starts failing then sounds like a bug or misconf
