[
https://issues.apache.org/jira/browse/SANDESHA2-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hans G Knudsen updated SANDESHA2-118:
-------------------------------------
Environment: Axis2/Sandesha2 1_2 + 1_3 (was: Axis2/Sandesha2 1_2)
Have not found the error as above - but on 1_3 - i saw a similar bug trying to
provoke it.
If two clients creates a new session simultaneously with the same Offer - two
RMS beans can be inserted with the same Seqeuence Id.
As in CreateSeqMsgProcessor - 'offerAccepted' cound check for existence of bean
with the Seq Id for both requests - before one of the session inserts it..
> 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
> Reporter: Hans G Knudsen
> Priority: Blocker
>
> I have a logging where 2 rmsbeans are found to be equal in
> InMemoryBeanMgr.findUnique
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
