[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xmlblaster] Strange error when unsubscribing

To: xmlblaster at server.xmlBlaster.org
Subject: Re: [xmlblaster] Strange error when unsubscribing
From: Marcel Ruff <mr at marcelruff.info>
Date: Mon, 28 May 2007 22:01:50 +0200
In-reply-to: <20070524150541.5eb1ecdb at mail.openroadsconsulting.com>
References: <20070524150541.5eb1ecdb at mail.openroadsconsulting.com>
Reply-to: xmlblaster at server.xmlBlaster.org
Sender: owner-xmlblaster at server.xmlBlaster.org
User-agent: Thunderbird 2.0.0.0 (X11/20070326)

Hi again,

(1) after some code review together with Michele we think that we have found the bug and have commitet the patch to svn:

o #16185 Fixed using ServerScope in ConnectQos which used wrong ServerEntryFactory on client side

(2) Additionally we have fixed a bug which occurres only when the same cluster slave connects to many master cluster nodes:

o #16187 Fixed cluster client queue to have unique storageId Use -xmlBlaster/cluster/useLegacyClientQueueName true forces old behavior

Robison: If you have entries remaining in a cluster client queue or plugin client queue you need to set: xmlBlaster/cluster/useLegacyClientQueueName=true Else the entries are not found on restarting the new xmlBlaster. Preferrably, if you can throw away those messages don't set anything to have the new behavior.

regards,

Marcel

David Robison wrote:

I know we have in the past had troubles with some plugins. We are integrating data from 911 systems XML messages that are published into a cluster of xmlBlaster nodes. To do this, we deploy xmlBlaster plugins that, in one case, periodically scrapes the 911 dispatch database. New dispatches are detected and then published directly into the xmlBlaster node that the plugin is part of. We have had trouble if we used the wrong Global object (server vs client) when publishing the message. It is possible that we still have a problem with a single plugin.
Can you think of any other way this could happen?
Thanks,
David
----- Original Message -----
From: Michele Laghi [mailto:michele at laghi.eu]
To: xmlblaster at server.xmlBlaster.org
Subject: Re: [xmlblaster] Strange error when unsubscribing
Hi David and Marcel, one possible reason of this problem could be a mixup between client and server queues: The client queue stores "subscribe" messages which could not be sent as "subscribe" (lower) (comes out of MethodName.SUBSCRIBE).

At the moment I still can not understand how the client entry is read as a server entry.

