[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [xmlblaster] remainingLife
Hi Liuwen,
sorry the late response.
This feature is not completly implemented.
I don't know yet when i find time to finish it (it shouldn't be a big deal).
I keep you informed,
regards,
Marcel
liuwen wrote:
>Hi, all
>
>I meet a question when using xmlBlaster, help me pls.
>
>the message PublishQos is:
><qos>
> <expiration remainingLife='10000'/>
></qos>
>
>publish such 10 messages
>
>After a while, the console Loged:
>[2002-6-14 16:19:09 WARN MessageUnitWrapper] Message 1 is expired, timeout event occurred - tests are missing!
>[2002-6-14 16:19:09 WARN MessageUnitWrapper] Message 2 is expired, timeout event occurred - tests are missing!
>[2002-6-14 16:19:09 WARN MessageUnitWrapper] Message 3 is expired, timeout event occurred - tests are missing!
>[2002-6-14 16:19:09 WARN MessageUnitWrapper] Message 4 is expired, timeout event occurred - tests are missing!
>[2002-6-14 16:19:09 WARN MessageUnitWrapper] Message 5 is expired, timeout event occurred - tests are missing!
>[2002-6-14 16:19:09 WARN MessageUnitWrapper] Message 6 is expired, timeout event occurred - tests are missing!
>[2002-6-14 16:19:09 WARN MessageUnitWrapper] Message 7 is expired, timeout event occurred - tests are missing!
>[2002-6-14 16:19:09 WARN MessageUnitWrapper] Message 8 is expired, timeout event occurred - tests are missing!
>[2002-6-14 16:19:10 WARN MessageUnitWrapper] Message 9 is expired, timeout event occurred - tests are missing!
>[2002-6-14 16:19:10 WARN MessageUnitWrapper] Message 10 is expired, timeout event occurred - tests are missing!
>
>then, start the receiver ( login as zhangsan), but it doesn't work, the console loged:
>[2002-6-14 16:20:07 INFO Authenticate-http://192.168.2.118:3412] Successful login for client zhangsan, session:4 expires after [ 24 h 0 millis ], 1 of 10 sessions are in use.
>[2002-6-14 16:20:07 INFO XmlKeyDom] Client zhangsan is accessing message oid="1" after successful query
>[2002-6-14 16:20:07 INFO XmlKeyDom] Client zhangsan is accessing message oid="2" after successful query
>[2002-6-14 16:20:07 INFO XmlKeyDom] Client zhangsan is accessing message oid="3" after successful query
>[2002-6-14 16:20:07 INFO XmlKeyDom] Client zhangsan is accessing message oid="4" after successful query
>[2002-6-14 16:20:07 INFO XmlKeyDom] Client zhangsan is accessing message oid="5" after successful query
>[2002-6-14 16:20:07 INFO XmlKeyDom] Client zhangsan is accessing message oid="6" after successful query
>[2002-6-14 16:20:07 INFO XmlKeyDom] Client zhangsan is accessing message oid="7" after successful query
>[2002-6-14 16:20:07 INFO XmlKeyDom] Client zhangsan is accessing message oid="8" after successful query
>[2002-6-14 16:20:07 INFO XmlKeyDom] Client zhangsan is accessing message oid="9" after successful query
>[2002-6-14 16:20:07 INFO XmlKeyDom] Client zhangsan is accessing message oid="10" after successful query
>[2002-6-14 16:20:07 INFO XmlKeyDom] 10 MessageUnits matched to subscription "//topic[ at id='aaaa']"
>[2002-6-14 16:20:07 ERROR CbWorker:session:4] Callback failed: java.lang.NullPointerException
>java.lang.NullPointerException
> at org.xmlBlaster.engine.queue.MsgQueue.takeMsgs(MsgQueue.java:321)
> at org.xmlBlaster.engine.callback.CbWorker.run(CbWorker.java:45)
> at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:725)
> at java.lang.Thread.run(Unknown Source)
>[2002-6-14 16:20:07 WARN MsgQueue:session:4] Lost callback connection for session:4 errorCounter=1
>[2002-6-14 16:20:07 WARN MsgQueue:session:4] Can't send message back to clientzhangsan, producing now dead letters.
>[2002-6-14 16:20:07 ERROR CbWorker:session:4] java.lang.NullPointerException
>java.lang.NullPointerExceptionat org.xmlBlaster.engine.queue.MsgQueue.takeMsgs(MsgQueue.java:321)
> at org.xmlBlaster.engine.queue.MsgQueue.handleFailure(MsgQueue.java:157)
> at org.xmlBlaster.engine.queue.MsgQueue.activateCallbackWorker(MsgQueue.java:452)
> at org.xmlBlaster.engine.callback.CbWorker.run(CbWorker.java:89)
> at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:725)
> at java.lang.Thread.run(Unknown Source)
>
>and after that, the publisher can't send any message to the receiver.
>
>what's the problem?
>
>liuwen.
>
>
>
>