java - Jersey REST service as Mule pooled component doesn't work as expected -


I am trying to work as a component shared in a Jersey resource vertically ESB 3.4.0

Mule flow configuration looks like this (Jersey resource is managed by Spring):

   & Lt; Pooling-profile maxactive = "3" /> & Lt; / Deposit Components & gt; & Lt; / Jersey: resources & gt;  

this & lt; Flow / & gt; is defined inside the tag.

I assumed that it would be recycled by giving three examples of service.

When the service runs 100 calls (each call is in its thread), then I think that only one example of service (jersey resource) is called if annotated with @Sington, And 100 different instances are said without @ Sissington.

How can I ensure that only 3 instances are created and reused?


Comments

Popular posts from this blog

winforms - C# Form - Property Change -

javascript - amcharts makechart not working -

java - Algorithm negotiation fail SSH in Jenkins -