|新浪首页|博客首页
  1. 发博文
  2. 发照片
  3. 发视频
  4. 发邮件
 发博文
忧郁森林 订阅
空间
博客
播客
相册
杂志
圈子
论坛
我主张
首页|博文|收藏
相关博文
内容读取中…
推荐博文
内容读取中…
谁看过这篇博文
内容读取中…
字体大小：大中小 正文
基于TCP/IP协议的HSQL数据库的连接设定 (2008-10-04 23:45:53)
标签：it  分类：java学友
HSQLDB-DS.XML

<?xml version="1.0" encoding="UTF-8"?>

<!-- The Hypersonic embedded database JCA connection factory config -->

<!-- $Id: hsqldb-ds.xml,v 1.15.2.1 2006/01/10 18:11:03 dimitris Exp $ -->

<datasources>
   <local-tx-datasource>
       <!-- http://www.360doc.com/showWeb/0/0/62227.aspx -->
      <!-- The jndi name of the DataSource, it is prefixed with java:/ -->
      <!-- Datasources are not available outside the virtual machine -->
      <jndi-name>DefaultDS</jndi-name>
      <!-- For server mode db, allowing other processes to use hsqldb over tcp.
      This requires the org.jboss.jdbc.HypersonicDatabase mbean.   -->
      <connection-url>jdbc:hsqldb:hsql://localhost:1701</connection-url>
      <!-- For totally in-memory db, not saved when jboss stops.
      The org.jboss.jdbc.HypersonicDatabase mbean is required for proper db shutdown
      <connection-url>jdbc:hsqldb:.</connection-url>
      -->
      <!-- For in-process persistent db, saved when jboss stops.
      The org.jboss.jdbc.HypersonicDatabase mbean is required for proper db shutdown
      <connection-url>jdbc:hsqldb:hsql://localhost:1701</connection-url>
      -->
      <!-- The driver class -->
      <driver-class>org.hsqldb.jdbcDriver</driver-class>

      <!-- The login and password -->
      <user-name>sa</user-name>
      <password></password>

      <!--example of how to specify class that determines if exception means connection should be destroyed-->
      <!--exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyExceptionSorter</exception-sorter-class-name-->

      <!-- this will be run before a managed connection is removed from the pool for use by a client-->
      <!--<check-valid-connection-sql>select * from something</check-valid-connection-sql> -->

      <!-- The minimum connections in a pool/sub-pool. Pools are lazily constructed on first use -->
      <min-pool-size>5</min-pool-size>

      <!-- The maximum connections in a pool/sub-pool -->
      <max-pool-size>20</max-pool-size>

      <!-- The time before an unused connection is destroyed -->
      <!-- NOTE: This is the check period. It will be destroyed somewhere between 1x and 2x this timeout after last use -->
      <!-- TEMPORARY FIX! - Disable idle connection removal, HSQLDB has a problem with not reaping threads on closed connections -->
      <idle-timeout-minutes>100</idle-timeout-minutes>

      <!-- sql to call when connection is created
        <new-connection-sql>some arbitrary sql</new-connection-sql>
      -->

      <!-- sql to call on an existing pooled connection when it is obtained from pool
         <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
      -->

      <!-- example of how to specify a class that determines a connection is valid before it is handed out from the pool
         <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyValidConnectionChecker</valid-connection-checker-class-name>
      -->

      <!-- Whether to check all statements are closed when the connection is returned to the pool,
           this is a debugging feature that should be turned off in production -->

      <!-- Use the getConnection(user, pw) for logins
        <application-managed-security/>
      -->

      <!-- Use the security domain defined in conf/login-config.xml -->
      <security-domain>HsqlDbRealm</security-domain>

      <!-- Use the security domain defined in conf/login-config.xml or the
           getConnection(user, pw) for logins. The security domain takes precedence.
        <security-domain-and-application>HsqlDbRealm</security-domain-and-application>
      -->

      <!-- HSQL DB benefits from prepared statement caching -->
      <prepared-statement-cache-size>32</prepared-statement-cache-size>

      <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
      <metadata>
         <type-mapping>Hypersonic SQL</type-mapping>
      </metadata>

      <!-- When using in-process (standalone) mode -->
      <depends>jboss:service=Hypersonic,database=localDB</depends>
      <!-- Uncomment when using hsqldb in server mode
      <depends>jboss:service=Hypersonic</depends>
      -->
   </local-tx-datasource>

   <!-- Uncomment if you want hsqldb accessed over tcp (server mode)  -->
   <mbean code="org.jboss.jdbc.HypersonicDatabase"
     name="jboss:service=Hypersonic">
     <attribute name="Port">1701</attribute>   
     <attribute name="Silent">true</attribute>
     <attribute name="Database">default</attribute>
     <attribute name="Trace">false</attribute>
     <attribute name="No_system_exit">true</attribute>
   </mbean>
  

   <!-- For hsqldb accessed from jboss only, in-process (standalone) mode -->
   <mbean code="org.jboss.jdbc.HypersonicDatabase"
     name="jboss:service=Hypersonic,database=localDB">
     <attribute name="Database">localDB</attribute>
     <attribute name="InProcessMode">true</attribute>
   </mbean>
  
</datasources>


HSQL 数据库能够以如下两种方式运行：进程内或客户-服务器（HSQL 文档称之为，服
务器模式）。由于用户需要使用能够连接到DB 的工具，以运行SQL 脚本，因此必须保证数
据库以客户-服务器模式运行，并能接受TCP/IP 连接请求。默认时，最新的JBoss 发布版将
客户-服务器模式禁用了，这主要考虑到安全性要素，因为如果默认登陆账号没有修改将导
致安全性问题。因此，用户需要打开设置了默认数据源的deploy/hsqldb-ds.xml 文件。在文
件的开始部分，能够看到connection-url 元素。其取值必须是

QUOTE:
jdbc:hsqldb:hsql://localhost:1701，
而且其他connection-url 元素值必须注释掉。


已投稿到： 排行榜 圈子
评论(0)| 阅读 (0) | 收藏 (0) | 分享 | 打印 | 举报
前一篇：为什么要设置JAVA_HOME&Path&CLASSPATH&CATALINA_HO
后一篇：Grails:一种新型 Web 开发框架
评论     发表评论
发表评论  
匿名评论(无需注册)
验证码：看不清楚数字吗？点击这里再试试。
新浪BLOG意见反馈留言板　不良信息反馈　电话：95105670 提示音后按2键（按当地市话标准计费）　欢迎批评指正

新浪简介 | About Sina | 广告服务 | 联系我们 | 招聘信息 | 网站律师 | SINA English | 会员注册 | 产品答疑

Copyright © 1996 - 2008 SINA Corporation, All Rights Reserved

新浪公司 版权所有