[
https://issues.apache.org/jira/browse/VYSPER-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann updated VYSPER-185:
------------------------------------
Attachment: VYSPER-185.2.patch
Please see if this patch is behaving more correctly for your use case.
Additionally, please note that this is not a sufficient committable patch
because:
+ patch is largely untested
+ endSession() is called not only on session abortion, but also in other cases,
where sending unavail to the session client is not allowed
+ we should not send unavail to the initiating entity, only to contacts
+ when we are not in session abortion case, we should send </stream:stream>
> 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
> Priority: Minor
> 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.
-
You can reply to this email to add a comment to the issue online.
