Started JBOSS 4.0. Get the following error when trying to create tables
db-create-table:
[java] java.sql.SQLException: socket creation error
[java] at org.hsqldb.jdbc.jdbcUtil.sqlException(Unknown Source)
[java] at org.hsqldb.jdbc.jdbcConnection.(Unknown Source)
[java] at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
[java] at org.hsqldb.jdbcDriver.connect(Unknown Source)
[java] at java.sql.DriverManager.getConnection(DriverManager.java:512)
[java] at java.sql.DriverManager.getConnection(DriverManager.java:171)
[java] at org.hsqldb.util.ScriptTool.execute(Unknown Source)
[java] at org.hsqldb.util.ScriptTool.main(Unknown Source)
[java] java.lang.NullPointerException
[java] at org.hsqldb.util.ScriptTool.execute(Unknown Source)
[java] at org.hsqldb.util.ScriptTool.main(Unknown Source)
[java] ScriptTool.init error: socket creation error
[java] Exception in thread main
[java] Java Result: 1
Thought I had done everything tutorial required - obviously missed something. Heres my
hsqldb-ds.xml; which I put in each of the deploy directories just to ensure wasnt
executing out of wrong one.
?xml version=1.0 encoding=UTF-8?
!-- The Hypersonic embedded database JCA connection factory config
$Id: hsqldb-ds.xml,v 1.15 2004/09/15 14:37:40 loubyansky Exp $ --
local-tx-datasource
!-- The jndi name of the DataSource, it is prefixed with java:/ --
!-- Datasources are not available outside the virtual machine --
jndi-nameDefaultDS/jndi-name
!-- for tcp connection, allowing other processes to use the hsqldb
database. This requires the org.jboss.jdbc.HypersonicDatabase mbean.
connection-urljdbc:hsqldb:hsql://localhost:1701/connection-url
--
!-- for totally in-memory db, not saved when jboss stops.
The org.jboss.jdbc.HypersonicDatabase mbean necessary
connection-urljdbc:hsqldb:./connection-url
--
!-- for in-process persistent db, saved when jboss stops. The
org.jboss.jdbc.HypersonicDatabase mbean is necessary for properly db shutdown
--
--
COMMENTING OUT TO RUN DUKE TUTORIAL
connection-urljdbc:hsqldb:${jboss.server.data.dir}${/}hypersonic${/}localDB/connection-url
--
-- USING TO RUN DUKE TUTORIAL - ALSO SEE MBEAN AT END
FOR TCPIP CONNECTIONS --
connection-urljdbc:hsqldb:hsql://localhost:1701/connection-url
!-- The driver class --
driver-classorg.hsqldb.jdbcDriver/driver-class
!-- The login and password --
user-namesa/user-name
!--example of how to specify class that determines if exception means
connection should be destroyed--
!--exception-sorter-class-nameorg.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-sqlselect * from
something/check-valid-connection-sql --
!-- The minimum connections in a pool/sub-pool. Pools are lazily constructed on
first use --
min-pool-size5/min-pool-size
!-- The maximum connections in a pool/sub-pool --
max-pool-size20/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-minutes0/idle-timeout-minutes
!-- sql to call when connection is created
new-connection-sqlsome arbitrary sql/new-connection-sql
--
!-- sql to call on an existing pooled connection when it is obtained from pool
check-valid-connection-sqlsome 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-nameorg.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 --
track-statements/
!-- Use the getConnection(user, pw) for logins
application-managed-security/
--
!-- Use the security domain defined in conf/login-config.xml --
security-domainHsqlDbRealm/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-applicationHsqlDbRealm/security-domain-and-application
--
!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) --
