Fastpath and openfire 3.6.4

We had an issue with the openfire server where it refused to login users in and refused to allow anyone into the admin console, I set the openfire.xml setup to false and went through the setup again and everything began working again but now fastpath is not working at all. I have went as far as removing and reinstalling fasthpath plugins. Fastpath is on the same server as the openfire server. The error I’m getting now is


Closing session due to incorrect hostname in stream header. Host: Connection: socket: Socket[addr=/,port=57426,localport=5269] session: null

Closing session due to incorrect hostname in stream header. Host: Connection: socket: Socket[addr=/,port=57426,localport=5269] session: null

2011.02.03 11:50:04 Could not retrieve image: offline


at com.jivesoftware.smack.workgroup.user.Workgroup.getChatSettings(Unknown Source)

at com.jivesoftware.smack.workgroup.user.Workgroup.getChatSettings(Unknown Source)

at org.jivesoftware.webchat.util.SettingsManager.getImage( )

at org.jivesoftware.webchat.FastpathServlet.service(

at javax.servlet.http.HttpServlet.service(

at org.mortbay.jetty.servlet.ServletHolder.handle(

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.ja va:1093)

at org.jivesoftware.webchat.SetCharacterEncodingFilter.doFilter(SetCharacterEncodi

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.ja va:1084)

at org.jivesoftware.webchat.SetupFilter.doFilter(

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.ja va:1084)

at org.mortbay.jetty.servlet.ServletHandler.handle(


at org.mortbay.jetty.servlet.SessionHandler.handle(

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

at org.mortbay.jetty.webapp.WebAppContext.handle(

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

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

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

at org.mortbay.jetty.Server.handle(

at org.mortbay.jetty.HttpConnection.handleRequest(

at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.j ava:829)

at org.mortbay.jetty.HttpParser.parseNext(

at org.mortbay.jetty.HttpParser.parseAvailable(

at org.mortbay.jetty.HttpConnection.handle(


at org.mortbay.thread.QueuedThreadPool$

**I changed the hostname and ip address for privacy reasons.

Is the host entry listed in /etc/hosts different from the IP address openfire runs on? Seems this is related to the error… or what does the DNS entry resolve to?

The IP resolves to the local server which is the openfire server. I forgot to add I even added the hostname to the /etc/hosts and the same error occured.

Does your XMPP Domain match (e.g. hostname entry)? If not, this is also a common resulting error.

My XMPP domain is also. I’ve made sure that everything matches.

From the Admin Console, first page after login, what is the “Server Name” set to under Server Properties, and what is the “Host Name” set to under Environment?

Wow I’m a fool, I was going through this so fast I over looked this part. The server name is while the hostname is . Is the server name changed in the database? If so I am using a MSSQL DB , and I was not able to find the proper table that houses the server name or is it in a xml file. I was not able to find material that discussed changing the server name.

Haha no worries, key contributor Sixthring must have replied to many similar forum posts in the past. It is an issue that genuinely comes up almost every week.

Try editing the “xmpp.domain” System Property within the Admin Console. The configuration of the server has been updated to focus there, instead of in openfire.xml or within the database itself.

“xmmp.domain” is set to

OK, does restarting openfire change it?

Thank you, this appeared to work. I believed that I had restarted the service , but that appears to not have been the case. It is now functioning again, and I thank you.

Thank you to everyone else that responded also. Have a good weekend.