Http-bind: connection closing without the correct response

When the server gets a new request whilst holding the maximum number allowed (HOLD=1), instead of closing the open request with an empty body tag and an HTTP 200 OK response, it simply closes the connection, leaving my application (Flash) to report that the post was a failure leaving me with no way to know if the connection was lost and whether the post actually worked, which it did.

Do you see any errors in the logs? Which version of Wildfire are you using?

Thanks,

Alex

version: 3.2.0 RC2

(removed auditing errors)

Message was edited by: Pokoyo

This log is stderror.log

2498 INFO org.mortbay.log - Logging to org.slf4j.impl.SimpleLogger(org.mortbay.log) via org.mortbay.log.Slf4jLog

2633 INFO org.mortbay.log - jetty-6.1.x

4127 INFO org.mortbay.log - Started SelectChannelConnector @ 192.168.0.115:8080

6797 INFO org.mortbay.log - Started HttpBindManager$JiveSslConnector @ 192.168.0.115:8443

7042 INFO org.mortbay.log - jetty-6.1.x

8648 INFO org.mortbay.log - Started SelectChannelConnector @ 192.168.0.115:9090

8650 INFO org.mortbay.log - Started AdminConsolePlugin$JiveSslConnector @ 192.168.0.115:9091

180787 ERROR org.mortbay.log - Error for /http-bind/

java.lang.InternalError: Could not locate connection: 111111117

at org.jivesoftware.wildfire.http.HttpSession.getResponse(HttpSession.java:329)

at org.jivesoftware.wildfire.http.HttpBindServlet.isContinuation(HttpBindServlet.j ava:117)

at org.jivesoftware.wildfire.http.HttpBindServlet.doPost(HttpBindServlet.java:77)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491)

at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367)

at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185)

at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)

at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689)

at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391)

at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollect ion.java:146)

at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)

at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)

at org.mortbay.jetty.Server.handle(Server.java:285)

at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:457)

at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:351)

at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:329)

at org.mortbay.jetty.nio.SelectChannelConnector$RetryContinuation.run(SelectChanne lConnector.java:389)

at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)

221800 ERROR org.mortbay.log - Error for /http-bind/

java.lang.InternalError: Could not locate connection: 111111120

at org.jivesoftware.wildfire.http.HttpSession.getResponse(HttpSession.java:329)

at org.jivesoftware.wildfire.http.HttpBindServlet.isContinuation(HttpBindServlet.j ava:117)

at org.jivesoftware.wildfire.http.HttpBindServlet.doPost(HttpBindServlet.java:77)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491)

at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367)

at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185)

at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)

at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689)

at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391)

at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollect ion.java:146)

at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)

at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)

at org.mortbay.jetty.Server.handle(Server.java:285)

at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:457)

at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:351)

at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:329)

at org.mortbay.jetty.nio.SelectChannelConnector$RetryContinuation.run(SelectChanne lConnector.java:389)

at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)

I’'ve just been watching the headers and an odd status is being returned:

HTTP/1.x 200 Could_not_locate_connection_111111121

it should be

HTTP/1.x 200 OK

Message was edited by: Pokoyo

The “Could_not_locate” bit first comes as an internal error code in the headers:

HTTP/1.x 500 Could_not_locate_connection_111111120

I am checking in a fix for this issue now:

JM-955

It will be in the final release of Wildfire. You will also see it in the next nightly build if you would like to test it before the final release.

Thanks,

Alex