|
From: Gait B. <gai...@ti...> - 2003-02-03 08:34:13
|
Hi team, while trying to speed up the receiving process (one of our apps is batch = oriented and typically needs to retrieve any buffered messages as fast = as possible without waiting for new ones), I found that the wait time is = reset to REQUEST_MIN_WAIT_INTERVAL after receiving a message from the = server (in Request.java), rather than the value set explicitly. While my = testing showed having 2 listeners polling every 10ms will result in = message loss (I patched Request.java to leave the value at the = customInterval), I am curious about the cause behind that, and a = possibly more accurate timing. For instance, making my listeners poll at = 100ms went just fine. Trying to bypass the polling mechanism in Request.java and going = directly through the MessageServiceHandlerConnection, as suggested a = while ago to Jason by Ng, gave me some issues with the database = connection when the MSH is running (using hsqldb) and with null pointers = when the MSH is not running.=20 Ideally, I'd like to retrieve the number of messages queued in the MSH = for my AC, and then just retrieve those messages in a burst. However, = getPendingMessages always returns an empty list, rather than a list of = queued messages, so I can't even count the number pending. It would be = even cooler if I could retrieve the messages by their messageId. thnx, Gait. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Gait Boxman Manager Advanced Technology & Standards TIE Product Development BV Amsterdam, The Netherlands Tel: +31 20 658 9091 Fax: +31 20 658 9945 E-mail: gai...@ti... WWW: www.TIEglobal.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |