You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sandesha-dev@ws.apache.org by "Hans G Knudsen (JIRA)" <ji...@apache.org> on 2007/12/18 13:21:43 UTC
[jira] Resolved: (SANDESHA2-118) Two RMSBeans can have same
'Internal Sequence Id'
[ https://issues.apache.org/jira/browse/SANDESHA2-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hans G Knudsen resolved SANDESHA2-118.
--------------------------------------
Resolution: Fixed
This was fixed for 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, 1.3
> Environment: Axis2/Sandesha2 1_2 + 1_3 - server side - with sync RM...
> Reporter: Hans G Knudsen
> Fix For: 1.3
>
> 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