smartfoxserver.com

Posted: **25 May 2010, 01:42**

Hi,

We have two servers, production and staging.

Staging is using port 9449 and production port 80 for bluebox, both server are running with 'root' privileges.

Requesting the following url '/BlueBox/HttpBox.do?debugCmd=main' gives NumberFormatException on production, but it works for staging.

What could be the cause of the problem?

Smart Fox Server 1.6.6 is being used.

Stacktrace:

Code: Select all

javax.servlet.UnavailableException: java.lang.NumberFormatException: null
   at org.mortbay.jetty.servlet.ServletHolder.makeUnavailable(ServletHolder.java:406)
   at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:442)
   at org.mortbay.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:339)
   at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:478)
   at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
   at it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter.doFilter(SessionIDFilter.java:195)
   at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148)
   at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:387)
   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:765)
   at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
   at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
   at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
   at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
   at org.mortbay.jetty.Server.handle(Server.java:324)
   at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:535)
   at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:880)
   at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
   at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
   at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
   at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
   at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)

Thank you

Posted: **25 May 2010, 10:21**

Can you please post the content of the bluebox.properties file found in your Server/ folder?
Also please tell me your <ServerIP> setting from the config.xml file.

Thanks

Posted: **25 May 2010, 22:24**

bluebox.properties

Code: Select all

log_level=FINER
log_folder=./logs/
log_max_size=100000
log_max_files=5

# Can be embedded or stand-alone
serverMode=embedded

# These 2 are available only in stand-alone mode
sfsAddr=127.0.0.1
sfsPort=9339

# This value should always be > 20. A value of 30 is recommended.
client_idle_time=30

#Ã‚Â Uncomment if you have set serverMode=stand-alone
# client_idle_request_time=300

# Allows runtime debugging
# You can point the browser to -> http://hostname:port/BlueBox/HttpBox.go?debugCmd=main
debug_mode=true

config.xml

Code: Select all

<ServerIP>*</ServerIP>

Problems disappeared after we have restarted bluebox from the SFS admin console. I wounder what could it be?

Posted: **29 May 2010, 13:33**

Maybe a port problem? You said the port used is 9449 but the BlueBox is configured for 9339.