SSI开发:spring-pool.xml标准配置模板

本文提供了一个Spring配置C3P0数据库连接池的示例模板,详细展示了如何配置各种连接池参数,如连接获取策略、空闲连接测试、初始化连接数等,以确保数据库连接的高效管理。

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:mvc="http://www.springframework.org/schema/mvc"
    xmlns:context="http://www.springframework.org/schema/context"
    xmlns:tx="http://www.springframework.org/schema/tx"
    xmlns:aop="http://www.springframework.org/schema/aop"
    xmlns:p="http://www.springframework.org/schema/p"
    xsi:schemaLocation="
 http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
 http://www.springframework.org/schema/mvc http://www.springframework.org/schema/mvc/spring-mvc-3.0.xsd 
 http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-3.0.xsd
 http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-3.0.xsd
 http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-3.0.xsd">

 <!-- C3P0数据库配置 -->
 <bean id="c3p0" class="com.mchange.v2.c3p0.ComboPooledDataSource" destroy-method="close">
  <property name="driverClass" value="${postgresql.jdbc.driverClassName}" />
  <property name="jdbcUrl" value="${postgresql.jdbc.url}" />
  <property name="user" value="${postgresql.jdbc.username}" />
  <property name="password" value="${postgresql.jdbc.password}" />
  
  <!-- 当连接池中的连接耗尽的时候c3p0一次同时获取的连接数。Default: 3 -->
  <property name="acquireIncrement" value="1" />
  <!-- 定义在从数据库获取新连接失败后重复尝试的次数。Default: 30 -->
  <property name="acquireRetryAttempts" value="30" />
  <!-- 两次连接中间隔时间,单位毫秒。Default: 1000 -->
  <property name="acquireRetryDelay" value="1000" />
  <!-- 连接关闭时默认将所有未提交的操作回滚。Default: false -->
  <property name="autoCommitOnClose" value="false" />
  <!-- 当连接池用完时客户端调用getConnection()后等待获取新连接的时间,超时后将抛出 SQLException,如设为0则无限期等待。单位毫秒。Default: 0 -->
  <property name="checkoutTimeout" value="10000" />
  <!-- 每60秒检查所有连接池中的空闲连接。Default: 0 -->
  <property name="idleConnectionTestPeriod" value="60" />
  <!-- 初始化时获取的连接数,取值应在minPoolSize与maxPoolSize之间。Default: 3 -->
  <property name="initialPoolSize" value="1" />
  <!-- 连接池中保留的最小连接数 -->
  <property name="minPoolSize" value="1" />
  <!-- 连接池中保留的最大连接数。Default: 15 -->
  <property name="maxPoolSize" value="30" />
  <!-- 最大空闲时间,60秒内未使用则连接被丢弃。若为0则永不丢弃。Default: 0 -->
  <property name="maxIdleTime" value="60" />
  <!-- c3p0将建一张名为Test的空表,并使用其自带的查询语句进行测试。如果定义了这个参数那么 属性preferredTestQuery将被忽略。你不能在这张Test表上进行任何操作,它将只供c3p0测试 使用。Default: null -->
  <property name="automaticTestTable" value="${postgresql.jdbc.username}.C3P0_TESTTABLE" />
  <!-- 获取连接失败将会引起所有等待连接池来获取连接的线程抛出异常。但是数据源仍有效 保留,并在下次调用getConnection()的时候继续尝试获取连接。如果设为true,那么在尝试 获取连接失败后该数据源将申明已断开并永久关闭。Default: false -->
  <property name="breakAfterAcquireFailure" value="false" />  
  <!--JDBC的标准参数,用以控制数据源内加载的PreparedStatements数量。但由于预缓存的statements
  属于单个connection而不是整个连接池。所以设置这个参数需要考虑到多方面的因素。
  如果maxStatements与maxStatementsPerConnection均为0,则缓存被关闭。Default: 0-->  
  <property name="maxStatements" value="0" />
  <!--maxStatementsPerConnection定义了连接池内单个连接所拥有的最大缓存statements数。Default: 0 -->
  <property name="maxStatementsPerConnection" value="0" />
  <!--c3p0是异步操作的,缓慢的JDBC操作通过帮助进程完成。扩展这些操作可以有效的提升性能
  通过多线程实现多个操作同时被执行。Default: 3-->
  <property name="numHelperThreads" value="3" />  
 </bean>

    <!-- p6spy配置   -->
    <bean id="p6spy" class="com.p6spy.engine.spy.P6DataSource">
     <constructor-arg>
       <ref local="c3p0"/>
      </constructor-arg>
    </bean>
