I came across a similar problem.
What had happened was that the Instant DB & HyperSonic JDBC drivers had been
removed to so the container was hanging when starting the out of the box
data sources.
Try this:
<mbean code="org.jboss.jdbc.JdbcProvider"
name="DefaultDomain:service=JdbcProvider">
<attribute
name="Drivers">org.hsql.jdbcDriver,org.enhydra.instantdb.jdbc.idbDriver,inte
rbase.interclient.Driver</attribute>
</mbean>
And see what happens.
Jonathan
-----Original Message-----
From: Wiwih "Will" Gunadi [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 31 May 2001 4:54 p.m.
To: [EMAIL PROTECTED]
Subject: [JBoss-user] JBoss hangs at starting DefaultDS pool using
Interbase
Hi all,
I'm using InterBase (Firebird v.0.9.4) and Interclient 1.6.
I saw a lot of people pull this off but having problems with the
interclient.jar.
In my case however, JBoss simply hangs without any trace (both console and
file log) after reporting that it's starting the DefaultDS pool.
Here's the Interbase section of my jboss.jcml:
<!-- JDBC -->
<mbean code="org.jboss.jdbc.JdbcProvider"
name="DefaultDomain:service=JdbcProvider">
<attribute name="Drivers">interbase.interclient.Driver</attribute>
</mbean>
<mbean code="org.jboss.jdbc.XADataSourceLoader"
name="DefaultDomain:service=XADataSource,name=DefaultDS">
<attribute name="PoolName">InterbaseDS</attribute>
<attribute
name="DataSourceClass">org.opentools.minerva.jdbc.xa.wrapper.XADataSourceImp
l</attribute>
<attribute name="Properties"></attribute>
<attribute
name="URL">jdbc:interclient://localhost/d:/jboss/jboss/db/interbase/jboss.gd
b</attribute>
<attribute name="JDBCUser">SYSDBA</attribute>
<attribute name="Password">masterkey</attribute>
<!--
<attribute name="GCMinIdleTime">1200000</attribute>
<attribute name="MaxSize">10</attribute>
<attribute name="GCEnabled">false</attribute>
<attribute name="InvalidateOnError">false</attribute>
<attribute name="TimestampUsed">false</attribute>
<attribute name="Blocking">true</attribute>
<attribute name="GCInterval">120000</attribute>
<attribute name="IdleTimeout">1800000</attribute>
<attribute name="IdleTimeoutEnabled">false</attribute>
<attribute name="LoggingEnabled">false</attribute>
<attribute name="MaxIdleTimeoutPercent">1.0</attribute>
<attribute name="MinSize">0</attribute>
-->
</mbean>
It doesn't matter whether I comment out the rest of the <mbean> or not. The
problem is not with the Interclient and Interbase because I can successfully
access the db using Interclient by itself.
Sorry I can't include the log because trying this out actually messed up my
JBoss installation (i.e a perfectly deployed .jar file using HyperSonic
stops working after I try to switch to Interbase, so I have to delete the
whole JBoss directory and re-do the install).
We use Jonas in our team right now, if I can work JBoss with Interbase,
it'll make a stronger case for us to switch to JBoss :)
Could anybody help me, and to the JBoss team, good job!
-Will Gunadi--
Developer
Compuware
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
