Hi!
Here is an update:
The Interbase 2.0 Client posted at the August 31 is buggy. Some classes
are missing. You have to rebuilt the jdbc drivers from the sources
(javac *.java in interclient/dev/packages/borland/.. , ../com/.. and
finally ../interbase/.. . Extend your classpath to
interclient/dev/packages/ before compling in ../interbase/..)
The missing classes caused the weird jBoss behavior. The [JDBC} thing
just stopped loading the drivers. Nevertehless jBoss startet but behaved
weird.
Some more brief instructions for setting up interbase:
ALWAYS provide username and password (which are SYSDBA and masterkey
initially). For adding users you need to start ./bin/gsec NOT just
./gsec ! Argh ...
Creating a new database with isql works with
CREATE DATABASE '/tmp/ejb.gdb' user 'SYSDBA' password 'masterkey'
The quotes are VERY important, don't ask me why !
You need to setup the ibserver program on the server. Just starting it
is fine. No news is good news here. Also you need the interserver from
the client (!) package on the server. This is started with the correct
entry in /etc/inetd.conf. Just install the client on the server too, the
script sets it up properly for you :-).
Finally the client needs the new .jar that your made out of the client
sources in its classpath.
Phew ...
Now I'll try to tune the test suite to use InterBase. To be continued
...
Tobias
Aaron Mulder wrote:
>
> Interesting. I hadn't heard it was now Open Source.
>
> In any case, there should be a line at the beginning of the server
> outpu that says either the driver was loaded or it wasn't loaded, not just
> silence. Can you look carefully and/or post the entire startup sequence?
> You must, of course, have an Interbase JDBC drive JAR in jboss/lib/ext in
> order for the driver to be loaded successfully (and I'm not sure what the
> correct class name is, but presumably the documentation comes with the
> JAR).
>
> I've never seen A. B sometimes happens when something doesn't
> start and the exception propogates all the way to the startup process,
> which then dies before it gets around to registering the shutdown
> listener. We need to fix that so exceptions never get that far.
> The easiest way to make the test suite use Interbase is to edit
> jboss/conf/jboss.conf and find the DataSourceImpl lines. Change the URL,
> driver, user name, and password, but leave the data source name as
> "Hypersonic", and then it should make your Interbase DB into a data source
> named "Hypersonic" which the test beans should use.
> However, there may be some lingering data type mapping issues
> which you'd have to resolve by creating a jaws.xml for the TestBeans.jar
> file. Personally, I'd rather try to fix it so that doesn't happen than
> try to talk you through the workaround, so let me know how far you get.
>
> Aaron
>
> On Tue, 5 Sep 2000, Tobias wrote:
> > Hi!
> > I tried to connect InterBase 6.0 to jBoss. I am running into some
> > problems:
> >
> > 1. From the mail archive I retrieved a message, which said, the jdbc
> > driver class should be interbase.interclient.Driver . If I include this
> > driver into jboss.properties in the jdbc.drivers line, the driver is not
> > loaded properly (no [JDBC] output at server startup).
> > Also there are two funny effects for the server:
> > a) The last line of the startup-sequence reads:
> > [JDBC] jBoss 2.0 Started
> > instead of
> > [Default] jBoss 2.0 Started
> >
> > b) Stopping jBoss results in some sort of immediate abort. The services
> > aren't shut down as usual.
> >
> > Should interbase.interclient.Driver be the correct class to use ?
> > Is there anyone out there who managed to get it working ?
> >
> > 2. How do I configure the test suite to only use the new data source ?
> > I've been looking for ejb-jar.xml and jboss.xml but couldn't find them
> > for the test suite.
> >
> >
> > It would be really interesting to get jBoss running with Interbase 6.0
> > as it is free and open source now (www.interbase.com).
> >
> > Bye,
> > Tobias
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
