Re: [xmlblaster] Calling peek admin message?
Thanks. In case others are interested, the correct call was:
MsgUnit[] msgUnit = xmlBlaster.get("", "type='QueueQuery'>");
David
Marcel Ruff wrote:
Hi David,
the way to query queues is described in
http://www.xmlblaster.org/xmlBlaster/doc/requirements/engine.qos.queryspec.QueueQuery.html
The notation you have described seems to be broken in the current
xmlBlaster,
we need to check this,
regards
Marcel
David R Robison wrote:
How would I call the peek admin message? I am trying it as:
MsgUnit[] msgUnit = xmlBlaster.get("", "");
but getting the error
errorCode=resource.configuration message=#exported Error while SAX
parsing :1:79 : org.xml.sax.SAXParseException: The entity name must
immediately follow the '&' in the entity reference.
any thoughts?
TNX David
--
David R Robison
Open Roads Consulting, Inc.
708 S. Battlefield Blvd., Chesapeake, VA 23322
phone: (757) 546-3401
e-mail: [EMAIL PROTECTED]
web: http://openroadsconsulting.com
blog: http://therobe.blogspot.com
book: http://www.xulonpress.com/book_detail.php?id=2579
Re: [xmlblaster] A couple of questions about messages in the log...
David R Robison wrote: Can you tell me what these two message mean and what might cause them? Nov 12, 2007 4:48:23 PM INFO 5625-XmlBlaster.DispatchWorkerPool.Albemarle911-15544 RL10 org.xmlBlaster.util.dispatch.DispatchManager prepareMsgsFromQueue: callback:/node/Albemarle911/client/StauntonSTC/1: Message callback:/node/Albemarle911/client/StauntonSTC/1/MAX/119490410354204/DomainHeartbeat-Albemarle911 is destroyed, ignoring it Do you specify an expiration lifetime for your message which has elapsed? Probably we should remove the logging output (change to debug). Nov 12, 2007 5:11:10 PM WARNING 5645-pool-1-thread-934 RL10 org.xmlBlaster.engine.RequestBroker unSubscribe: UnSubscribe of __subId:StauntonSTC-XPATH119490247020900 by session /node/Albemarle911/client/StauntonSTC/1 failed I think I'm having a issue with remote subscriptions. I have a program that connects to node A and subscribes to messages whose master is node B. If I exit ungracefully from node A and then reconnect, then my client queue appears to be almost full of messages from node B. I know this is probably as clear as mud... but I think these messages in the logfile may be related to my problem. When your client disappears ungracefully (without unSubscribe) and its session is configured failsafe the messages will queue up. To avoid this consider to use none-failsafe login sessions which are destroyed if the client disappears (its subscriptions are removed automatically). Another option is to use the plugin xmlBlaster/src/java/org/xmlBlaster/contrib/mime/DropIfNotDeliverable.java (from xmlBlaster 1.6.1 or newer). It drops messages if subscriber is in POLLING state See xmlBlaster/src/java/org/xmlBlaster/contrib/mime/DropIfNotDeliverable.java javadoc for details regards Marcel Thanks in advance, David -- Marcel Ruff http://www.xmlBlaster.org
Re: [xmlblaster] Calling peek admin message?
Hi David,
the way to query queues is described in
http://www.xmlblaster.org/xmlBlaster/doc/requirements/engine.qos.queryspec.QueueQuery.html
The notation you have described seems to be broken in the current
xmlBlaster,
we need to check this,
regards
Marcel
David R Robison wrote:
How would I call the peek admin message? I am trying it as:
MsgUnit[] msgUnit = xmlBlaster.get("", "");
but getting the error
errorCode=resource.configuration message=#exported Error while SAX
parsing :1:79 : org.xml.sax.SAXParseException: The entity name must
immediately follow the '&' in the entity reference.
any thoughts?
TNX David
--
Marcel Ruff
http://www.xmlBlaster.org
