Use connection pooling in Jetty too

It should increase performance when developing.
This commit is contained in:
Oscar Gonzalez Fernandez 2013-06-01 18:20:14 +02:00
parent 59da60fe75
commit 3ce5e012be
2 changed files with 36 additions and 8 deletions

32
pom.xml
View file

@ -982,11 +982,33 @@
</configuration>
<dependencies>
<dependency>
<groupId>${jdbcDriver.groupId}</groupId>
<artifactId>${jdbcDriver.artifactId}</artifactId>
<version>${jdbcDriver.version}</version>
</dependency>
<dependency>
<groupId>${jdbcDriver.groupId}</groupId>
<artifactId>${jdbcDriver.artifactId}</artifactId>
<version>${jdbcDriver.version}</version>
</dependency>
<!-- connection pooling -->
<dependency>
<groupId>com.jolbox</groupId>
<artifactId>bonecp</artifactId>
<version>0.7.1.RELEASE</version>
</dependency>
<!-- connection pooling dependencies -->
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>1.5.5</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-simple</artifactId>
<version>1.5.5</version>
</dependency>
<dependency>
<groupId>com.google.guava</groupId>
<artifactId>guava</artifactId>
<version>14.0.1</version>
</dependency>
</dependencies>
</plugin>

View file

@ -6,11 +6,17 @@
<New id="libreplan-ds" class="org.mortbay.jetty.plus.naming.Resource">
<Arg>${dataSource.jndiName}</Arg>
<Arg>
<New class="org.springframework.jdbc.datasource.DriverManagerDataSource">
<Set name="driverClassName">${jdbcDriver.className}</Set>
<Set name="url">${dataSource.url}</Set>
<New class="com.jolbox.bonecp.BoneCPDataSource">
<Set name="driverClass">${jdbcDriver.className}</Set>
<Set name="jdbcUrl">${dataSource.url}</Set>
<Set name="username">${dataSource.user}</Set>
<Set name="password">${dataSource.password}</Set>
<Set name="partitionCount">3</Set>
<Set name="minConnectionsPerPartition">5</Set>
<Set name="maxConnectionsPerPartition">100</Set>
<Set name="acquireIncrement">5</Set>
<Set name="idleConnectionTestPeriod">30</Set>
</New>
</Arg>
</New>