Project:
| View Revisions: Issue #39056 | [ Back to Issue ] | ||
| Summary | 0039056: Hibernate pool is being used by some ant tasks | ||
| Revision | 2019-01-31 19:17 by caristu | ||
| Description | The Hibernate pool is being used by some ant tasks defined in src-db/build.xml. We are not using the Tomcat pool to retrieve the DB connections in those tasks because their classpath does not include the .jars required by the Tomcat pool. |
||
| Revision | 2019-01-31 19:15 by caristu | ||
| Description | The Hibernate pool is being used by some ant tasks. In the ant tasks defined in src-db/build.xml we are not using the Tomcat pool to retrieve the DB connections, because their classpath does not include the .jar required by the Tomcat pool (tomcat-jdbc.jar). |
||
| Revision | 2019-01-31 19:08 by caristu | ||
| Description | The Hibernate pool is being used by some ant tasks: a) We are not using the Tomcat pool to retrieve the DB connections, because the classpath of some tasks does not include the .jar required by the Tomcat pool (tomcat-jdbc.jar). b) The Hibernate pool is being created and used in some cases, for example those tasks that are making use of the ModelProvider. The default Tomcat pool should be used instead. |
||
| Revision | 2019-01-31 18:53 by caristu | ||
| Description | The Hibernate pool is being used by some ant tasks: a) We are not using the Tomcat pool to retrieve the DB connections, because the classpath of some tasks does not include the .jar required by the Tomcat pool (tomcat-jdbc.jar). b) The Hibernate pool is being created and used in some cases, for example those tasks that are making use of the ModelProvider. The default Tomcat pool should be used instead. Note that this issue is solved for the tasks defined in src-db/build.xml with the fix for issue 0040047. This is because those tasks are using a classpath(runtime-classpath) that includes the tomcat pool libraries. |
||
| Revision | 2019-01-31 18:48 by caristu | ||
| Description | The Hibernate pool is being used by some ant tasks: a) We are not using the Tomcat pool to retrieve the DB connections, because the classpath of some tasks does not include the .jar required by the Tomcat pool (tomcat-jdbc.jar). b) The Hibernate pool is being created and used in some cases, for example those tasks that are making use of the ModelProvider. The default Tomcat pool should be used instead. |
||
| Revision | 2018-07-26 13:34 by caristu | ||
| Description | The Hibernate pool is being used by some ant tasks: a) We are not using the Tomcat pool to retrieve the DB connections, because the classpath of the tasks (runtime-classpath) does not include the .jar required by the Tomcat pool (tomcat-jdbc.jar). b) The Hibernate pool is being created and used in some cases, for example those tasks that are making use of the ModelProvider. The default Tomcat pool should be used instead. |
||
| Revision | 2018-07-26 13:32 by caristu | ||
| Description | The Hibernate pool is being used by some ant tasks: a) We are not using the Tomcat pool to retrieve the DB connections, because the classpath of the tasks (runtime-classpath) does not include the .jar required by the Tomcat pool (tomcat-jdbc.jar). b) We are making use of DAL within some tasks, like the export.database task. When initializing the DAL layer, the Hibernate pool is being created and used in some cases. The default Tomcat pool should be used instead. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |