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/07/06 14:15:34 UTC

[jira] [Resolved] (VYSPER-185) Send unavailable on lost connection

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

Bernd Fondermann resolved VYSPER-185.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.8

this has been fixed when endSession() is now called instead of close()
                
> Send unavailable on lost connection
> -----------------------------------
>
>                 Key: VYSPER-185
>                 URL: https://issues.apache.org/jira/browse/VYSPER-185
>             Project: VYSPER
>          Issue Type: Bug
>          Components: core protocol
>            Reporter: Thomas Kratz
>            Assignee: Bernd Fondermann
>            Priority: Minor
>             Fix For: 0.8
>
>         Attachments: AbstractSessionContext.java.patch, VYSPER-185.2.patch
>
>
> If the clients drops the connection or connection gets broken, an anavailable should be sent out to other parties. I need this fix, because I manage license based on the presence of users and if a client breaks down (yes it does sometimes, its eclipse based) I need to release the license. I'll attach a pacth for this (is state of my work) and kindly ask you to have a look at it. It currently breaks 
>   testProcessUnknownStanza(org.apache.vysper.xmpp.protocol.ProtocolWorkerProcess
> TestCase)
> and I don't have deep enough understanding why this happens.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira