All i am doing is creating an instance of a connector and setting it with
an java executor with an custom thread pool. Not sure i get it, when you
say registering the executor mbean, thought if connector is just
programmatically created, it shouldn't have really mattered. Moreover, it
does show the
Vicky,
On 12/21/15 3:12 PM, Vicky wrote:
> I am using an embedded version of Tomcat 7.0.42. Using java executor with
> either of the connectors i.e. BIO/NIO.
>
> However while monitoring the server via JMX, I see the mbean attributes,
>
> currentThreadCount
>
> currentThreadsBusy
>
> always sh
On Jan 18, 2013, at 3:08 PM, yogesh hingmire wrote:
> Thanks Dan,
>
> So when i am not using the executor and specifying the maxthreads in the
> connector element, what would be the size of the pool ?
maxThreads
From the docs...
"The maximum number of request processing threads to be created b
Thanks Dan,
So when i am not using the executor and specifying the maxthreads in the
connector element, what would be the size of the pool ?
Yogesh
On Fri, Jan 18, 2013 at 12:04 PM, Daniel Mikusa wrote:
> On Jan 18, 2013, at 12:54 PM, yogesh hingmire wrote:
>
> > Folks,
> >
> > What are the pe
On Jan 18, 2013, at 12:54 PM, yogesh hingmire wrote:
> Folks,
>
> What are the performance implications of not using the executor element
> (threadpool) for my AJP connector ?
Instead of having one pool of threads that you can share across multiple
connectors, you'll just have one pool of threa
