R: [Geoserver-devel] Class loading error

GeoServer GeoServer Developer
1

I'm not sure at all, but I remember something about a change
in the class loading from Tomcat 5.0.x to 5.5.x.
It was something about having a global or not-so global calss loading.
But I may be completely wrong, it's a distant memory...

Bye
Paolo Rizzi

-----Messaggio originale-----
Da: Rob Atkinson [mailto:rob@anonymised.com]
Inviato: giovedì 22 dicembre 2005 1.18
A: Geoserver-devel; geotools-devel
Oggetto: [Geoserver-devel] Class loading error

Hi,

Have uncovered a class loader issue.

Deploying under Tomcat 5.5 I got a "ClassDefNotFound" error with a
configuration that ended up executing the code in
org.geotools.data.geometryless.ConnectionPoolFacade:

    public ConnectionPoolFacade(String poolKey, String driver)
            throws SQLException {

        try {
            javax.sql.ConnectionPoolDataSource _nativePool =
(javax.sql.ConnectionPoolDataSource) (Class.forName(driver)
                    .newInstance());
            // LOGGER.fine("Obtained ConnectionPoolDataSource " +
_nativePool
            // + " from driver " + driver);

        } catch (Exception e) {
            throw new SQLException(
                    "Failed to instantiate connection pool
using " + driver
                            + "(" + e + ")");
        }
    }

But the same code in a simple JSP page worked just fine.

The same configuration, however, worked just fine in Jetty on
the same
machine.

So, there is some quirk or bug in the class loading that may
be related
to the way the datastore plugin stuff works in geoserver.

Has anyone got any insight into this beast?

I will attempt to test under Tomcat 4.1 on the same box when I get
access again.

Rob Atkinson

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep
through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web.
DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

AVVERTENZE AI SENSI DEL D. LGS. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i
file/s allegato/i, sono da considerarsi strettamente riservate. Il loro
utilizzo è consentito esclusivamente al destinatario del messaggio, per le
finalità indicate nel messaggio stesso. Qualora riceveste questo messaggio
senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia
via e-mail e di procedere alla distruzione del messaggio stesso,
cancellandolo dal Vostro sistema; costituisce comportamento contrario ai
principi dettati dal D. Lgs. 196/2003 il trattenere il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse.

2

Hmm - sounds possible, although it worked OK on windows but not SUSE linux.

Well, a bit more of a play with it today: it works on Tomcat 4.1 on the same platform. I guess I should file a Jira issue on this so its a warning at least.

Rob

P.Rizzi Ag.Mobilità Ambiente wrote:

I'm not sure at all, but I remember something about a change
in the class loading from Tomcat 5.0.x to 5.5.x.
It was something about having a global or not-so global calss loading.
But I may be completely wrong, it's a distant memory...

Bye
Paolo Rizzi

-----Messaggio originale-----
Da: Rob Atkinson [mailto:rob@anonymised.com]
Inviato: giovedì 22 dicembre 2005 1.18
A: Geoserver-devel; geotools-devel
Oggetto: [Geoserver-devel] Class loading error

Hi,

Have uncovered a class loader issue.

Deploying under Tomcat 5.5 I got a "ClassDefNotFound" error with a configuration that ended up executing the code in
org.geotools.data.geometryless.ConnectionPoolFacade:

    public ConnectionPoolFacade(String poolKey, String driver)
            throws SQLException {

        try {
            javax.sql.ConnectionPoolDataSource _nativePool = (javax.sql.ConnectionPoolDataSource) (Class.forName(driver)
                    .newInstance());
            // LOGGER.fine("Obtained ConnectionPoolDataSource " + _nativePool
            // + " from driver " + driver);

        } catch (Exception e) {
            throw new SQLException(
                    "Failed to instantiate connection pool using " + driver
                            + "(" + e + ")");
        }
    }

But the same code in a simple JSP page worked just fine.

The same configuration, however, worked just fine in Jetty on the same machine.

So, there is some quirk or bug in the class loading that may be related to the way the datastore plugin stuff works in geoserver.

Has anyone got any insight into this beast?

I will attempt to test under Tomcat 4.1 on the same box when I get access again.

Rob Atkinson

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

AVVERTENZE AI SENSI DEL D. LGS. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i
file/s allegato/i, sono da considerarsi strettamente riservate. Il loro
utilizzo è consentito esclusivamente al destinatario del messaggio, per le
finalità indicate nel messaggio stesso. Qualora riceveste questo messaggio
senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia
via e-mail e di procedere alla distruzione del messaggio stesso,
cancellandolo dal Vostro sistema; costituisce comportamento contrario ai
principi dettati dal D. Lgs. 196/2003 il trattenere il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse.