[xmlblaster] XmlBlaster client recovery after crash

[Dimitri.Devriendt at ses-astra.com]

Hi Marcel,

I use XmlBlaster to send PtP messages from XmlBlaster client A to client B.
The messages are volatile and don't use the forcequeuing feature.

Client B uses a callback that implements the update method like  :
      private messageCount = 0;

      public String[] update(String cbSessionId, MessageUnit[] msgUnitArr)
{
            if (messageCount == 10) {
                  System.exit(0);
            } else {
                  /* handle message */
            }
            messageCount++;
      }

During the crash (simulated by the System.exit(0)), XmlBlaster server gets
an org.omg.CORBA.COMM_FAILURE and then throws the following :
      [Aug 20, 2002 5:27:50 PM ERROR MsgQueue.java:294-MsgQueue:subject:B]
The queue is shutdown, putMsgs() of 1 messages failed, starting error
handling ...
      java.lang.Exception: Stack trace
              at java.lang.Thread.dumpStack(Thread.java:992)
              at
org.xmlBlaster.engine.queue.MsgQueue.putMsgs(MsgQueue.java:295)
              at
org.xmlBlaster.engine.queue.MsgQueue.putMsg(MsgQueue.java:274)
              at
org.xmlBlaster.authentication.SubjectInfo.queueMessage(SubjectInfo.java:205)
              at
org.xmlBlaster.engine.RequestBroker.publish(RequestBroker.java:1009)
              at
org.xmlBlaster.engine.XmlBlasterImpl.publish(XmlBlasterImpl.java:136)
              at
org.xmlBlaster.protocol.corba.ServerImpl.publish(ServerImpl.java:107)
              at org.xmlBlaster.protocol.corba.serverIdl.ServerPOA.
_invoke(ServerPOA.java:80)
              at
org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java:207)
              at
org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:404)
              at
org.jacorb.poa.RequestProcessor.run(RequestProcessor.java:513)
      [Aug 20, 2002 5:27:51 PM INFO  RequestBroker] Publishing 1 volatile
dead letters

After the crash of client B, I restart that client (login with the same
name and password) and XmlBlaster server still throws the above mentioned
exceptions for all new sended messages.

What is wrong ?

Best regards,

Dimitri







--
DISCLAIMER:
This e-mail contains proprietary information some or all of which may be
legally privileged. It is for the intended recipient only. If an addressing
or transmission error has misdirected this e-mail, please notify the author
by replying to this e-mail. If you are not the intended recipient you must
not use, disclose, distribute, copy, print, or rely on this e-mail.