Hi
I am having a little problem with bluebox after i updated to 1.6.
when i block the normal port to test bluebox. my client sends connect and receives status 200 ,but after that nothing happens.
(status 200 should indicate that the request was successful right?)
i have tested to do the same with the AdvancedChat example but i get almost the same result there. the only difference is that the status message don't appear
i downloaded the latest API and tried again this time i didn't receive the status 200 it just stopped at send connect.
anyway after some testing i figured out that it when i ran it on my local computer everything worked fine but when i tested it on my server it did not.
i tested the debug URL that was written in one of the config files and it gave me a 500 error i don't know what it means but hopefully you do
when i ran it locally i only got a small page with the header BlueBox Debugging Page
I also want to add that the reloading of java extension is not working for me. the only way to reload a java extension is to restart the server and that's pretty annoying since i am trying to test out some new extensions i am making
Hi, this problem was also notified by another client. We investigated and found a possible problem that makes this exception intermittent
You have an update in your mail box
that new file solved 1 of the 2 errors that the debugger showed now there only one but i still don't have a clue about what is causing it, and how to fix it. Here's the link and error:
HTTP ERROR: 500
INTERNAL_SERVER_ERROR
RequestURI=/BlueBox/HttpBox.do
Caused by:
java.lang.NullPointerException
at it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter.doFilter(SessionIDFilter.java:110)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
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:502)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:821)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:208)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:378)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:368)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
Powered by Jetty://
Yes, I tried the patch. But I will try it again and post the result here.
-----------
I tried the patch (new .war file and API's), HttpBox.do file still gives the error specified below.
---------------------------
HTTP ERROR: 500
java.lang.NumberFormatException: null
RequestURI=/BlueBox/HttpBox.do
Caused by:
javax.servlet.ServletException: java.lang.NumberFormatException: null
at it.gotoandplay.smartfoxserver.httpbox.HttpBox.init(HttpBox.java:84)
at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:433)
at org.mortbay.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:342)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:463)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1098)
at it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter.doFilter(SessionIDFilter.java:184)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
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:502)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:821)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:208)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:378)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:368)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
Caused by: java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at it.gotoandplay.smartfoxserver.httpbox.util.ClientActivityMonitor.(ClientActivityMonitor.java:40)
at it.gotoandplay.smartfoxserver.httpbox.ConnectionManager.(ConnectionManager.java:62)
at it.gotoandplay.smartfoxserver.httpbox.ConnectionManager.getInstance(ConnectionManager.java:50)
at it.gotoandplay.smartfoxserver.httpbox.HttpBox.init(HttpBox.java:73)
... 22 more
Caused by:
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at it.gotoandplay.smartfoxserver.httpbox.util.ClientActivityMonitor.(ClientActivityMonitor.java:40)
at it.gotoandplay.smartfoxserver.httpbox.ConnectionManager.(ConnectionManager.java:62)
at it.gotoandplay.smartfoxserver.httpbox.ConnectionManager.getInstance(ConnectionManager.java:50)
at it.gotoandplay.smartfoxserver.httpbox.HttpBox.init(HttpBox.java:73)
at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:433)
at org.mortbay.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:342)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:463)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1098)
at it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter.doFilter(SessionIDFilter.java:184)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
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:502)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:821)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:208)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:378)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:368)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
Powered by Jetty://
When i try it on my local machine there is no problem.
Yes, it worked for me. But this time I am dealing with this security error (only in remote, not standalone or in local browser). I try to configure crossdomain.xml but I have almost tried every configuration (even connected to SFS with domain instead of IP). The security error that flash debugger shows is located below.)
i noticed that if i put the crossdomain file to the root of the site' the working version (without bluebox) also gives a sandbox error.
Lapo, also i want to share my basic problem.
some of the visitors of the site are behind firewalls so they could not connect to SFS over 9339 or any other port. their system only allows 80 or 8080.
i try to get over this problem by bluebox to have these visitors connected to the SFS' othwerwise the project will be a real failure.
i want to mention again that i am able to connect bluebox (by avoiding my SFS port 9339 from the dsl modem) when i view the swf in Flash and in local html file.
i think the the main problem is caused by the new security additions to the latest flash player version, but if it is, i really do not know what to do as i tried almost every configuration of the cross domain file.
We have started doing the first tests with the latest policy changes.
As of now it looks like the crossdomain.xml served via http works okay in most cases. Test Page
Check this post and let me know if the connection test works for you.
If it does you should try to replicate the "configuration" we have used.
Additionally the BlueBox is active, so if you can temporarily block port 9339 on your side, you can also check it.