7 Replies Last post: Apr 13, 2008 5:20 PM by Sander  
Daniel Henninger Jiver 2,904 posts since
Aug 10, 2005
Currently Being Moderated

Apr 8, 2008 1:46 PM

IM Gateway Plugin 1.2.3 Released!

Hi folk!  I meant to post this yesterday but missed it!  The IM Gateway plugin version 1.2.3 was released.  Primarily, it's a release to address compatibility with Openfire 3.5.0.  That said, it also includes a couple of bugfixes and new features!

 

  • There is now a QQ Transport thanks to lizongbo!

  • Administrators can now set the connect host to * for the XMPP Transport to enable users to connect to whatever server they want, based off their JID.

  • Incoming messages are now send to bare JIDs, which means they'll be routed according to the rules of the server instead of the IM Gateway plugin's tracking.  (primarily affects multiple logins as the same priority)

 

You can download the new version from the plugins page or via the admin console of Openfire 3.5.0.

Dallas Gutauckis Bronze 33 posts since
Jul 26, 2007
Currently Being Moderated
Apr 9, 2008 8:31 AM in response to: Daniel Henninger
Re: IM Gateway Plugin 1.2.3 Released!

 

Daniel,

 

 

We're currently seeing issues with the IM Gateway plugin and 3.5

 

 

When a transport is registered, I'm seeing:

<iq type="set" id="569-44" to="dallas@im.myyearbook.com/b3MvbS8xLjguMS4xMy8xMjA3NzQ3NDM0NzM4"><query xmlns="jabber:iq:roster"><item jid="msn.im.myyearbook.com" name="MSN Transport" subscription="both"><group>Transports</group></item>

 

 

However, no further roster items, or presence comes through with screen names from the transport or anything. This is failing on all transports. I have tried the Gateway Tests in admin console with a "Success" response.

 

 

Any idea what may be wrong, here?

 

 

Thanks,

Dallas

 

 

Dallas Gutauckis Bronze 33 posts since
Jul 26, 2007
Currently Being Moderated
Apr 9, 2008 9:13 AM in response to: Dallas Gutauckis
Re: IM Gateway Plugin 1.2.3 Released!

 

And, to supplement from logs what might be the problem:

 

 

2008.04.09 10:02:30 org.jivesoftware.openfire.net.SocketPacketWriteHandler.process(SocketPacketWrite Handler.java:62) Could not deliver packet

 

<presence from="dallas@im.myyearbook.com/b3MvbS8xLjguMS4xMy8xMjA3NzQ5NzM0NDcz" to="aim.im.myyearbook.com"/>

