Now it works using the old turbine-pool.jar!
I just needed to restart the servlet engine!!! How silly!
And the result is amazing! My DB connection time passed from 1.5 s to a
value I cannot even notice anymore!
Turbine rocks!
- Tony
> > > I'm trying to use Turbine connection pooling. I just need this
> > feature so I
> > > didn't install turbine. I just copied the turbine-pool.jar in
> > the tomcat lib
> > > folder
> >
> > Well, that .jar file is no longer valid anymore. Just use the
> turbine.jar.
> > Having the rest of the classes in there doesn't hurt anything
> because they
> > aren't used unless necessary.
>
> My machine got Tomcat and cocoon 1.8.2 installed and runnig and I
> got the turbine-pool.jar from the cocoon installation. The tricky
> is that I need to use the connection pooling outside of cocoon.
>
> So to create a turbine.jar, I'll have to build it. So basically I
> unzipped (i'm under windows2000) into a tdk folder and when I
> call newapp.bat, I get a
>
> java.lang.SecurityException: sealing violation
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:236)
> [..]
>
> > Do you also have the code for that driver in the classpath?
>
> Yes. Because I am usig my DB2 jdbc driver without connection pool
> and without problem like this:
>
> Class.forName ("COM.ibm.db2.jdbc.app.DB2Driver").newInstance ();
> // load database interface
> m_Conn = DriverManager.getConnection("jdbc:db2:" + DB , User ,
> Password); // Set the connection
>
> - tony
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
