https://issues.apache.org/bugzilla/show_bug.cgi?id=56472
--- Comment #2 from Stefan Frings ---
Thanks for your quick answer.
1)While analyzing this problem, I found and solved two problem causes:
I disabled the pooling of the LDAP interface because the pool starts a thread
that remains running.
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project taglibs-parent has an issue affecting its community integration.
This issu
I am hoping this is the proper forum for my problem. I have enabled the
JmxRemoteLifeCycleListener and able to connect to tomcat 7 using
jconsole etc. using the following url.
service:jmx:rmi://10.92.12.88:10002/jndi/rmi://10.92.12.88:10001/jmxrmi
However as soon as I try to connect from my ow
https://issues.apache.org/bugzilla/show_bug.cgi?id=56472
--- Comment #1 from Konstantin Kolinko ---
1. Normally that reference should have been cleared by NamingContextListener
The sequence of events is
o.a.c.core.StandardContext.stopInternal()
...
fireLifecycleEvent(Lifecycle.CONFIGURE_STOP_E
https://issues.apache.org/bugzilla/show_bug.cgi?id=56474
--- Comment #2 from vlcvlc ---
(In reply to Konstantin Kolinko from comment #1)
> (In reply to vlcvlc from comment #0)
>
> At least the following in your configuration is insane:
> 1 threads x 2Mb jvm thread stack each = 20 Gb.
>
> Bu
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project taglibs-parent has an issue affecting its community integration.
This issu
