Disabling Transport in 1.2.0 does not work

Jonas · November 5, 2007, 12:01pm

Fresh week, fresh issue

Good morning Mr. Henninger, this time, it’s a minor one:

Upgraded to 3.4.1 and 1.2.0 this morning.

When I unchecked the box in front of a transport in the settings, usually the transport went offline straight away. This now only works with XMPP. Others (or at least ICQ, YAHOO, MSN) are pretty unimpressed, when I deactivate them, they still work, they stay online. (setting sais offline, but messaging works fine)

Luckily they produce an error. Unluckily one I don’t understand

2007.11.05 12:49:30 [org.jivesoftware.openfire.component.InternalComponentManager$2.error(InternalComponentManager.java:290)] org.xmpp.component.ComponentException: Domain (icq) already taken by another component: org.jivesoftware.openfire.gateway.protocols.oscar.OSCARTransport@ee83a8
at org.jivesoftware.openfire.component.InternalComponentManager.addComponent(InternalComponentManager.java:108)
at org.jivesoftware.openfire.gateway.TransportInstance.startInstance(TransportInstance.java:209)
at org.jivesoftware.openfire.gateway.TransportInstance.enable(TransportInstance.java:97)
at org.jivesoftware.openfire.gateway.GatewayPlugin.enableService(GatewayPlugin.java:157)
at org.jivesoftware.openfire.gateway.web.ConfigManager.toggleTransport(ConfigManager.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at uk.ltd.getahead.dwr.impl.ExecuteQuery.execute(ExecuteQuery.java:239)
at uk.ltd.getahead.dwr.impl.DefaultExecProcessor.handle(DefaultExecProcessor.java:48)
at uk.ltd.getahead.dwr.impl.DefaultProcessor.handle(DefaultProcessor.java:84)
at uk.ltd.getahead.dwr.AbstractDWRServlet.doPost(AbstractDWRServlet.java:162)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.jivesoftware.openfire.container.PluginServlet.handleServlet(PluginServlet.java:250)
at org.jivesoftware.openfire.container.PluginServlet.service(PluginServlet.java:90)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093)
at org.jivesoftware.admin.PluginFilter.doFilter(PluginFilter.java:69)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
at org.jivesoftware.admin.AuthCheckFilter.doFilter(AuthCheckFilter.java:98)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
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:313)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:844)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)

NO_MESSAGES_OR_FRIEN · November 5, 2007, 1:05pm

Daniel I have confirmed this issue with my server as weel. I attempted to add a jira entry for this but still have no access to enter issues for the gateway plugin (see pic below).

Jonas · November 5, 2007, 1:38pm

In Addition (and probably related): Spark only shows XMPP as transport icon and only offers XMPP as external Network, when adding a new user. (Always, not only when they are deactivated via backend.

The roster-entries for the gateways are there and conversations work as well.

Another thing that might be related (if not, it still should not be there):

A warning was issued…I don’t know exactly when, but I think when I tried to delete or add a MSN user:

2007.11.05 14:32:40 Error or result packet could not be delivered <iq type="error" id="mir_120" from="******@msn.*.*" to="me@*.*/Miranda">
<error code="503" type="cancel">
<service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"></service-unavailable>
</error>
</iq>

Message was edited by: Jonas

Daniel_Henninger · November 5, 2007, 2:13pm

It looks like this isn’t strictly an IM Gateway issue. I’m running into it with other plugins as well. Doing some research … see if I can figure out what’s causing it.