Re: Best practices for connection factory configurations when using connection pooling?


Thanks Andy, I appreciate the response. Makes sense.

On the same note, given we use a pool of adequate size for the primary connection factory, wouldn't it also make sense to enable datanucleus.connection.singleConnectionPerExecutionContext? If the connections were not pooled, using different connection factories for tx and non-tx contexts sounds logical. But with pooling in place already, it feels a bit wasteful. Speaking in context of an application that performs many non-tx read operations here.

Join { to automatically receive all group messages.