Try to separate the client from the server queues by giving them different names:
in JdbcStorage[...].entriesTableName
Regards
Michele
David Robison wrote:
In the logfile portion I sent, it throws a warning that a prepared
statement is being closed with autocomplete false. Should we configure access to the postgresql database for autocomplete true?
Thanks, David
----- Original Message -----
From: Marcel Ruff [mailto:mr at marcelruff.info]
To: xmlblaster at server.xmlBlaster.org
Subject: Re: [xmlblaster] Strange error when unsubscribing
Hi again,
our persistent entries should be marked with capital letters public static final String ENTRY_TYPE_SUBSCRIBE = "SUBSCRIBE";
which does not match to the type of your logging output:
'subscribe'
I have no idea how this small notation can appear, i believe it must be somewhere in your database?
I have commited to the current svn a version which ignores case during
persistence lookup, but this is just a temporary workaround,
regards
Marcel
David Robison wrote:
We are experiencing a problem running xmlBlaster 1.5.1. After running
for
several weeks, two nodes in our cluster start reporting the same types of errors:
May 23, 2007 12:08:52 PM WARNING 6901718-pool-1-thread-4878 RL10
org.xmlBlaster.util.queue.jdbc.PreparedQuery close: close with autocommit 'false': rollback
May 23, 2007 12:08:52 PM SEVERE 6901718-pool-1-thread-4878 RL10
org.xmlBlaster.util.queue.cache.CacheQueueInterceptorPlugin loadFromPersistence: connection:/node/StauntonSTC/client/StauntonSTC/1: Could not read back data from persistence: XmlBlasterException serverSideException=true node=[StauntonSTC] location=[ServerEntryFactory]
stackTrace=errorCode=internal.notImplemented message=#exported
Persistent
object 'subscribe' is not implemented
at
org.xmlBlaster.engine.queuemsg.ServerEntryFactory.createEntry(ServerEntryFactory.java:289)
at
org.xmlBlaster.util.queue.jdbc.JdbcManagerCommonTable.processResultSet(JdbcManagerCommonTable.java:1181)
at
org.xmlBlaster.util.queue.jdbc.JdbcManagerCommonTable.getEntries(JdbcManagerCommonTable.java:2017)
at
org.xmlBlaster.util.queue.jdbc.JdbcQueueCommonTablePlugin.peek(JdbcQueueCommonTablePlugin.java:576)
at
org.xmlBlaster.util.queue.cache.CacheQueueInterceptorPlugin.loadFromPersistence(CacheQueueInterceptorPlugin.java:1042)
at
org.xmlBlaster.util.queue.cache.CacheQueueInterceptorPlugin.put(CacheQueueInterceptorPlugin.java:545)
at
org.xmlBlaster.util.queue.cache.CacheQueueInterceptorPlugin.put(CacheQueueInterceptorPlugin.java:447)
at
org.xmlBlaster.client.XmlBlasterAccess.queueMessage(XmlBlasterAccess.java:792)
at
org.xmlBlaster.client.XmlBlasterAccess.unSubscribe(XmlBlasterAccess.java:931)
at
org.xmlBlaster.engine.cluster.ClusterManager.forwardUnSubscribe(ClusterManager.java:537)
at
org.xmlBlaster.engine.RequestBroker.unSubscribe(RequestBroker.java:1167)
at
org.xmlBlaster.engine.XmlBlasterImpl.unSubscribe(XmlBlasterImpl.java:131)
at
org.xmlBlaster.util.protocol.RequestReplyExecutor.receiveReply(RequestReplyExecutor.java:490)
at
org.xmlBlaster.protocol.socket.HandleClient.handleMessage(HandleClient.java:227)
at
org.xmlBlaster.protocol.socket.HandleClient$1.run(HandleClient.java:376)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Unknown Source) versionInfo=version=1.5.1,revision=exported,os.name=Windows
2003,os.version=5.2,java.vm.vendor=Sun Microsystems Inc.,java.vm.version=1.5.0_10-b03,os.arch=x86,build.timestamp=02/26/2007 08:00 AM,build.java.vendor=Sun Microsystems
Inc.,build.java.version=1.4.2_06
errorCode
description=http://www.xmlblaster.org/xmlBlaster/doc/requirements/admin.errorcodes.listing.html#internal.notImplemented
errorCode=internal.notImplemented message=#exported Persistent object
'subscribe' is not implemented
at
org.xmlBlaster.engine.queuemsg.ServerEntryFactory.createEntry(ServerEntryFactory.java:289)
at
org.xmlBlaster.util.queue.jdbc.JdbcManagerCommonTable.processResultSet(JdbcManagerCommonTable.java:1181)
at
org.xmlBlaster.util.queue.jdbc.JdbcManagerCommonTable.getEntries(JdbcManagerCommonTable.java:2017)
at
org.xmlBlaster.util.queue.jdbc.JdbcQueueCommonTablePlugin.peek(JdbcQueueCommonTablePlugin.java:576)
at
org.xmlBlaster.util.queue.cache.CacheQueueInterceptorPlugin.loadFromPersistence(CacheQueueInterceptorPlugin.java:1042)
at
org.xmlBlaster.util.queue.cache.CacheQueueInterceptorPlugin.put(CacheQueueInterceptorPlugin.java:545)
at
org.xmlBlaster.util.queue.cache.CacheQueueInterceptorPlugin.put(CacheQueueInterceptorPlugin.java:447)
at
org.xmlBlaster.client.XmlBlasterAccess.queueMessage(XmlBlasterAccess.java:792)
at
org.xmlBlaster.client.XmlBlasterAccess.unSubscribe(XmlBlasterAccess.java:931)
at
org.xmlBlaster.engine.cluster.ClusterManager.forwardUnSubscribe(ClusterManager.java:537)
at
org.xmlBlaster.engine.RequestBroker.unSubscribe(RequestBroker.java:1167)
at
org.xmlBlaster.engine.XmlBlasterImpl.unSubscribe(XmlBlasterImpl.java:131)
at
org.xmlBlaster.util.protocol.RequestReplyExecutor.receiveReply(RequestReplyExecutor.java:490)
at
org.xmlBlaster.protocol.socket.HandleClient.handleMessage(HandleClient.java:227)
at
org.xmlBlaster.protocol.socket.HandleClient$1.run(HandleClient.java:376)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Unknown Source) May 23, 2007 12:08:52 PM INFO 6901718-pool-1-thread-4878 RL10
org.xmlBlaster.engine.RequestBroker unSubscribe: unSubscribe of '__subId:StauntonSTC-XPATH1179936462585000000' matched 1 entries in
remote
cluster
May 23, 2007 12:08:52 PM WARNING 6901718-pool-1-thread-4878 RL10
org.xmlBlaster.util.queue.jdbc.PreparedQuery close: close with autocommit 'false': rollback
May 23, 2007 12:08:52 PM SEVERE 6901718-pool-1-thread-4878 RL10
org.xmlBlaster.util.queue.cache.CacheQueueInterceptorPlugin loadFromPersistence: connection:/node/StauntonSTC/client/StauntonSTC/1: Could not read back data from persistence: XmlBlasterException serverSideException=true node=[StauntonSTC] location=[ServerEntryFactory]
stackTrace=errorCode=internal.notImplemented message=#exported
Persistent
object 'subscribe' is not implemented
at
org.xmlBlaster.engine.queuemsg.ServerEntryFactory.createEntry(ServerEntryFactory.java:289)
at
org.xmlBlaster.util.queue.jdbc.JdbcManagerCommonTable.processResultSet(JdbcManagerCommonTable.java:1181)
at
org.xmlBlaster.util.queue.jdbc.JdbcManagerCommonTable.getEntries(JdbcManagerCommonTable.java:2017)
at
org.xmlBlaster.util.queue.jdbc.JdbcQueueCommonTablePlugin.peek(JdbcQueueCommonTablePlugin.java:576)
at
org.xmlBlaster.util.queue.cache.CacheQueueInterceptorPlugin.loadFromPersistence(CacheQueueInterceptorPlugin.java:1042)
at
org.xmlBlaster.util.queue.cache.CacheQueueInterceptorPlugin.put(CacheQueueInterceptorPlugin.java:545)
at
org.xmlBlaster.util.queue.cache.CacheQueueInterceptorPlugin.put(CacheQueueInterceptorPlugin.java:447)
at
org.xmlBlaster.client.XmlBlasterAccess.queueMessage(XmlBlasterAccess.java:792)
at
org.xmlBlaster.client.XmlBlasterAccess.unSubscribe(XmlBlasterAccess.java:931)
at
org.xmlBlaster.engine.cluster.ClusterManager.forwardUnSubscribe(ClusterManager.java:537)
at
org.xmlBlaster.engine.RequestBroker.unSubscribe(RequestBroker.java:1167)
at
org.xmlBlaster.engine.XmlBlasterImpl.unSubscribe(XmlBlasterImpl.java:131)
at
org.xmlBlaster.util.protocol.RequestReplyExecutor.receiveReply(RequestReplyExecutor.java:490)
at
org.xmlBlaster.protocol.socket.HandleClient.handleMessage(HandleClient.java:227)
at
org.xmlBlaster.protocol.socket.HandleClient$1.run(HandleClient.java:376)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Unknown Source) versionInfo=version=1.5.1,revision=exported,os.name=Windows
2003,os.version=5.2,java.vm.vendor=Sun Microsystems Inc.,java.vm.version=1.5.0_10-b03,os.arch=x86,build.timestamp=02/26/2007 08:00 AM,build.java.vendor=Sun Microsystems
Inc.,build.java.version=1.4.2_06
errorCode
description=http://www.xmlblaster.org/xmlBlaster/doc/requirements/admin.errorcodes.listing.html#internal.notImplemented
errorCode=internal.notImplemented message=#exported Persistent object
'subscribe' is not implemented
at
org.xmlBlaster.engine.queuemsg.ServerEntryFactory.createEntry(ServerEntryFactory.java:289)
at
org.xmlBlaster.util.queue.jdbc.JdbcManagerCommonTable.processResultSet(JdbcManagerCommonTable.java:1181)
at
org.xmlBlaster.util.queue.jdbc.JdbcManagerCommonTable.getEntries(JdbcManagerCommonTable.java:2017)
at
org.xmlBlaster.util.queue.jdbc.JdbcQueueCommonTablePlugin.peek(JdbcQueueCommonTablePlugin.java:576)
at
org.xmlBlaster.util.queue.cache.CacheQueueInterceptorPlugin.loadFromPersistence(CacheQueueInterceptorPlugin.java:1042)
at
org.xmlBlaster.util.queue.cache.CacheQueueInterceptorPlugin.put(CacheQueueInterceptorPlugin.java:545)
at
org.xmlBlaster.util.queue.cache.CacheQueueInterceptorPlugin.put(CacheQueueInterceptorPlugin.java:447)
at
org.xmlBlaster.client.XmlBlasterAccess.queueMessage(XmlBlasterAccess.java:792)
at
org.xmlBlaster.client.XmlBlasterAccess.unSubscribe(XmlBlasterAccess.java:931)
at
org.xmlBlaster.engine.cluster.ClusterManager.forwardUnSubscribe(ClusterManager.java:537)
at
org.xmlBlaster.engine.RequestBroker.unSubscribe(RequestBroker.java:1167)
at
org.xmlBlaster.engine.XmlBlasterImpl.unSubscribe(XmlBlasterImpl.java:131)
at
org.xmlBlaster.util.protocol.RequestReplyExecutor.receiveReply(RequestReplyExecutor.java:490)
at
org.xmlBlaster.protocol.socket.HandleClient.handleMessage(HandleClient.java:227)
at
org.xmlBlaster.protocol.socket.HandleClient$1.run(HandleClient.java:376)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Unknown Source) May 23, 2007 12:08:52 PM INFO 6901718-pool-1-thread-4878 RL10
org.xmlBlaster.engine.RequestBroker unSubscribe: unSubscribe of '__subId:StauntonSTC-XPATH1179936462757000000' matched 1 entries in
remote
cluster
It appears that there is a problem unsubscribing but I am unsure what
the
problem might be. Any thoughts or hints on how to proceed with debugging this problem?
Thanks in advance, David Robison
--
Marcel Ruff
http://www.xmlBlaster.org

--
Marcel Ruff
http://www.xmlBlaster.org

References:
- Re: [xmlblaster] Strange error when unsubscribing
  - From: "David Robison" <drrobison at openroadsconsulting.com>

Prev by Date: Re: [xmlblaster] Strange error when unsubscribing
Next by Date: [xmlblaster] minor socket ping/refreshSession method inconsistency?
Previous by thread: Re: [xmlblaster] Strange error when unsubscribing
Next by thread: [xmlblaster] minor socket ping/refreshSession method inconsistency?
Index(es):
- Date
- Thread