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 "David Illsley (JIRA)" <ji...@apache.org> on 2008/08/18 15:31:45 UTC

[jira] Closed: (SANDESHA2-152) MakeConnections not finding createSeq Msg to send when security enabled

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

David Illsley closed SANDESHA2-152.
-----------------------------------

    Resolution: Fixed

> MakeConnections not finding createSeq Msg to send when security enabled
> -----------------------------------------------------------------------
>
>                 Key: SANDESHA2-152
>                 URL: https://issues.apache.org/jira/browse/SANDESHA2-152
>             Project: Sandesha2
>          Issue Type: Bug
>            Reporter: Dave Parsons
>         Attachments: ImproveSecureMakeConnProcessing.patch
>
>
> When a secure makeConnection arrives at a provider the MakeConnectionProcessor finds all RMS & RMD Beans that match the security token in the makeConnection msg.  It then goes on to pick one of the beans it has found at random and then selects a random senderbean from the RMS or RMD Bean chosen.  If there are no senderbeans it does nothing and returns.
> I'm finding that the client can occasionally timeout because the RMS or RMD bean selected has no senderbeans while the unselected one does.
> To solve the problem I propose that in the secure scenario it should randomly pick an RMS or RMD bean but if it doesn't find any senderbeans on that RMS or RMD bean it should try to find senderbeans on one of the other RMS or RMD beans.

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