You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Bernd Fondermann (JIRA)" <ji...@apache.org> on 2012/10/23 11:41:18 UTC
[jira] [Closed] (VYSPER-323) (VYSPER-275) Race condition in stanza
handling - How does this affect the BoshEndpoint ?
[ https://issues.apache.org/jira/browse/VYSPER-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bernd Fondermann closed VYSPER-323.
-----------------------------------
Resolution: Not A Problem
Don't know what to do with this JIRA
> (VYSPER-275) Race condition in stanza handling - How does this affect the BoshEndpoint ?
> -----------------------------------------------------------------------------------------
>
> Key: VYSPER-323
> URL: https://issues.apache.org/jira/browse/VYSPER-323
> Project: VYSPER
> Issue Type: Question
> Affects Versions: 0.8
> Reporter: Paul Clare
>
> Currently the BoshHandler places stanzas directly in the StazaProcessor which prior to fix 275 was a QueuedStazaProcessor with an underlying ExecutorService. and as a result, the calls will not block but are likely to have sequencing issues.
> 275 replaces the QueuedStazaProcessor with a ProtocolWorker in favor of moving the ExecutorService to the TCPEndpoint.
> I am hoping to get some thoughts on the impact of removing the QueuedStazaProcessor from the BoshHandler which will make it a blocking call on the ProtocolWorker.
> BoshHandler.processStanza() {
> serverRuntimeContext.getStanzaProcessor().processStanza(
> serverRuntimeContext, session, stanza, session.getStateHolder());
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira