We've followed the instructions on the smartfoxserver.com / BlueBox FAQ to set up Jetty for BlueBox stand-alone.
Together with this, we are seeing sessions being created through the page provided at http://host:port/BlueBox/HttpBox.do?debugCmd=main.
But, the major issue is that none of our BlueBox clients connect all the way through to the SFS instance, and we consider that it's due to the handshake failures.
The full detail, in context...
We start jetty with:
Code: Select all
java -Xmx256 -jar start.jar etc/jetty.xml
And the output is:
Code: Select all
::::::::::: { BlueBox INITED } ::::::::::::
: :
: Version 1.0.5 -- (c) 2008 gotoAndPlay() :
: :
:::::::::::::::::::::::::::::::::::::::::::
2009-04-03 17:16:07.040::INFO: Opened /home/yp/jetty/jetty-6.1.15/logs/2009_04_03.request.log
2009-04-03 17:16:07.054::INFO: Started SelectChannelConnector@10.6.20.2:8082
Apr 3, 2009 5:17:20 PM it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter doFilter
WARNING: BlueBox<->SFS Handshake failure!
Apr 3, 2009 5:17:20 PM it.gotoandplay.smartfoxserver.httpbox.HttpBox init
INFO: BlueBox initializing...
Apr 3, 2009 5:17:20 PM it.gotoandplay.smartfoxserver.httpbox.util.ClientActivityMonitor run
INFO: Activity Monitor starts
Apr 3, 2009 5:17:36 PM it.gotoandplay.smartfoxserver.httpbox.filter.SessionIDFilter doFilter
WARNING: BlueBox<->SFS Handshake failure!
Our bluebox.properties:
Code: Select all
#:::::::::::::::::::::::::::::::::::::::::::::::::::::::
# {{ SmartFoxServer - BlueBox }}
# Configuration File
# version 1.0
#
# (c) 2004-2007 gotoAndPlay()
# www.smartfoxserver.com
# www.gotoandplay.it
#:::::::::::::::::::::::::::::::::::::::::::::::::::::::
log_level=FINEST
log_folder=./logs/
log_max_size=100000
log_max_files=5
# Can be embedded or stand-alone
serverMode=stand-alone
# These 2 are available only in stand-alone mode
sfsAddr=127.0.0.1
sfsPort=80
# This value should always be > 20. A value of 30 is recommended.
client_idle_time=3600
# Needed for stand-alone configuration
client_idle_request_time=3600
# Allows runtime debugging
# You can point the browser to -> http://hostname:port/BlueBox/HttpBox.go?debugCmd=main
debug_mode=true
Our jetty.xml, well, just the Connector section for now...
Code: Select all
<Call name="addConnector">
<Arg>
<New class="org.mortbay.jetty.nio.SelectChannelConnector">
<Set name="host">10.6.20.2</Set>
<Set name="port"><SystemProperty name="jetty.port" default="8082"/></Set>
<Set name="maxIdleTime">30000</Set>
<Set name="Acceptors">2</Set>
<Set name="statsOn">false</Set>
<Set name="confidentialPort">8443</Set>
<Set name="lowResourcesConnections">5000</Set>
<Set name="lowResourcesMaxIdleTime">5000</Set>
</New>
</Arg>
</Call>
Finally, our AS2 client code configures the SFClient to "Bluebox-connect" to an Apache virtual host which forwards the external host-addr:80 to 10.6.20.2:8082.
Can anyone help us better understand the cause of the "SFS<->BlueBox handshake failure" messages and toward a solution which allows BlueBox clients to connect all the way through?
Thanks so much, in advance!