[Geoserver-devel] interesting classpath conflict between geoserver and gwc standalone

Not sure if this is just news to me, or just a rare situation. I have been testing GeoWebCache standalone (I know right) alongside GeoServer in Tomcat 7 / Java 7.

And the result does not quite function (with deep scary messages coming out of grid coverage code). Result of a debug run with Kevin shows that image formats are being picked up twice, once from geoserver and once from geowebcache - since both have been registered with SPI they can manage to trip on each other.

As a temporary measure I can move the common libraries out to the tomcat lib folder (like we do with JDBC drivers). Or I guess for JAI and ImageIO move them out the the jre/ext ).

I guess long term I could take a fix over to GeoTools that checked classloaders.

Jody

Apparently I am mistaken, issue is showing up in Jetty (not tomcat7) which makes a fair bit more sense since Jetty is a bit more lax about classloader separation. In particular it tries to automatically recognise system classes such as “javax”.

References:

Cheers,
Jody

On Fri Dec 05 2014 at 11:05:06 AM Jody Garnett <jody.garnett@anonymised.com> wrote:

Not sure if this is just news to me, or just a rare situation. I have been testing GeoWebCache standalone (I know right) alongside GeoServer in Tomcat 7 / Java 7.

And the result does not quite function (with deep scary messages coming out of grid coverage code). Result of a debug run with Kevin shows that image formats are being picked up twice, once from geoserver and once from geowebcache - since both have been registered with SPI they can manage to trip on each other.

As a temporary measure I can move the common libraries out to the tomcat lib folder (like we do with JDBC drivers). Or I guess for JAI and ImageIO move them out the the jre/ext ).

I guess long term I could take a fix over to GeoTools that checked classloaders.

Jody

It’s showing up in both Tomcat on Ubuntu with OpenJDK and Jetty on Windows with Oracle Java.

···

On 5 December 2014 at 11:27, Jody Garnett <jody.garnett@anonymised.com> wrote:

Apparently I am mistaken, issue is showing up in Jetty (not tomcat7) which makes a fair bit more sense since Jetty is a bit more lax about classloader separation. In particular it tries to automatically recognise system classes such as “javax”.

References:

Cheers,
Jody

On Fri Dec 05 2014 at 11:05:06 AM Jody Garnett <jody.garnett@anonymised.com> wrote:

Not sure if this is just news to me, or just a rare situation. I have been testing GeoWebCache standalone (I know right) alongside GeoServer in Tomcat 7 / Java 7.

And the result does not quite function (with deep scary messages coming out of grid coverage code). Result of a debug run with Kevin shows that image formats are being picked up twice, once from geoserver and once from geowebcache - since both have been registered with SPI they can manage to trip on each other.

As a temporary measure I can move the common libraries out to the tomcat lib folder (like we do with JDBC drivers). Or I guess for JAI and ImageIO move them out the the jre/ext ).

I guess long term I could take a fix over to GeoTools that checked classloaders.

Jody


Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk


Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Kevin Smith

Junior Software Engineer | Boundless

ksmith@anonymised.com

+1-778-785-7459

@boundlessgeo

http://boundlessgeo.com/

Okay so it is not an isolated problem, lets raise an issue in GeoTools Jira and we can try and sort it out.

···

On 5 December 2014 at 11:27, Jody Garnett <jody.garnett@anonymised.com> wrote:

Apparently I am mistaken, issue is showing up in Jetty (not tomcat7) which makes a fair bit more sense since Jetty is a bit more lax about classloader separation. In particular it tries to automatically recognise system classes such as “javax”.

References:

Cheers,
Jody

On Fri Dec 05 2014 at 11:05:06 AM Jody Garnett <jody.garnett@anonymised.com403…> wrote:

Not sure if this is just news to me, or just a rare situation. I have been testing GeoWebCache standalone (I know right) alongside GeoServer in Tomcat 7 / Java 7.

And the result does not quite function (with deep scary messages coming out of grid coverage code). Result of a debug run with Kevin shows that image formats are being picked up twice, once from geoserver and once from geowebcache - since both have been registered with SPI they can manage to trip on each other.

As a temporary measure I can move the common libraries out to the tomcat lib folder (like we do with JDBC drivers). Or I guess for JAI and ImageIO move them out the the jre/ext ).

I guess long term I could take a fix over to GeoTools that checked classloaders.

Jody


Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk


Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Kevin Smith

Junior Software Engineer | Boundless

ksmith@anonymised.com

+1-778-785-7459

@boundlessgeo

http://boundlessgeo.com/