</beans>

行 137995: 09-18 09:52:32.972 root 2028 2028 I update_engine: type: new_update 行 137996: 09-18 09:52:32.972 root 2028 2028 I update_engine: version: 行 137997: 09-18 09:52:32.972 root 2028 2028 I update_engine: source_slot: A 行 137998: 09-18 09:52:32.972 root 2028 2028 I update_engine: target_slot: B 行 137999: 09-18 09:52:32.972 root 2028 2028 I update_engine: initial url: /storage/emulated/0/Download/flame-ota_incremental-OS3.0.250915.1.WGUCNXM.STABLE-SSI-OS3.0.250917.1.WGUCNXM.STABLE-SSI-user-16.0-016342ab2d.zip 行 138000: 09-18 09:52:32.972 root 2028 2028 I update_engine: hash_checks_mandatory: true 行 138001: 09-18 09:52:32.972 root 2028 2028 I update_engine: powerwash_required: false 行 138002: 09-18 09:52:32.972 root 2028 2028 I update_engine: switch_slot_on_reboot: true 行 138003: 09-18 09:52:32.972 root 2028 2028 I update_engine: run_post_install: true 行 138004: 09-18 09:52:32.972 root 2028 2028 I update_engine: write_verity: true 行 138005: 09-18 09:52:32.972 root 2028 2028 I update_engine: Payload: 0 行 138006: 09-18 09:52:32.972 root 2028 2028 I update_engine: urls: () 行 138007: 09-18 09:52:32.972 root 2028 2028 I update_engine: size: 238789346 行 138008: 09-18 09:52:32.972 root 2028 2028 I update_engine: metadata_size: 5180000 行 138009: 09-18 09:52:32.972 root 2028 2028 I update_engine: metadata_signature: 行 138010: 09-18 09:52:32.972 root 2028 2028 I update_engine: hash: 634C6A718C22A31B4C607AFD2359FF6B84BE6B3C4AC2FA3CB8BEB6A29C0A2AC9 行 138011: 09-18 09:52:32.972 root 2028 2028 I update_engine: type: unknown 行 138012: 09-18 09:52:32.972 root 2028 2028 I update_engine: fingerprint: 行 138013: 09-18 09:52:32.972 root 2028 2028 I update_engine: app_id: 行 138014: 09-18 09:52:32.972 root 2028 2028 I update_engine: already_applied: false 行 138015: 09-18 09:52:32.973 root 2028 2028 I update_engine: [INFO:dynamic_partition_control_android.cc(1006)] SnapshotManager initialized. 行 138016: 09-18 09:52:32.978 root 2028 2028 I update_engine: [INFO:postinstall_runner_action.cc(94)] postinstall mount point: /postinstall 行 138019: 09-18 09:52:32.988 root 2028 2028 I update_engine: [INFO:metrics_utils.cc(330)] Number of Reboots during current update attempt = 0 行 138020: 09-18 09:52:32.998 root 2028 2028 I update_engine: [INFO:metrics_utils.cc(338)] Payload Attempt Number = 1 行 138021: 09-18 09:52:33.011 root 2028 2028 I update_engine: [INFO:metrics_utils.cc(355)] Update Monotonic Timestamp Start = 1/1/1970 0:24:06 GMT 行 138022: 09-18 09:52:33.026 root 2028 2028 I update_engine: [INFO:metrics_utils.cc(364)] Update Boot Timestamp Start = 1/1/1970 0:24:06 GMT 行 138023: 09-18 09:52:33.029 root 2028 2028 I update_engine: [INFO:update_attempter_android.cc(1017)] Clearing update complete marker. 行 138024: 09-18 09:52:33.032 root 2028 2028 I update_engine: [INFO:update_attempter_android.cc(896)] Scheduling an action processor start. 行 138025: 09-18 09:52:33.037 root 2028 2028 I update_engine: [INFO:action_processor.cc(51)] ActionProcessor: starting UpdateBootFlagsAction 行 138026: 09-18 09:52:33.039 root 2028 2028 I update_engine: [INFO:update_boot_flags_action.cc(45)] Marking booted slot as good. 行 138030: 09-18 09:52:33.224 root 2028 2028 I update_engine: [INFO:action_processor.cc(116)] ActionProcessor: finished UpdateBootFlagsAction with code ErrorCode::kSuccess 行 138033: 09-18 09:52:33.226 root 2028 2028 I update_engine: [INFO:action_processor.cc(143)] ActionProcessor: starting CleanupPreviousUpdateAction 行 138034: 09-18 09:52:33.228 root 2028 2028 I update_engine: [INFO:cleanup_previous_update_action.cc(154)] Starting/resuming CleanupPreviousUpdateAction 行 138035: 09-18 09:52:33.230 root 2028 2028 I update_engine: [INFO:cleanup_previous_update_action.cc(195)] Boot completed, waiting on markBootSuccessful() 行 138036: 09-18 09:52:33.240 root 2028 2028 I update_engine: [INFO:snapshot.cpp(4145)] EnsureMetadataMounted does nothing in Android mode. 行 138037: 09-18 09:52:33.243 root 2028 2028 I update_engine: [INFO:snapshot_stats.cpp(40)] Read merge statistics file failed: No such file or directory 行 138038: 09-18 09:52:33.251 root 2028 2028 I update_engine: [INFO:cleanup_previous_update_action.cc(294)] Waiting for any previous merge request to complete. This can take up to several minutes. 行 138039: 09-18 09:52:33.254 root 2028 2028 I update_engine: [INFO:snapshot.cpp(1190)] CheckMergeState for snapshots returned: None 行 138040: 09-18 09:52:33.256 root 2028 2028 I update_engine: [INFO:snapshot.cpp(1155)] ProcessUpdateState handling state: None 行 138041: 09-18 09:52:33.259 root 2028 2028 I update_engine: [INFO:cleanup_previous_update_action.cc(331)] Can't find any snapshot to merge. 行 138042: 09-18 09:52:33.261 root 2028 2028 I update_engine: [INFO:snapshot.cpp(247)] Cancelling update from state: 0 行 138043: 09-18 09:52:33.263 root 2028 2028 I update_engine: [INFO:snapshot.cpp(352)] Removing all update state. 行 138044: 09-18 09:52:33.281 root 2028 2028 I update_engine: [INFO:cleanup_previous_update_action.cc(136)] Stopping/suspending/completing CleanupPreviousUpdateAction 行 138045: 09-18 09:52:33.284 root 2028 2028 I update_engine: [INFO:cleanup_previous_update_action.cc(520)] Not reporting merge stats because state is None 行 138046: 09-18 09:52:33.286 root 2028 2028 I update_engine: [INFO:cleanup_previous_update_action.cc(136)] Stopping/suspending/completing CleanupPreviousUpdateAction 行 138047: 09-18 09:52:33.288 root 2028 2028 I update_engine: [INFO:action_processor.cc(116)] ActionProcessor: finished CleanupPreviousUpdateAction with code ErrorCode::kSuccess 行 138048: 09-18 09:52:33.289 root 2028 2028 I update_engine: [INFO:action_processor.cc(143)] ActionProcessor: starting InstallPlanAction 行 138049: 09-18 09:52:33.291 root 2028 2028 I update_engine: [INFO:action_processor.cc(116)] ActionProcessor: finished InstallPlanAction with code ErrorCode::kSuccess 行 138050: 09-18 09:52:33.293 root 2028 2028 I update_engine: [INFO:action_processor.cc(143)] ActionProcessor: starting DownloadAction 行 138051: 09-18 09:52:33.295 root 2028 2028 I update_engine: [INFO:install_plan.cc(79)] InstallPlan:
09-19
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值