Hi,
OK, that does sound reasonable, but if that is the case, then how can you
distinguish between just wait time and actual CPU time in the profiler
output?
Hiram Chirino wrote:
>
> Hi I don't think your interpreting the profiler correctly.
>
> It is expected that most of the time that threa
Hi I don't think your interpreting the profiler correctly.
It is expected that most of the time that thread will be spent on the
SocketInputStream.socketRead0() call. But that's just wall time not
CPU time. The method is blocking/idle waiting for IO from the socket.
Regards,
Hiram
On Dec 19,
I replied to this but cant seem to see the reply, anyway, it looks like this
is still happening on 5.0.should I file a jira on 4.1.1?
/Tom
rajdavies wrote:
>
> This looks like it might be a bug - but ActiveMQ 5.0 is now available
> - please give it a try ;)
> On Dec 19, 2007, at 10:57 AM
Hi,
Its still the same issue in 5.0 by the looks of things:
http://www.nabble.com/file/p14418496/AMQ5.0_dump.html AMQ5.0_dump.html
100% is being spent in readInt()
Would you expect alot of time to be spent in this method in the first place
or is this completely unexpected? Has you/anyone ever
This looks like it might be a bug - but ActiveMQ 5.0 is now available
- please give it a try ;)
On Dec 19, 2007, at 10:57 AM, TOPPER_HARLEY wrote:
Hi,
Im running an eclipse RCP application that uses AMQ4.1.1 for
receiving data
from temp queues(request/response) and topics (for updates). We
