ws-sandesha-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chamikara Jayalath (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SANDESHA2-118) Two RMSBeans can have same 'Internal Sequence Id'
Date Mon, 10 Sep 2007 04:44:29 GMT

     [ https://issues.apache.org/jira/browse/SANDESHA2-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chamikara Jayalath updated SANDESHA2-118:
-----------------------------------------

    Priority: Major  (was: Blocker)

I've fixed the 1.3 issue with my last commit. Added a function to check for key conflicts
when inserting entries.
Reducing the priority of this Issue since rest it's a 1.2 issue and since we are now more
concerned about the 1.3 release.

> Two RMSBeans can have same 'Internal Sequence Id'
> -------------------------------------------------
>
>                 Key: SANDESHA2-118
>                 URL: https://issues.apache.org/jira/browse/SANDESHA2-118
>             Project: Sandesha2
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: Axis2/Sandesha2 1_2 + 1_3 - server side - with sync RM...
>            Reporter: Hans G Knudsen
>         Attachments: storage_manager_constraing.txt
>
>
> I have a logging where 2 rmsbeans are found to be  equal in InMemoryBeanMgr.findUnique
- on server side
> The logging shows that 
> Internal Seq Id  : Sandesha2InternalSequence:urn:uuid:16F6AC7844CFEFE6C61187856973547
> are equal for both beans...
> I will try to find out if this is still the case for the 1_3 branch....

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org


Mime
View raw message