If you just share one connection between the Scheduler Pooling consumers, it
could be not effective, as the consumers have to be wait for the connection.
I think it could be reasonable to use the a pool to hold the connections for
the consumers to share with.
Blog: http://willemjiang.blogspot.com (English)
On September 15, 2016 at 1:54:17 PM, Corral A. (acorralor...@gmail.com) wrote:
> I investigated and I would like to know how I sould do the next EIP
> I have 20 scheduler task that launch a task, each with different data but
> using the same component. The component is a custom component that connects
> to a remote service to read data. I would like to instantiate only one
> component for this read tasks.
> The readcomponent supports SchedulerPoooling but I don't want to use one
> instance by schedule because "readcomponent" is too heavy.
> Is it correct if I develop "readcomponent" for using an external service
> (Spring @Service) that manages only one connection and do the heavy work.