on 5/26/2000 12:17 PM, Rafal Krzewski at [EMAIL PROTECTED] wrote:

> Here are the results of my testing of Turbine under different environments.
> I have no serious test suite - just WebMacroSite from the example and
> user administration module.

awesome! i'm having a hard time keeping up with you. this is great! :-)

> I'm using Debian/GNU 2.2 running Linux 2.2.15 on x86 machine.
> JDK is IBM 1.3.  I had some nasty crashes of vm, for examle while
> compiling with *certain builds* of Ant, and during restarting WebLogic
> from it's Swing based console, so now, I'm not so sure about
> using it in production environment. It seems much faster than
> Sun 1.2.2 though.
> I'm always running CVS Turbine, updated approx. twice daily.

ya...not much we can do here about JVM problems. :-(

> First, I was running uder Jserv 1.1 over Apache 1.3.9. Everything was
> OK.

cool.

> Then I moved to Jakarta Tomcat 3.1 - It may be not complete, but
> servlets 2.2 are definetly better than 2.0.

cool.

> Running Turbine/Webmacro went really smooth.

YES!

> I was using MySQL 3.22 for Turbine, but since I installed Sybase ASE 11.9.2
> for Linux lately, I moved Turbines DB to Sybase, and tweaked Turbine and
> Village
> a little bit to make it work.

i just committed your changes. will do a release of Village today.

> Then, I tried running Turbine under WebLogic. It's working, but theres a
> strange
> error: upon first request I get the following exception:
> 
> java.lang.NullPointerException
> at Turbine.doGet(Turbine.java:375)
> and since then, everything's working OK.

I just checked in a change in that should prevent this from happening again.
i hate NPE's. :-(

> I tried using weblogic.jdbc.pool driver for Turbine and it was OK - both
> running
> the pool on top of MySQL and Sybase connection.

cool! originally (years ago now) Turbine was written against the Weblogic
engine so this code should work pretty well.

> The only probem occured when I tried to use direct Sybase connection:
> Turbine *really* went down, displaing the above exception on the first hit,
> 'Infinite redirect detected' message from Turbine.class on the second
> and 'Exception: java.lang.ClassCircularityError:
> com/sybase/jdbc2/timedio/SocketDbio'
> exception followed by page and a half stack trace on the third.
> Something is seriously messed up, probably the Sybase driver that comes with
> WebLogic. If I find a solution for this, I let you know.

Sybase sucks.

> Apache 1.3.9 + JServ 1.1 + MySQL 3.22 OK
> Tomcat 3.1 + MySQL 3.22 OK
> Tomcat 3.1 + Sybase ASE 11.9.2  OK
> WebLogic 5.1+ MySQL 3.22 OK
> WebLogic 5.1+ weblogic.jdbc.pool over MySQL 3.22  OK
> WebLogic 5.1+ weblogic.jdbc.pool over Sybase ASE 11.9.2  OK
> WebLogic 5.1 + Sybase ASE 11.9.2 FAILED (but I'm not giving up yet!)

awesome...thanks for doing this testing. it is really appreciated. keep up
the great work! :-)

also, my development is against fairly recent CVS versions of Tomcat and it
works well with that as well...

thanks,

-jon



------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to