[
https://issues.apache.org/jira/browse/VYSPER-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263144#comment-13263144
]
Paul Clare commented on VYSPER-309:
-----------------------------------
Apologies but I still did not describe it quite right.
synchronized (session) {
session.insertRequest(br);
for (;;) {
// When a request from the user comes in, it is possible
that the request fills a gap
// created by previous lost request, and it could be
possible to process more than the current request
// continuing with all the adjacent requests.
br = session.getNextRequest();
if (br == null) {
break;
}
processSession(session, br);
}
}
processSession() will never get invoked because getNextRequest() will always
return null in this case.
> 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
