cayenne-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrus Adamchik <>
Subject Re: Creating a second runtime with different number of max connections
Date Mon, 18 Nov 2013 06:25:02 GMT
This looks about right.. However you may just use “cayenne.jdbc.max_connections”. Presumably
module properties are scoped by runtime, so stripping off domain/node should be ok.

Also check that you don’t have it set globally for the JVM via -Dcayenne.jdbc.max_connections
, which would override any Module settings.


On Nov 14, 2013, at 7:30 PM, John Huss <> wrote:

> I'm having trouble overriding the max number of database connections when
> creating a second ServerRuntime.  I have a module like this:
> public class BackgroundModule implements Module {
>    @Override
>    public void configure(Binder binder) {
>        binder.bindMap(Constants.PROPERTIES_MAP)
>            .put("cayenne.jdbc.max_connections.MyDomain.MyNode", 1);
>    }
> }
> In the first ServerRuntime I create I have set the number of connections
> higher.  That higher number is still used in the second runtime created
> even though I have added the BackgroundModule to the end of the module list
> and it is for sure being run.  Is there a way to override the max
> connections either directly or via DI?
> Thanks,
> John

View raw message