But, I get this error on startup:
May 3, 2006 9:23:37 PM SEVERE 10-XmlBlaster.MainThread org.xmlBlaster.util.queue.jdbc.JdbcConn
ectionPool initialize: connecting to DB, error code : '0 : SOO10 Invalid argument in JDBC call' DB configuration details follow (check if the DB is running)
May 3, 2006 9:23:37 PM INFO 10-XmlBlaster.MainThread org.xmlBlaster.util.queue.jdbc.JdbcConn
ectionPool initialize: diagnostics: initialize -url : 'jdbc:firebirdsql:server2/3050:/usr/database/xmlblaster.gdb'
May 3, 2006 9:23:37 PM INFO 10-XmlBlaster.MainThread org.xmlBlaster.util.queue.jdbc.JdbcConn
ectionPool initialize: diagnostics: initialize -user : 'sysdba'
May 3, 2006 9:23:37 PM INFO 10-XmlBlaster.MainThread org.xmlBlaster.util.queue.jdbc.JdbcConn
ectionPool initialize: diagnostics: initialize -password : 'something'
May 3, 2006 9:23:37 PM INFO 10-XmlBlaster.MainThread org.xmlBlaster.util.queue.jdbc.JdbcConn
ectionPool initialize: diagnostics: initialize -max number of conn : '1'
May 3, 2006 9:23:37 PM INFO 10-XmlBlaster.MainThread org.xmlBlaster.util.queue.jdbc.JdbcConn
ectionPool initialize: diagnostics: initialize -conn busy timeout : '90000'
May 3, 2006 9:23:37 PM INFO 10-XmlBlaster.MainThread org.xmlBlaster.util.queue.jdbc.JdbcConn
ectionPool initialize: diagnostics: initialize -driver list : 'org.hsqldb.jdbcDriver:org.ldbc.jdbc.jdbcDriver:com.mckoi.JDBCDriver:sun.jdbc.odbc.JdbcOdbcDriver:ORG.as220.tinySQL.dbfFileDriver:oracle.jdbc.driver.OracleDriver:com.microsoft.jdbc.sqlserver.SQLServerDriver:com.microsoft.sqlserver.jdbc.SQLServerDriver:com.mysql.jdbc.Driver:org.postgresql.Driver:org.firebirdsql.jdbc.FBDriver:de.sag.jdbc.adabasd.ADriver:com.sybase.jdbc2.jdbc.SybDriver:SQLite.JDBCDriver'
May 3, 2006 9:23:37 PM INFO 10-XmlBlaster.MainThread org.xmlBlaster.util.queue.jdbc.JdbcConn
ectionPool initialize: diagnostics: initialize -max. waiting Threads: '300'
java.sql.SQLException: SOO10 Invalid argument in JDBC call
at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
at org.hsqldb.jdbcDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
<snip>
Too bad it doesn't say which argument is invalid.
I copied the jdbc url into Quantum DB perspective in Eclipse, and it works.
So, I guess xmlblaster is not loading the jaybird .jar file, but that jar file is in the lib
directory.
I run xmlblaster with this command line (jdk java 1.5.0_05)
$JAVA_HOME/bin/java -jar lib/xmlBlaster.jar -admin.remoteconsole.port 1024
-plugin/xmlrpc/hostname 192.168.1.4 -plugin/xmlrpc/port 4080
So, I haven't explicitely specified the classpath, but the firebird xmlblaster docs do
say "just copy jaybird..jar into lib directory"
Sorry I'm a java newbie..