we're trying to get BB working but fail. Our latest results are these nice exceptions in the standalone Jetty on a seperate server:
Code: Select all
WARNING: BlueBox<->SFS Handshake failure!
Sep 18, 2010 7:17:14 AM it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter doFilter
WARNING: BlueBox<->SFS Handshake failure!
Sep 18, 2010 7:17:15 AM it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter doFilter
WARNING: BlueBox<->SFS Handshake failure!
2010-09-18 07:17:15.282:WARN::Error for /BlueBox/HttpBox.do
java.lang.NoClassDefFoundError: org/mortbay/util/ajax/ContinuationSupport
at it.gotoandplay.smartfoxserver.httpbox.HttpBox.handlePollingRequest(HttpBox.java:330)
at it.gotoandplay.smartfoxserver.httpbox.HttpBox.doPost(HttpBox.java:166)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:527)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1216)
at it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter.doFilter(SessionIDFilter.java:195)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1187)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:421)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:456)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:225)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:930)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:358)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:183)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:866)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:245)
at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113)
at org.eclipse.jetty.server.Server.handle(Server.java:351)
at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:594)
at org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:1059)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:764)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:217)
at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:424)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:506)
at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436)
at java.lang.Thread.run(Thread.java:619)
Sep 18, 2010 7:17:17 AM it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter doFilter
WARNING: BlueBox<->SFS Handshake failure!
Our situation:
1. server "A" with Jetty on port 80 on IP address 1.2.3.4 (example)
2. same server "A" has other services on ports 80 and other IP's ; that work
3. seperate SFS server "B" PRO with BlueBox license and updated license file on IP address 2.2.2.2 , SFS listens on port 9339
4. server A and B are at the same provider , in different subnets , but both on 1 Gbit , the ping between machines is 0.2 millisec
5. We run a stand-alone jetty 6 , not a debian package, installed bluebox.properties as instructed. Inside the properties file the IP of the SFS server and the port of the SFS server are filled in. The mode is 'stand-alone'.
The debug HttpBox.do works and sometimes shows output like this:
Code: Select all
BlueBox Debugging Page
Logging level: FINER
Client idle time: 30
Client idle request time: 300
Active sessions: 1
SessionId Q Size Creation Last Act. Last Req.
8f558a25d4f88bd190bccb71fafd4390 4 7:20:48 7:21:49 7:21:49
( BlueBox beta debugger )
However the users cannot connect with BlueBox (we test by blocking outgoing traffic to port 9339 with IPSec) ; after say 5-10 seconds everyone gets disconnected.
We see these kind of messages in the jetty-console:
Code: Select all
WARNING: BlueBox<->SFS Handshake failure!
Sep 18, 2010 7:21:49 AM it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter doFilter
WARNING: BlueBox<->SFS Handshake failure!
Sep 18, 2010 7:21:49 AM it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter doFilter
WARNING: BlueBox<->SFS Handshake failure!
Sep 18, 2010 7:21:58 AM it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter doFilter
WARNING: BlueBox<->SFS Handshake failure!
Sep 18, 2010 7:22:22 AM it.gotoandplay.smartfoxserver.httpbox.ConnectionManager disposeClients
INFO: Disposed session: 8f558a25d4f88bd190bccb71fafd4390, 4
Sep 18, 2010 7:22:22 AM it.gotoandplay.smartfoxserver.httpbox.SFSConnectionHandler onClose
INFO: Disconnected: IP: 77.169.161.19 - SessID: 8f558a25d4f88bd190bccb71fafd4390
There are no errors in the SFS console output.
The SFS server (9339) is bound to a specific IP , the embedded Jetty of that SFS server is running on port 80 of that IP. We have other services (NGINX) running on port 80 (other IP).
I'm not trying to use Jetty or BB behind a proxy, APache_mod or something. Every service has it's own IP and port. All services are bound correctly to it's assigned IP and port. "netstat -an | grep LISTEN" show that every service is running normally.
Our SFS server "A" runs fine (50k users a day minimum), embedded Jetty of SFS runs fine. The HttpBox.do page on server "B" shows output and even sessions.
All servers have 1 gbit public connectors and are not overloaded. Average ping to a user is 20 ms. All tests were done with normal systems on decent lines. There is no network-issue between server and clients or between the servers themselves.
Any tips ?
[/code]