[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1682) duplicate key value violates unique constraint "jbm_msg_pkey" exceptions in a clustered

[Howard Gao (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBMESSAGING-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12475712#action_12475712 ] 

Howard Gao commented on JBMESSAGING-1682:
-----------------------------------------

Thanks Tim, I had a look at it and I think the idea is to drop the time bits and use check points.

So the idea would be:

[10 bits node-id][54 bits counter]

This eliminates the time issue. But we need:

create a table in the DB, store checkpoints for each node.

It looks like a simple solution, I'll try this way. 

Comments?

Howard


> duplicate key value violates unique constraint "jbm_msg_pkey" exceptions in a clustered
> ---------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1682
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1682
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.SP3.CP07, 1.4.0.SP3.CP08, 1.4.4.GA
>            Reporter: Masao Kato
>            Assignee: Howard Gao
>            Priority: Blocker
>             Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
>
>
> NodeID(server peer id) of the cluster : in the adjoined identification number such as 0 and 1, 2 and 3. 
> When message ID is generated at the same time, the exception might be generated by the duplicate of ID. 

-- 
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