"bstansberry(a)jboss.com" wrote : Sounds like disconnecting is necessary though,
with the "invokerDestructionDelay" as the workaround to cut down on the waste
associated with that.
I agree. It looks to me the right thing to do is to connect()/disconnect(). The only
reason I could see to leave it as it is would be if creation/connect were noticeable more
expensive operations compared to caching it and reusing the same client all the time. I
don't see it being much more expensive although the ClientInvoker location done in
2.2.x happens within a big synchronized block.
A jira on this could verify the performance of different options.
View the original post :
Reply to the post :