I apologize in advance for the excessive quoting. I'm using Lotus Notes,
which sucks for this sort of thing (that is to say, internet email). Ah,
well.
Anyway, thanks for the info. Since my last message I've gone and dug up
IBM's WebSphere application server advanced for Linux, which appears to
have been made available in June. I'm guessing it works with DB2, but I
haven't been able to verify that yet. I went through a tutorial to
familiarize myself with IBM's "console" UI, and at the moment there are 135
java threads/processes on my system. The load average is over 50. This is
using IBM's JDK 1.1.8 (I've tried other JDKs with WAS to no avail), where
there are no green threads available.
I have to wonder what WAS performs like on other systems. Sun's EJB
server, AFAIK, is just a reference server and isn't really intended to be
used for deployed systems, but it's good for learning. I may go back to it
for the time being if the information you provided does the trick.
As far as the advantages of EJB... By itself, I really don't know for sure.
To some extent, I think using EJB instead of pure JDBC makes it so you
don't have to think quite so hard about multi-user issues. You just tell
the server what restrictions there are on the various bean methods and it
organizes connections and transactions accordingly in what (one hopes) is
an optimal manner. Having dealt with locking and other similar issues
before, I can see a fair amount of value in that.
But for me, there's also the capabilities provided by servlets and JSP.
For what I'm doing, minimizing client side effort is a good thing. I'm
still learning all this, so that's about as much information as I can
provide :-).
"Stefan Kahle" <[EMAIL PROTECTED]> on 08/02/2000 06:59:54 AM
To: John Knutson/GISD/SGG/ARLUT
cc: [EMAIL PROTECTED]
Subject: Antwort: Re: Using DB2 w/ Sun J2EE server
Hi,
i had a similar problem running a java-servlet with access to DB2 data. My
enviroment is Linux Kernel 2.2.x, DB2 V7.1, blackdown jdk, SUN servlet
engine. I used the COM.ibm.db2.jdbc.net.DB2Driver and it run when i put the
(IP-) name of server where db2jd is running and the port of db2jd into the
datasource.
Try this:
db2jstrt 6789
jdbc.datasources=jdbc:db2://<IPName>:6789:/<dbname>
Perhaps You can tell me what the advantage of EJB in accessing the data of
a data warehouse is. I'm building a dataware house too and looking for a
good method to access the data.
/Stefan Kahle
jknutson@arlut.
utexas.edu An: [EMAIL PROTECTED]
Kopie:
27.07.00 16:15 Thema: Re: Using DB2 w/ Sun
J2EE server
Thanks to Larry Sanderson at Sun for pointing me in the right direction:
j2sdkee1.2.1/config/default.properties (documented in
doc/release/ConfigGuide.html, guess I should have RTFM)
I've had a little better success since then (after fixing the case error in
the driver name). Unfortunately I still haven't managed to get a
functional system.
As per instructions, I added the db2 driver and datasource to the
properties file, thus:
jdbc.drivers=COM.cloudscape.core.RmiJdbcDriver:COM.ibm.db2.jdbc.app.DB2Driv
er
jdbc.datasources=jdbc/Cloudscape|jdbc:cloudscape:rmi:CloudscapeDB;create=tr
ue|jdbc/db2|jdbc:db2:<dbname>
DB2 has two jdbc drivers, COM.ibm.db2.jdbc.app.DB2Driver, used for
applications, and COM.ibm.db2.jdbc.net.DB2Driver, used for applets. I've
used a sample application that uses the application driver, so I know it
works. However, the JVM used by the j2ee server dies with a SIGSEGV (and
lots and lots of debug output) if I try to use the application driver with
EJB. If I try to use the applet driver, I end up with a
java.sql.SQLException: No suitable driver. The EJB server doesn't put out
any output at all, not even to the logs, for this.
I thought there might be an issue that the drivers are actually JDBC 2.0
and not 1.2 (or whatever the earlier "latest" was/is), but there doesn't
seem to be any support for JDBC 2.0 from DB2 for linux.
It's looking like noone else has tried using this combination so I may be
stuck (or more accurately I may simply have to use bean managed persistence
everywhere), but hopefully someone out there has an idea on how to proceed
they'd be willing to share...
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
