Having problem setting up FastPath outside of the plugins directory

I prefer not explosing our physical wildfire server to the outside world, other than the XMPP ports needed to talk and federate with it, thus, I’'ve decided to setup a jetty server running on our webserver. (IIS btw). (I put jetty on port 8000 and the version is 6.1.0 (latest stable version)).

Jetty starts up fine and i can browse the default contexts no problem, so I shutdown the webserver and put the webchat.war in the webapps directory and restarted the webserver. Browsing to the /server/webchat path in IE, i’‘m prompted with the Fasthpath setup which i complete. At the end of the setup, I’‘m told I can click on the image to test the setup, but no image is appearing and I’'m getting the following erros in my console:


2007-01-30 14:58:39.829::INFO: Started SelectChannelConnector @

Jan 30, 2007 2:59:13 PM com.jivesoftware.webchat.util.WebLog logError

WARNING: Could not retrieve image: offline


at com.jivesoftware.smack.workgroup.user.Workgroup.getChatSettings(Unkno

wn Source)

at com.jivesoftware.smack.workgroup.user.Workgroup.getChatSettings(Unkno

wn Source)

at com.jivesoftware.webchat.util.SettingsManager.getImage(SettingsManage


at com.jivesoftware.webchat.LiveAssistantServlet.service(LiveAssistantSe


at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491


at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(Servlet


at com.jivesoftware.webchat.SetCharacterEncodingFilter.doFilter(SetChara


at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(Servlet


at com.jivesoftware.webchat.SetupFilter.doFilter(SetupFilter.java:91)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(Servlet


at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:3

at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.jav


at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:1

at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:6

at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391)

at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHand


at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.


at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:1

at org.mortbay.jetty.Server.handle(Server.java:285)

at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:45

at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpCo


at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:500)

at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)

at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:357)

at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.ja


at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool


I ignore the error and browse back to the /computer/webchat directory to see that the image is indeed working and perform a test. The request comes through my spark client and I accept it; however, the ‘‘user’’ side never leaves the looking for agent screen. The agent side shows the ‘‘user’’ joining the room, but no activity on the user side whatsoever–it just sits there.

Lastly, when i shutdown the jetty server, and start it back up, its going through the setup process again as a fresh install.

Currently, there is no firewall between this webserver and the wildfireserver–they’'re both on the same local network.

I’'m not married to the idea of using jetty to make this work, I chose it only because I thought since Wildfire was using it that it would be ‘‘easier’’ to get up and running and has a small footprint considering its only for this application.

Thanks in advance for your help.


Just to followup. After being anoyed with not getting jetty to work, I switched to tomcat and worked like a champ. I’'m now in the process of setting up an IASPI filter in IIS to proxy requests from our webserver to tomcat much like we do with JIRA.