Are the Jelly folks listening? Does anyone care? -- if no one speaks
up, you can probably expect the GUMP build of Jelly-Tags to start in the
next week or two.
james
On Fri, 2003-03-14 at 10:53, James House wrote:
Hi,
I'm the lead developer of the Quartz project
(http
On Mon, 2003-03-17 at 12:38, James House wrote:
you can probably expect the GUMP build of Jelly-Tags to start in the
next week or two.
That should have said to start breaking in the next week or two.
james
On Fri, 2003-03-14 at 10:53, James House wrote:
Hi,
I'm the lead
for such a
developer to prepare an alpha release of the tags to
tide folks over while Quartz is in flux.
- Morgan
--- James House [EMAIL PROTECTED] wrote:
Are the Jelly folks listening? Does anyone care? --
if no one speaks
up, you can probably expect the GUMP build of
Jelly-Tags to start
Hi,
I'm the lead developer of the Quartz project
(http://www.sourceforge.net/projects/quartz).
Currently Quartz is building nightly as part of the GUMP process,
because a few Jakarta projects depend on it - Jelly is one them. (see
the org.apache.commons.jelly.tags.quartz package).
Over on the
-
From: James House [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 01, 2002 10:26 AM
To: [EMAIL PROTECTED]
Subject: [POOL] Bug
I've ran into another bug with Pool / DBCP.
The problem lies in GenericObjectPool's returnObject() method.
There is no check to see if the object has already been
drivers.
So to get driver via url it must be registered first.
But to register it you have to have the driver's class instance!
James House wrote:
In the BasicDataSource.createDataSource() method, there are 2 serious
bugs in the following block of code
I've ran into another bug with Pool / DBCP.
The problem lies in GenericObjectPool's returnObject() method.
There is no check to see if the object has already been returned, it simply
adds the object back into the pool.
If the object has already been returned, then the object now appears two
In the BasicDataSource.createDataSource() method, there are 2 serious
bugs in the following block of code:
===
// Load the JDBC driver class
Class driverClass = null;
try {
driverClass =
Attempts to locate a driver that understands the given URL. The
DriverManager attempts to select an appropriate driver from the
set of registered JDBC drivers.
So to get driver via url it must be registered first.
But to register it you have to have the driver's class instance!
James House wrote
its JDBC resources from preventing
others from getting a JDBC connection.
Logging of misbehaving JSP pages and servlets is important.
I am all for adding the below patch and the option above.
It sure would have saved me some time the last few days. :-)
Regards,
Glenn
James House wrote
At 2/23/2002 01:25 PM -0600, Rodney Waldhoff wrote:
James House wrote:
A few months back I made my own hacks to
DBCP in order to have it find places in
our code that didn't free up DB resources
properly.
snip
If anyone's interested, I could try
digging it up, and posting
At 2/23/2002 01:25 PM -0600, Rodney Waldhoff wrote:
A few months back I made my own hacks to
DBCP in order to have it find places in
our code that didn't free up DB resources
properly.
I was able to generate class names and
line-numbers (stack trace) for every place
in the code
the last few days. :-)
Regards,
Glenn
James House wrote:
At 2/23/2002 01:25 PM -0600, Rodney Waldhoff wrote:
A few months back I made my own hacks to
DBCP in order to have it find places in
our code that didn't free up DB resources
properly.
I was able to generate class
At 2/22/2002 08:47 PM +0100, Juozas Baliuka wrote:
It is very dificult to find pooling related bugs in application.
May be it has meaning to implement something like DebugPool to help find
problems
in users code.
I can think about this, if this idea is interesting.
A few months back I made my
I've got a Job Scheduler project under way at Source Forge - I'm not aware
of one here at Commons.
The project began last spring, and actually was completed in the sense
that there was a release. In fact there are a number of people using
it. However, the design was really shoddy, and I
Hi,
I have a proposed correction for the class PoolableConnectionFactory.java
The method validateObject(Object object) has a block of code that
responsible for doing the test-query that currently looks like this:
if(null != query) {
Statement stmt = null;
Hi,
I have a proposed correction for the class PoolingDataSource.java
change this method:
public synchronized Connection getConnection() throws SQLException {
return (Connection)(_pool.borrowObject());
}
to be like this:
public synchronized Connection getConnection()
17 matches
Mail list logo
