[Geoserver-users] geoserver-1.4.1-war.zip deploys fine within tomcat but geoserver-1.5.0-RC3-war.zip does not

Hi,

I deployed geoserver-1.4.1-war.zip which deploys fine within tomcat but geoserver-1.5.0-RC3-war.zip does not and has the following error:

FAIL - Application at context path /geoserver could not be started

Thanks,


John J. Mitchell

John Mitchell ha scritto:

Hi,

I deployed geoserver-1.4.1-war.zip which deploys fine within tomcat but geoserver-1.5.0-RC3-war.zip does not and has the following error:

FAIL - Application at context path /geoserver could not be started

John, thanks for the report.
Unfortunately we need more to address this issue: can you provide us
with a full log of the application start?

Cheers
Andrea

Andrea,

I have attached the log file.

Thanks,

John Mitchell

On 3/28/07, Andrea Aime <aaime@anonymised.com > wrote:

John Mitchell ha scritto:

Hi,

I deployed geoserver-1.4.1-war.zip which deploys fine within tomcat but
geoserver-1.5.0-RC3-war.zip does not and has the following error:

FAIL - Application at context path /geoserver could not be started

John, thanks for the report.
Unfortunately we need more to address this issue: can you provide us
with a full log of the application start?

Cheers
Andrea


John J. Mitchell

localhost.2007-03-28.log (21.2 KB)

John Mitchell ha scritto:

Andrea,

I have attached the log file.

Ouch!

org.springframework.beans.FatalBeanException: Could not instantiate class [org.vfny.geoserver.global.GeoServer]; constructor threw exception; nested exception is java.lang.NoSuchFieldError: KEY_CACHED_TILE_RECYCLING_ENABLED
java.lang.NoSuchFieldError: KEY_CACHED_TILE_RECYCLING_ENABLED
  at org.vfny.geoserver.global.GeoServer.initJAI(GeoServer.java:502)
  at org.vfny.geoserver.global.GeoServer.load(GeoServer.java:361)

It seems you have an old JAI installed in your java runtime. Can you tell me which version do you have, I would like to put a warning in the user guide.

You have two possible solutions:
* upgrade your JAI install to a more recent one. Geoserver 1.5.x
   requires the last stable version of both JAI and JAI image i/o
* remove JAI altogheter from your JDK/JRE, and Geoserver will use the
   pure java versions it has in his classpath (that will slow down
   raster handling compared to an install that has the right native
   JAI, but at least it'll work).

Cheers
Andrea

Hi,

I just downloaded the latest stable version 2 days ago: jai 1.1.3 and the actual file name is below:

jai-1_1_3-lib-windows-i586-jdk.exe

John Mitchell

On 3/28/07, Andrea Aime <aaime@anonymised.com> wrote:

John Mitchell ha scritto:

Andrea,

I have attached the log file.

Ouch!

org.springframework.beans.FatalBeanException: Could not instantiate
class [org.vfny.geoserver.global.GeoServer ]; constructor threw
exception; nested exception is java.lang.NoSuchFieldError:
KEY_CACHED_TILE_RECYCLING_ENABLED
java.lang.NoSuchFieldError: KEY_CACHED_TILE_RECYCLING_ENABLED
at org.vfny.geoserver.global.GeoServer.initJAI (GeoServer.java:502)
at org.vfny.geoserver.global.GeoServer.load(GeoServer.java:361)

It seems you have an old JAI installed in your java runtime. Can you
tell me which version do you have, I would like to put a warning in the
user guide.

You have two possible solutions:

  • upgrade your JAI install to a more recent one. Geoserver 1.5.x
    requires the last stable version of both JAI and JAI image i/o
  • remove JAI altogheter from your JDK/JRE, and Geoserver will use the
    pure java versions it has in his classpath (that will slow down
    raster handling compared to an install that has the right native
    JAI, but at least it’ll work).

Cheers
Andrea


John J. Mitchell

John Mitchell ha scritto:

Hi,

I just downloaded the latest stable version 2 days ago: jai 1.1.3 and the actual file name is below:

jai-1_1_3-lib-windows-i586-jdk.exe

Strange, according to http://java.sun.com/products/java-media/jai/forDevelopers/jai-apidocs/javax/media/jai/JAI.html#KEY_CACHED_TILE_RECYCLING_ENABLED

that constant has been around since 1.1.2 (so it's pretty recent).

Can you double check? It may be you have multiple jdk, and the container
is running on top of a different one than the one you updated?
Cheers
Andrea