TimeoutFactory exits if the thread pool rejects any new tasks (thread pool is full)

If the pool is configured to be blocking, then the TimeoutFactory gets a ThreadPoolExecption.

It would be preferable if the TimeoutFactory ran the same task in the same context, rather than aborting on ThreadPoolFullException.

This causes all expired messages/scheduled messages to stop processing entirely.

Stack trace:

2005-08-29 17:46:37,812 ERROR [STDERR] ( ) org.jboss.util.threadpool.ThreadPoolFullException: java.lang.RuntimeException: Pool is blocked
2005-08-29 17:46:37,813 ERROR [STDERR] ( ) at org.jboss.util.threadpool.BasicThreadPool.execute(BasicThreadPool.java:273)
2005-08-29 17:46:37,813 ERROR [STDERR] ( ) at org.jboss.util.threadpool.BasicThreadPool.runTaskWrapper(BasicThreadPool.java:129)
2005-08-29 17:46:37,813 ERROR [STDERR] ( ) at org.jboss.util.threadpool.BasicThreadPool.run(BasicThreadPool.java:145)
2005-08-29 17:46:37,813 ERROR [STDERR] ( ) at org.jboss.util.timeout.TimeoutFactory.doWork(TimeoutFactory.java:521)
2005-08-29 17:46:37,813 ERROR [STDERR] ( ) at org.jboss.util.timeout.TimeoutFactory.access$300(TimeoutFactory.java:28)
2005-08-29 17:46:37,814 ERROR [STDERR] ( ) at org.jboss.util.timeout.TimeoutFactory$1.run(TimeoutFactory.java:549)