PubSub performance/service question


i’‘m developing a little application, a shared text editor like writely (but only plain text for now ). I’'m using xmpp pubsub for disseminating changes and wildfire as the xmpp server.

But i’'m stuck right now, if the publication rate is about 1 publication/second to the same node, the server start to throw internal server errors (like the ones at the end of the mail) and no broadcast the published items. If the publication rate is lower, say 5/seg , everything works fine.

Is any limitation to the rate at which a publisher can push items to the node?.

when i send


its handled ok, and i get:

async recv:

but less than 3 seconds later, i send:

Tue Aug 22 13:16:30 2006]


i dont know the reason of that

Actually i’'m using JabberHTTPBind ( and JSJaC for the connection betwen the clients and the server, but i think the problem is not there.

Any suggestions?

i dont think the pubsub module has these limitations, but after looking in my code and the stanzas sended over the wire, i dont know where the problem is.


Exceptions i get from the server:

2006.08.22 11:22:44 org.jivesoftware.wildfire.pubsub.PubSubEngine$ .java:1936) Internal server error


at java.util.concurrent.LinkedBlockingQueue.extract(

at java.util.concurrent.LinkedBlockingQueue.poll(

at org.jivesoftware.wildfire.pubsub.PubSubEngine$

at java.util.TimerThread.mainLoop(


2006.08.22 11:23:30 org.jivesoftware.wildfire.pubsub.PubSubModule.process( Internal server error


at java.util.concurrent.LinkedBlockingQueue.remove(

at org.jivesoftware.wildfire.pubsub.PubSubEngine.queueItemToRemove(PubSubEngine.ja va:1878)

at org.jivesoftware.wildfire.pubsub.LeafNode.publishItems(

at org.jivesoftware.wildfire.pubsub.PubSubEngine.publishItemsToNode(PubSubEngine.j ava:420)

at org.jivesoftware.wildfire.pubsub.PubSubEngine.process(

at org.jivesoftware.wildfire.pubsub.PubSubModule.process(

at org.jivesoftware.wildfire.IQRouter.handle(

at org.jivesoftware.wildfire.IQRouter.route(

at org.jivesoftware.wildfire.spi.PacketRouterImpl.route(


at ava:51)



at 62)



Hola Pablo,

Which Java version are you using? As mentioned in JM-716 this is a problem with old JVM versions. Try using JDK (1.5.0_06 or later) and see how it goes. BTW, Java 1.5.0_08 has been released a few weeks ago.


– Gato

Thanks Gaston!

i’'m have used version 1.5.0 … now with a more recent jdk, is working fine.

Thanks for you quick answer!

gracias Maestro,