[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [xmlblaster] I_Callback
How can I prevent my client which implements I_Callback interface to logout
prematurely before all the updates have been received into callback receiver
i think i don't understand the question.
Messages are delivered instantly - if there are publishers active
there will always be new messages.
You can check the current number of callback queue entries with
<qos> <!-- update() -->
<queue index='0' of='1'/>
Here is an example:
1. Start the server
2. Start a subscriber with a positive sessionId
java javaclients.HelloWorldSubscribe -session.name joe/1 -dispatch/callback/retries -1
Don't hit a key to NOT subscribe explicitly as we publish below a PtP message
-> Now kill the subscriber with Ctrl-C
3. Start a PtP publisher
java javaclients.HelloWorldPublish -destination joe -forceQueuing true -numPublish 1000
Hit ten times a key to publish ten messages
4. Start the subscriber from 2. again und you will receive the
messages with the queue index count.
A variation is to not do step 2 before step 3. Because the destination "joe"
is unknown the messages are stored in an instantly created 'subject' queue
(note we have set forceQueuing to true). When now 'joe/1' logs in
all 10 messages are delivered but in this case the qos queue size may not be 10
but be some smaller chunks (which sums up to 10)
as the subject queue entries are shuffeled to the callback queue and
this may be intermitted by the callback sending thread.
The PtP publisher however could mark a message as the last message
(setting a QoS client property) but this is transparent to xmlBlaster,
I am trying to use socket protocol and getting:
[14-nov.-2003 13:13:54 INFO
MsgErrorHandler-/node/thomas_laptop/client/mon_01/-77] We are the last session taking care on PtP message
02', putting it back to subject queue
[14-nov.-2003 13:13:54 WARN
MsgErrorHandler-/node/thomas_laptop/client/mon_01/-77] Callback server is lost, killing login session of client
errorCode=[communication.noConnection.dead] serverSideException=true node=[thomas_laptop]
location=[SOCKET-HandleClientRequest-mon_01] message=[update() invocation ignored, we
are shutdown. :Original erroCode=communication.noConnection]