Hi,
I don't see what the problem is from this.
You might try interclient 2.0; if you are using jdk 1.3 you will probably
have to recompile the java portion. Source code is available at
http://www.ibphoenix.com/ibp_interbase_download.html
If you wish to use the firebird version of interclient 2.0
(sourceforge.net.projects.firebird) you will need to compile the c++
interserver as well; the firebird version fixes some problems with
databasemetadata. I don't know if anyone has successfully done this on
windows: if you are interested I will be happy to work with you.
I think the hanging means the connection pool can't get its test
connection. Are you sure the path to the db is correct? I suggest
uncommenting the pool parameters and setting LoggingEnabled to true: the
stack trace might be helpful.
I have never seen jboss get messed up, I don't know how that could happen.
david jencks
On 2001.05.31 00:53:51 -0400 Wiwih Will Gunadi wrote:
> 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
