HI shital, then build in delays in procesing the message on the consumer side. i.e. after you call invokelater, do a sleep.
On 8/1/06, shital <[EMAIL PROTECTED]> wrote:
i already did this. i used netbean's profiler. the main thing is server is sending at such high rate that client can not keep up. also on the client hand i am trying to update the JTable with whatever data i get. to update the table i am using SwingUtilities.invokelater(..) . if i just read messages and dont do anything then its looks like fine. but if i process the message then CPU raises ?? any idea ? Thanks Shital -- View this message in context: http://www.nabble.com/very-slow-consumer-cpu-100--tf2034246.html#a5597125 Sent from the ActiveMQ - User forum at Nabble.com.
-- Regards, Hiram Blog: http://hiramchirino.com
