standalone BB to SFS on other server ; exceptions

Submit all your BlueBox related questions or report a bug here!

Moderators: Lapo, Bax

m4io
Posts: 7
Joined: 22 Jan 2009, 14:32

standalone BB to SFS on other server ; exceptions

Postby m4io » 18 Sep 2010, 04:54

Hi,

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]
m4io
Posts: 7
Joined: 22 Jan 2009, 14:32

Postby m4io » 18 Sep 2010, 05:04

This is the client-side debug output.

At first the client tries to connect to the default port 9339 which is not allowed and then the client tries to connect to the bluebox port (on the seperate machine).

Warning: Timeout on xmlsocket://live2.xxxx.com:843 (at 3 seconds) while waiting for socket policy file. This should not cause any problems, but see http://www.adobe.com/go/strict_policy_files for an explanation.
Warning: Timeout on xmlsocket://live2.xxxxx.com:9339 (at 3 seconds) while waiting for socket policy file. This should not cause any problems, but see http://www.adobe.com/go/strict_policy_files for an explanation.
Error: Request for resource at xmlsocket://live2.xxxxxxxx.com:9339 by requestor from http://live1files.xxxxxxxxxx.com/xxxxxx ... 2010_13_50 has failed because the server cannot be reached.
*** Security Sandbox Violation ***
Connection to live2.xxxxxx.com:9339 halted - not permitted from http://live1files.xxxxxxx.com/xxxxxx/li ... 2010_13_50
Socket connection failed. Trying BlueBox
[ Send ]: sfsHttp=connect
Warning: Domain bluebox.xxxxxx.com does not specify a meta-policy. Applying default meta-policy 'master-only'. This configuration is deprecated. See http://www.adobe.com/go/strict_policy_files to fix this problem.
[Sending]: <msg t='sys'><body action='verChk' r='0'><ver v='161' /></body></msg>

[ Send ]: sfsHttp=8d3ff4112248839586e08916c9c16854%3Cmsg%20t%3D%27sys%27%3E%3Cbody%20action%3D%27verChk%27%20r%3D%270%27%3E%3Cver%20v%3D%27161%27%20%2F%3E%3C%2Fbody%3E%3C%2Fmsg%3E
[ RECEIVED ]: <cross-domain-policy><allow-access-from domain='*' to-ports='9339' /></cross-domain-policy>, (len: 91)
[ RECEIVED ]: <msg t='sys'><body action='apiOK' r='0'></body></msg>, (len: 53)
Login Zone18 f2d75bd78151a359 bqe9vbpt1ad1fa0w
[Sending]: <msg t='sys'><body action='login' r='0'><login z='Zone18'><nick><![CDATA[f2d75bd78151a359]]></nick><pword><![CDATA[bqe9vbpt1ad1fa0w]]></pword></login></body></msg>

[ Send ]: sfsHttp=8d3ff4112248839586e08916c9c16854%3Cmsg%20t%3D%27sys%27%3E%3Cbody%20action%3D%27login%27%20r%3D%270%27%3E%3Clogin%20z%3D%27Zone18%27%3E%3Cnick%3E%3C%21%5BCDATA%5Bf2d75bd78151a359%5D%5D%3E%3C%2Fnick%3E%3Cpword%3E%3C%21%5BCDATA%5Bbqe9vbpt1ad1fa0w%5D%5D%3E%3C%2Fpword%3E%3C%2Flogin%3E%3C%2Fbody%3E%3C%2Fmsg%3E
HttpError


After the HttpError the log is silent forever.

All connections between the servers have been checkend, all ports can be reached, from server A to server B and vice versa.

Grazie.
Last edited by m4io on 10 Nov 2010, 01:40, edited 1 time in total.
m4io
Posts: 7
Joined: 22 Jan 2009, 14:32

Postby m4io » 18 Sep 2010, 07:13

Update: We were using Jetty 7 which causes this error:

2010-09-18 07:17:15.282:WARN::Error for /BlueBox/HttpBox.do
java.lang.NoClassDefFoundError: org/mortbay/util/ajax/ContinuationSupport

We switched back to Jetty 6 but still have handshake errors.

Some part of the log of Jetty 6 :

Code: Select all

Sep 18, 2010 9:42:09 AM it.gotoandplay.smartfoxserver.httpbox.ConnectionManager disposeClients
INFO: Disposed session: 34380e736fb1c3e174f0669bb222c559, 1
Sep 18, 2010 9:42:09 AM it.gotoandplay.smartfoxserver.httpbox.SFSConnectionHandler onClose
INFO: Disconnected: IP: 194.105.120.70 - SessID: 34380e736fb1c3e174f0669bb222c559
Sep 18, 2010 9:42:10 AM it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter doFilter
WARNING: BlueBox<->SFS Handshake failure!
Sep 18, 2010 9:42:11 AM it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter doFilter
WARNING: BlueBox<->SFS Handshake failure!
Sep 18, 2010 9:42:13 AM it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter doFilter
WARNING: BlueBox<->SFS Handshake failure!
Sep 18, 2010 9:42:16 AM it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter doFilter
WARNING: BlueBox<->SFS Handshake failure!
Sep 18, 2010 9:42:17 AM it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter doFilter
WARNING: BlueBox<->SFS Handshake failure!
Sep 18, 2010 9:42:34 AM it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter doFilter
WARNING: BlueBox<->SFS Handshake failure!
Sep 18, 2010 9:42:49 AM it.gotoandplay.smartfoxserver.httpbox.ConnectionManager disposeClients
INFO: Disposed session: 46a4c02eb2bb992f4f42ea8d60e388e9, 0
Sep 18, 2010 9:42:49 AM it.gotoandplay.smartfoxserver.httpbox.SFSConnectionHandler onClose
INFO: Disconnected: IP: 77.249.77.12 - SessID: 46a4c02eb2bb992f4f42ea8d60e388e9
Sep 18, 2010 9:43:59 AM it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter doFilter
WARNING: BlueBox<->SFS Handshake failure!
Sep 18, 2010 9:44:04 AM it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter doFilter
WARNING: BlueBox<->SFS Handshake failure!
Sep 18, 2010 9:44:04 AM it.gotoandplay.smartfoxserver.httpbox.SFSConnectionHandler onConnect
INFO: Connected: IP: 81.207.211.38 - SessID: c5d8d50a3e344cf20cf26847d945be67
Sep 18, 2010 9:44:09 AM it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter doFilter
WARNING: BlueBox<->SFS Handshake failure!
Sep 18, 2010 9:44:14 AM it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter doFilter
WARNING: BlueBox<->SFS Handshake failure!
Sep 18, 2010 9:44:14 AM it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter doFilter
WARNING: BlueBox<->SFS Handshake failure!
Sep 18, 2010 9:44:19 AM it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter doFilter
WARNING: BlueBox<->SFS Handshake failure!
Sep 18, 2010 9:44:44 AM it.gotoandplay.smartfoxserver.httpbox.ConnectionManager disposeClients
INFO: Disposed session: c5d8d50a3e344cf20cf26847d945be67, 0
Sep 18, 2010 9:44:44 AM it.gotoandplay.smartfoxserver.httpbox.SFSConnectionHandler onClose
INFO: Disconnected: IP: 81.207.211.38 - SessID: c5d8d50a3e344cf20cf26847d945be67
User avatar
Lapo
Site Admin
Posts: 20277
Joined: 21 Mar 2005, 09:50
Location: Italy

Postby Lapo » 18 Sep 2010, 08:55

Thanks for the (tons of) details :)
For starters... the BlueBox does not work with Jetty 7, you will need to stick with Jetty 6.
Second thing, if the BlueBox is a licensed one you will need to get in touch with our sales department and require a change of IP address in the license.
By default the BBox communicates with SFS exclusively via the localhost address. So that needs to be changed and it should solve your problems.

Hope it helps
Lapo
--
gotoAndPlay()
...addicted to flash games
m4io
Posts: 7
Joined: 22 Jan 2009, 14:32

Postby m4io » 18 Sep 2010, 09:25

We are running with Jetty 6 as mentioned in the 2nd post.

We received a new license yesterday and it has been installed.

However still only handshake failures.
User avatar
Lapo
Site Admin
Posts: 20277
Joined: 21 Mar 2005, 09:50
Location: Italy

Postby Lapo » 18 Sep 2010, 15:59

Sending both messages here and via email is not going to help maintain a record of what's going on.
Please let's keep with the emails since this is a problem that is very specific to your setup.
Lapo

--

gotoAndPlay()

...addicted to flash games
m4io
Posts: 7
Joined: 22 Jan 2009, 14:32

Postby m4io » 02 Oct 2010, 17:24

We solved the problem ourselves. Had to add source-routing on the standalone BB box since it used it's main IP instead of the IP BB is listening on. Imho a BB issue but some might want to blame ip-aliasing of Linux.

Anyway if you ask for a BB license make sure you ask for the main IP of your BB box in the license. Or use source-routing towards your SFS box.

Return to “BlueBox”

Who is online

Users browsing this forum: No registered users and 1 guest