java.lang.UnsupportedOperationException

  • at com.tangosol.coherence.component.util.daemon.queueProcessor.service.replicatedC ache.Optimistic$CacheHandler.unlock(Optimistic.CDB:1)*

  • at com.tangosol.coherence.component.util.SafeNamedCache.unlock(SafeNamedCache.CDB: 1)*

  • at com.jivesoftware.util.cache.ClusteredCache.unlock(ClusteredCache.java:234)*

  • at com.jivesoftware.util.cache.CoherenceClusteredCacheFactory$CoherenceLock.unlock (CoherenceClusteredCacheFactory.java:351)*

  • at org.jivesoftware.openfire.gateway.BaseTransport.processPacket(BaseTransport.jav a:189)*

  • at org.jivesoftware.openfire.component.InternalComponentManager$RoutableComponents .process(InternalComponentManager.java:592)*

  • at org.jivesoftware.openfire.spi.RoutingTableImpl.routePacket(RoutingTableImpl.jav a:257)*

  • at org.jivesoftware.openfire.net.SocketPacketWriteHandler.process(SocketPacketWrit eHandler.java:43)*

  • at org.jivesoftware.openfire.spi.PacketDelivererImpl.deliver(PacketDelivererImpl.j ava:47)*

  • at org.jivesoftware.openfire.spi.PresenceManagerImpl.probePresence(PresenceManager Impl.java:384)*

  • at org.jivesoftware.openfire.spi.PresenceManagerImpl.handleProbe(PresenceManagerIm pl.java:282)*

  • at org.jivesoftware.openfire.PresenceRouter.handle(PresenceRouter.java:182)*

  • at org.jivesoftware.openfire.PresenceRouter.route(PresenceRouter.java:69)*

  • at org.jivesoftware.openfire.spi.PacketRouterImpl.route(PacketRouterImpl.java:75)*

  • at org.jivesoftware.openfire.spi.PacketRouterImpl.route(PacketRouterImpl.java:56)*

  • at org.jivesoftware.openfire.component.InternalComponentManager.sendPacket(Interna lComponentManager.java:237)*

  • at org.jivesoftware.openfire.gateway.BaseTransport.sendPacket(BaseTransport.java:1 830)*

  • at org.jivesoftware.openfire.gateway.BaseTransport.start(BaseTransport.java:1131)*

  • at org.jivesoftware.openfire.component.InternalComponentManager.addComponent(Inter nalComponentManager.java:130)*

  • at org.jivesoftware.openfire.gateway.TransportInstance.startInstance(TransportInst ance.java:182)*

  • at org.jivesoftware.openfire.gateway.GatewayPlugin.maybeStartService(GatewayPlugin .java:151)*

  • at org.jivesoftware.openfire.gateway.GatewayPlugin.initializePlugin(GatewayPlugin. java:71)*

  • at org.jivesoftware.openfire.container.PluginManager.loadPlugin(PluginManager.java :447)*

  • at org.jivesoftware.openfire.container.PluginManager.access$300(PluginManager.java :46)*

  • at org.jivesoftware.openfire.container.PluginManager$PluginMonitor.run(PluginManag er.java:1013)*

  • at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)*

  • at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)*

  • at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)*

  • at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101 (ScheduledThreadPoolExecutor.java:98)*

  • at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodi c(ScheduledThreadPoolExecutor.java:181)*

  • at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Schedu ledThreadPoolExecutor.java:205)*

  • at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java: 885)*

  • at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) *

  • at java.lang.Thread.run(Thread.java:619)*

 

 

 

Todd Getz KeyContributor 1,957 posts since
Apr 2, 2007
Currently Being Moderated
Apr 9, 2008 10:28 AM in response to: Dallas Gutauckis
Re: IM Gateway Plugin 1.2.3 Released!

Have you tried manually deleting the plugin, and its folder.  Then download the new one again.  It could be it did not install correctly.

Dallas Gutauckis Bronze 33 posts since
Jul 26, 2007
Currently Being Moderated
Apr 9, 2008 10:30 AM in response to: Todd Getz
Re: IM Gateway Plugin 1.2.3 Released!

This was all a fresh installation, but it looks as if this may have been caused by a conflict from another plugin.

Todd Getz KeyContributor 1,957 posts since
Apr 2, 2007
Currently Being Moderated
Apr 9, 2008 10:31 AM in response to: Dallas Gutauckis
Re: IM Gateway Plugin 1.2.3 Released!

What plugins do you have installed?

Dallas Gutauckis Bronze 33 posts since
Jul 26, 2007
Currently Being Moderated
Apr 9, 2008 10:35 AM in response to: Todd Getz
Re: IM Gateway Plugin 1.2.3 Released!

I believe the problem was the Enterprise plugin w/ clustering.  I suppose we'll have to see how this goes with the open-sourcing of Enterprise.

Sander Bronze 146 posts since
Jun 14, 2005
Currently Being Moderated
Apr 13, 2008 5:20 PM in response to: Daniel Henninger
Re: IM Gateway Plugin 1.2.3 Released!

/me attached a screenshot of how the new QQ transport looks like in a non-cvs development build of Coccinella currently.

Attachments:

More Like This

  • Retrieving data ...