[
https://issues.apache.org/jira/browse/VYSPER-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258151#comment-13258151
]
Pedro Romão Pereira commented on VYSPER-309:
--------------------------------------------
I had the same problem with Emite, but it was an error on Emite. Because after
the SASL negotiation ends succesfully, the server sends a stanza with the
features and if the bind feature is present the client must bind a resource.
Emite tries to bind the resource right after the SASL negotiation, before it
receives the feature stanza. When the feature stanza arrives Emite is already
waiting for the bind response and looses context.
> BOSH plugin does not always send or recieve messages from client
> ----------------------------------------------------------------
>
> Key: VYSPER-309
> URL: https://issues.apache.org/jira/browse/VYSPER-309
> Project: VYSPER
> Issue Type: Bug
> Components: BOSH
> Affects Versions: 0.7
> Environment: Tomcat 7.0.25 / Tomcat 7.0.27 / Jetty 8.1.2
> Reporter: Stig Runar Vangen
>
> The BOSH extension does not always return a result from a request. I saw the
> same behavior using both the Jetty Continuation API's and the Servlet 3.0
> API's. The result of this is that Emite (http://code.google.com/p/emite/)
> never finished logging in. I also tried using Pidgin (http://www.pidgin.im/),
> which has BOSH support if you enable it. Using Pidgin I was able to log in
> successfully, but chatting was a bit problematic. Sending a message to the
> server wasn't noticed by the server using an already open async request. I
> know the server never received the message as I had enabled both console
> logging of all BOSH messages as well as database logging of all chat
> messages. When Piding lost the connection and created a new one however, the
> message was resent, and the message got through. I then also received pending
> messages from others.
--
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
