WARNING: This server is unstable and will be retired in the next days. If you want to keep this forum available, please request immediately a migration on the Nabble Support forum. Forums that don't receive any migration request will be deleted forever.

 « Return to Thread: Significance of DEBUG bitronix.tm.timer.TaskScheduler - total task(s) still queued:

Re: Significance of DEBUG bitronix.tm.timer.TaskScheduler - total task(s) still queued:

by snicoll :: Rate this Message:

| View in Thread

Hi,

It is a debug statement. As a regular user, you shouldn't have to care too much about BTM's debug logs unless you have a problem that you need to investigate. BTM will logs a lot of information in DEBUG mode that are pretty much useless in production.

We can explain to you what that debug statement means if you want to but it's harmless as far as I can see.

S.

On Mon, Jul 25, 2011 at 1:50 PM, Franklin Antony <franklinantony@...> wrote:

I have just started using Bitronix to get a JTA transaction done. However, I
can see the following in my log.

DEBUG bitronix.tm.timer.TaskScheduler - total task(s) still queued:


Not really sure what it means. Am sure its trying to do something. Is this
something I need to worry about ?

Regards,
Franklin


--
View this message in context: http://old.nabble.com/Significance-of-DEBUG-bitronix.tm.timer.TaskScheduler---total-task%28s%29-still-queued%3A-tp32131060p32131060.html
Sent from the Bitronix Transaction Manager mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email



 « Return to Thread: Significance of DEBUG bitronix.tm.timer.TaskScheduler - total task(s) still queued: