We would experience jmanage freezing, and incorrectly sending emails
reporting that applications were down.
When we checked the logs it appeared that the jvm was unable to allocate
another thread as the maximum number of threads had been exceeded. When we
viewed the jvm threads that were occurring in jmanage it appeared that there
were a lot of threads that were getting started that never finished. I
believe we have max number of threads to be 255.
We had a look at the code and noticed that no one else was reporting issues
like this, so isolated the problem down to the JSR160 connector. We had a
look at the code and could not see anything wrong with what was being done.
The number of thread names that were increasing all started with
Job_Executor[n] and the stack trace was always
The problem seemed to be exasperated when one of the applications we had
under jmanage was taken down.
So we made the assumption that this was an error in the implementation of
jmxremote_optional.jar we upgraded to the latest version on the sub website
and everything appears to be working fine now with a stable number of live
On Thu, Apr 2, 2009 at 2:59 AM, Rakesh Kalra <getkalra@...> wrote:
> Hi Ben -
> Can you share a bit more about the problem and the solution?
> On Apr 1, 2009, at 6:07 AM, Ben Storey <ben.storey@...> wrote:
> This seems to be a problem with jmxremote_optional.jar with the thread
> executors we upgraded and the number threads no longer increases. Funnily
> enough we used jmanages thread monitoring utility to help diagnose the
> On Wed, Apr 1, 2009 at 9:25 AM, Ben Storey < <ben.storey@...>
> ben.storey@...> wrote:
>> We currently have several applications that we are using to monitor and do
>> some operations on.
>> These are all JSR160 applications that we expose MBeans using spring.
>> JManage used to run ok but recently we have had to restart it nearly every
>> day because it is incorrectly reporting applications are down when they are
>> When we look at the logs it appears that the JManage is failing when
>> trying to start another thread. Monitory the jmanage application threads
>> through jmanage reports a massive number of threads started somewhere in the
>> order of 20k.
>> Has anyone run into similar problems and knows the cause or any
>> configuration that we are missing.
>> Thanks in advance.
>> Cheers ben
> jmanage-users mailing list