users@glassfish.java.net

service failure results in start-up failure (3.1.2.2)

From: Pawel Veselov <pawel.veselov_at_gmail.com>
Date: Fri, 28 Feb 2014 14:14:24 -0800

Hi.

I'm running into a problem when I'm trying to start an instance that is
immediately pounded by service load. Apparently, the start-up process is
sensitive to errors that are not related to start-up process at all. Is
there any way to make it, well, not sensitive?

Specifically:

[#|2014-02-28T14:04:14.182-0800|SEVERE|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=10;_ThreadName=Thread-2;|Shutting
down v3 due
to startup exception : The thread pool's task queue is full, limit: 50|#]

I'm fine with the task queue being full, and definitely don't consider it a
start-up exception...