Hi.
I'm having some really odd xmlBlaster server behavior, and I'm hoping
you might have some ideas even though I don't have that much information
to give you.
I put my projects own metadata into the xmlBlaster key before
publishing. Clients in our system subscribe either to a topic or using
XPath (matching our metadata in the key). What we started seeing is that
some times XPath subscriptions and queries stop working. Clients
subscribed to the corresponding topic still get the messages, but those
subscribed to the XPath don't. Stranger still is that I can change the
XPath string and get it to match. I give you an example below. These
issues happen intermittently, but now we have gotten into this state
more often than not. I am using 0.91. It happens on servers running on
both WinXP and linux.
Here's an example. The xmlBlaster key that gets published looks
something like the following:
<key oid='ComponentControl' contentMime='text/xml'>
<jaguarMetadata>
<product><System><Component><Control/></Component></System></product>
<publisher>MC</publisher>
<jagTimeOfPub>2004-10-28T19:46:31Z</jagTimeOfPub>
<docid>MC63</docid>
<predecessors>
</predecessors>
</jaguarMetadata>
</key>
If I set the XPath string to "//product/System/Component/Control", the
server says it doesn't match, and client doesn't receive the message. On
the other hand if I were to set the XPath string to "//product" it does
match and deliver the message.
Please let me know if you have any ideas of what can be going on. If you
need any more information let me know.
Thank you.
Marshall