[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [xmlblaster] polling -> reconnecting
Eduardo Catarino wrote:
I have the following problem. I have a simple test
procedure that does this task:
1) Start the XmlBlaster server and publish 50 messages
2) Shut down the server
3) Publish again 50 messages
4) Start the server again
5) Send another 50 messages
All the messages have in common the same OID.
I can receive all the messages except the ones are sent when the
server is down, in this case I only receive the last one of that group.
What should I do in order to receive also those messages?
I have to add some steps:
1) Start the XmlBlaster server
2) Start subscriber
3) Start publisher and publish 50 messages
4) Subscriber reveives 50 messages
5) Shut down the server
6) Publish again 50 messages
7) Start the server again
8) Send another 50 messages
9) Subscriber reconnects and receives 100 messages
The 50 messages of 6) need to be queued on client side as no server is
This is possible out of the box only with the C++ client library and the
Java client library.
Please set the session.name to use a postiv public sessionId, for
Further - as on 8) the subscribes is not yet up and running
it wont receive the messages if not the subscriber did a persistent
subscribe on 2)
java -Dcom.sun.management.jmxremote org.xmlBlaster.Main
java javaclients.HelloWorldPublish -session.name aPublisher/1
java javaclients.HelloWorldSubscribe -session.name aSubscriber/1
-persistentSubscribe true -multiSubscribe false
With the above command line clients started in 3 DOS-Boxes (xterms) you can
play and simulate easily the above steps.