[Geoserver-users] Pb with 1.6.4b

hi all,

I 've just migrated from 1.6.3 to 1.6.4b...

When i start the server :
2008-06-05 13:16:56,069 WARN [referencing.factory] - Axis elements found in a wkt definition, the force longitude first axis order hint might not be respected:
PROJCS["WGS84 / Simple Mercator", GEOGCS["WGS 84", DATUM["WGS_1984", SPHEROID["WGS_1984", 6378137.0, 298.257223563]], PRIMEM["Greenwich", 0.0], UNIT["degree", 0.017453292519943295], AXIS["Longitude", EAST], AXIS["Latitude", NORTH]], PROJECTION["Mercator_1SP_Google"], PARAMETER["latitude_of_origin", 0.0], PARAMETER["central_meridian", 0.0], PARAMETER["scale_factor", 1.0], PARAMETER["false_easting", 0.0], PARAMETER["false_northing", 0.0], UNIT["m", 1.0], AXIS["x", EAST], AXIS["y", NORTH], AUTHORITY["EPSG","900913"]]
2008-06-05 13:16:56,069 WARN [referencing.factory] - Axis elements found in a wkt definition, the force longitude first axis order hint might not be respected:
PROJCS["Albers Equal area",GEOGCS["WGS 84", DATUM["World Geodetic System 1984", SPHEROID["WGS 84", 6378137.0, 298.257223563, AUTHORITY["EPSG","7030"]], AUTHORITY["EPSG","6326"]], PRIMEM["Greenwich", 0.0, AUTHORITY["EPSG","8901"]], UNIT["degree", 0.017453292519943295], AXIS["Geodetic latitude", NORTH], AXIS["Geodetic longitude", EAST], AUTHORITY["EPSG","4326"]], PROJECTION["Albers Equal Area", AUTHORITY["EPSG","9822"]], PARAMETER["central_meridian", -96.0], PARAMETER["latitude_of_origin", 37.5], PARAMETER["standard_parallel_1", 29.833333333333336], PARAMETER["false_easting", 0.0], PARAMETER["false_northing", 0.0], PARAMETER["standard_parallel_2", 45.833333333333336], UNIT["m", 1.0], AXIS["Easting", EAST], AXIS["Northing", NORTH], AUTHORITY["EPSG","45556"]]
2008-06-05 13:16:56,070 WARN [referencing.factory] - Axis elements found in a wkt definition, the force longitude first axis order hint might not be respected:
PROJCS["WGS84 / Simple Mercator", GEOGCS["WGS 84", DATUM["WGS_1984", SPHEROID["WGS_1984", 6378137.0, 298.257223563]], PRIMEM["Greenwich", 0.0], UNIT["degree", 0.017453292519943295], AXIS["Longitude", EAST], AXIS["Latitude", NORTH]], PROJECTION["Mercator_1SP_Google"], PARAMETER["latitude_of_origin", 0.0], PARAMETER["central_meridian", 0.0], PARAMETER["scale_factor", 1.0], PARAMETER["false_easting", 0.0], PARAMETER["false_northing", 0.0], UNIT["m", 1.0], AXIS["x", EAST], AXIS["y", NORTH], AUTHORITY["EPSG","100003"]]

when i WFS request :
2008-06-05 13:19:35,786 WARN [geoserver.ows] -
java.lang.RuntimeException: Encode failed for timeStamp. Cause: com/sun/msv/datatype/xsd/datetime/CalendarFormatter
        at org.geotools.xml.impl.AttributeEncodeExecutor.visit(AttributeEncodeExecutor.java:73)
        at org.geotools.xml.impl.BindingWalker$BindingExecutionChain.execute(BindingWalker.java:197)
        at org.geotools.xml.impl.BindingWalker.walk(BindingWalker.java:163)
        at org.geotools.xml.impl.BindingWalker.walk(BindingWalker.java:167)
        at org.geotools.xml.impl.ElementEncoder.encode(ElementEncoder.java:70)
        at org.geotools.xml.Encoder.encode(Encoder.java:839)
        at org.geotools.xml.Encoder.encode(Encoder.java:681)
        at org.geotools.xml.Encoder.encode(Encoder.java:471)
        at org.geoserver.wfs.xml.GML3OutputFormat.write(GML3OutputFormat.java:123)
        ....

Caused by: java.lang.NoClassDefFoundError: com/sun/msv/datatype/xsd/datetime/CalendarFormatter
        at com.sun.msv.datatype.xsd.DateTimeBaseType.serializeJavaObject(DateTimeBaseType.java:74)
        at com.sun.xml.bind.DatatypeConverterImpl.printDateTime(DatatypeConverterImpl.java:343)
        at javax.xml.bind.DatatypeConverter.printDateTime(DatatypeConverter.java:534)
        at org.geotools.xs.bindings.XSDateTimeBinding.encode(XSDateTimeBinding.java:119)
        at org.geotools.xml.impl.AttributeEncodeExecutor.visit(AttributeEncodeExecutor.java:68)

anyone could help ?
thanks.

no response...
does it mean that i am the only one who have these pb ?

what means 'Axis elements found in a wkt definition, the force longitude first axis order hint might not be respected' ???

Sébastien Geindre a écrit :

hi all,

I 've just migrated from 1.6.3 to 1.6.4b...

When i start the server :
2008-06-05 13:16:56,069 WARN [referencing.factory] - Axis elements found in a wkt definition, the force longitude first axis order hint might not be respected:
PROJCS["WGS84 / Simple Mercator", GEOGCS["WGS 84", DATUM["WGS_1984", SPHEROID["WGS_1984", 6378137.0, 298.257223563]], PRIMEM["Greenwich", 0.0], UNIT["degree", 0.017453292519943295], AXIS["Longitude", EAST], AXIS["Latitude", NORTH]], PROJECTION["Mercator_1SP_Google"], PARAMETER["latitude_of_origin", 0.0], PARAMETER["central_meridian", 0.0], PARAMETER["scale_factor", 1.0], PARAMETER["false_easting", 0.0], PARAMETER["false_northing", 0.0], UNIT["m", 1.0], AXIS["x", EAST], AXIS["y", NORTH], AUTHORITY["EPSG","900913"]]
2008-06-05 13:16:56,069 WARN [referencing.factory] - Axis elements found in a wkt definition, the force longitude first axis order hint might not be respected:
PROJCS["Albers Equal area",GEOGCS["WGS 84", DATUM["World Geodetic System 1984", SPHEROID["WGS 84", 6378137.0, 298.257223563, AUTHORITY["EPSG","7030"]], AUTHORITY["EPSG","6326"]], PRIMEM["Greenwich", 0.0, AUTHORITY["EPSG","8901"]], UNIT["degree", 0.017453292519943295], AXIS["Geodetic latitude", NORTH], AXIS["Geodetic longitude", EAST], AUTHORITY["EPSG","4326"]], PROJECTION["Albers Equal Area", AUTHORITY["EPSG","9822"]], PARAMETER["central_meridian", -96.0], PARAMETER["latitude_of_origin", 37.5], PARAMETER["standard_parallel_1", 29.833333333333336], PARAMETER["false_easting", 0.0], PARAMETER["false_northing", 0.0], PARAMETER["standard_parallel_2", 45.833333333333336], UNIT["m", 1.0], AXIS["Easting", EAST], AXIS["Northing", NORTH], AUTHORITY["EPSG","45556"]]
2008-06-05 13:16:56,070 WARN [referencing.factory] - Axis elements found in a wkt definition, the force longitude first axis order hint might not be respected:
PROJCS["WGS84 / Simple Mercator", GEOGCS["WGS 84", DATUM["WGS_1984", SPHEROID["WGS_1984", 6378137.0, 298.257223563]], PRIMEM["Greenwich", 0.0], UNIT["degree", 0.017453292519943295], AXIS["Longitude", EAST], AXIS["Latitude", NORTH]], PROJECTION["Mercator_1SP_Google"], PARAMETER["latitude_of_origin", 0.0], PARAMETER["central_meridian", 0.0], PARAMETER["scale_factor", 1.0], PARAMETER["false_easting", 0.0], PARAMETER["false_northing", 0.0], UNIT["m", 1.0], AXIS["x", EAST], AXIS["y", NORTH], AUTHORITY["EPSG","100003"]]

when i WFS request :
2008-06-05 13:19:35,786 WARN [geoserver.ows] -
java.lang.RuntimeException: Encode failed for timeStamp. Cause: com/sun/msv/datatype/xsd/datetime/CalendarFormatter
        at org.geotools.xml.impl.AttributeEncodeExecutor.visit(AttributeEncodeExecutor.java:73)
        at org.geotools.xml.impl.BindingWalker$BindingExecutionChain.execute(BindingWalker.java:197)
        at org.geotools.xml.impl.BindingWalker.walk(BindingWalker.java:163)
        at org.geotools.xml.impl.BindingWalker.walk(BindingWalker.java:167)
        at org.geotools.xml.impl.ElementEncoder.encode(ElementEncoder.java:70)
        at org.geotools.xml.Encoder.encode(Encoder.java:839)
        at org.geotools.xml.Encoder.encode(Encoder.java:681)
        at org.geotools.xml.Encoder.encode(Encoder.java:471)
        at org.geoserver.wfs.xml.GML3OutputFormat.write(GML3OutputFormat.java:123)
        ....

Caused by: java.lang.NoClassDefFoundError: com/sun/msv/datatype/xsd/datetime/CalendarFormatter
        at com.sun.msv.datatype.xsd.DateTimeBaseType.serializeJavaObject(DateTimeBaseType.java:74)
        at com.sun.xml.bind.DatatypeConverterImpl.printDateTime(DatatypeConverterImpl.java:343)
        at javax.xml.bind.DatatypeConverter.printDateTime(DatatypeConverter.java:534)
        at org.geotools.xs.bindings.XSDateTimeBinding.encode(XSDateTimeBinding.java:119)
        at org.geotools.xml.impl.AttributeEncodeExecutor.visit(AttributeEncodeExecutor.java:68)

anyone could help ?
thanks.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Hi Sébastien,

Apologies for noone responding to you earlier. The message about the Axis order is probably unrelated to your project. Its mostly about how GeoServer deals with axis order with respect to the google 900913 projection.

So it seems there is a problem with one of the libraries that GeoServer uses to encode dates. Can you give me a bit more information about the upgrade? Are you running in a servlet container or standalone jetty install? Are the old installation and the new installation completely separated?

It would also help if you told us a little about the data you are using? Which backend data source?

-Justin

Sébastien Geindre wrote:

no response...
does it mean that i am the only one who have these pb ?

what means 'Axis elements found in a wkt definition, the force longitude first axis order hint might not be respected' ???

Sébastien Geindre a écrit :

hi all,

I 've just migrated from 1.6.3 to 1.6.4b...

When i start the server :
2008-06-05 13:16:56,069 WARN [referencing.factory] - Axis elements found in a wkt definition, the force longitude first axis order hint might not be respected:
PROJCS["WGS84 / Simple Mercator", GEOGCS["WGS 84", DATUM["WGS_1984", SPHEROID["WGS_1984", 6378137.0, 298.257223563]], PRIMEM["Greenwich", 0.0], UNIT["degree", 0.017453292519943295], AXIS["Longitude", EAST], AXIS["Latitude", NORTH]], PROJECTION["Mercator_1SP_Google"], PARAMETER["latitude_of_origin", 0.0], PARAMETER["central_meridian", 0.0], PARAMETER["scale_factor", 1.0], PARAMETER["false_easting", 0.0], PARAMETER["false_northing", 0.0], UNIT["m", 1.0], AXIS["x", EAST], AXIS["y", NORTH], AUTHORITY["EPSG","900913"]]
2008-06-05 13:16:56,069 WARN [referencing.factory] - Axis elements found in a wkt definition, the force longitude first axis order hint might not be respected:
PROJCS["Albers Equal area",GEOGCS["WGS 84", DATUM["World Geodetic System 1984", SPHEROID["WGS 84", 6378137.0, 298.257223563, AUTHORITY["EPSG","7030"]], AUTHORITY["EPSG","6326"]], PRIMEM["Greenwich", 0.0, AUTHORITY["EPSG","8901"]], UNIT["degree", 0.017453292519943295], AXIS["Geodetic latitude", NORTH], AXIS["Geodetic longitude", EAST], AUTHORITY["EPSG","4326"]], PROJECTION["Albers Equal Area", AUTHORITY["EPSG","9822"]], PARAMETER["central_meridian", -96.0], PARAMETER["latitude_of_origin", 37.5], PARAMETER["standard_parallel_1", 29.833333333333336], PARAMETER["false_easting", 0.0], PARAMETER["false_northing", 0.0], PARAMETER["standard_parallel_2", 45.833333333333336], UNIT["m", 1.0], AXIS["Easting", EAST], AXIS["Northing", NORTH], AUTHORITY["EPSG","45556"]]
2008-06-05 13:16:56,070 WARN [referencing.factory] - Axis elements found in a wkt definition, the force longitude first axis order hint might not be respected:
PROJCS["WGS84 / Simple Mercator", GEOGCS["WGS 84", DATUM["WGS_1984", SPHEROID["WGS_1984", 6378137.0, 298.257223563]], PRIMEM["Greenwich", 0.0], UNIT["degree", 0.017453292519943295], AXIS["Longitude", EAST], AXIS["Latitude", NORTH]], PROJECTION["Mercator_1SP_Google"], PARAMETER["latitude_of_origin", 0.0], PARAMETER["central_meridian", 0.0], PARAMETER["scale_factor", 1.0], PARAMETER["false_easting", 0.0], PARAMETER["false_northing", 0.0], UNIT["m", 1.0], AXIS["x", EAST], AXIS["y", NORTH], AUTHORITY["EPSG","100003"]]

when i WFS request :
2008-06-05 13:19:35,786 WARN [geoserver.ows] -
java.lang.RuntimeException: Encode failed for timeStamp. Cause: com/sun/msv/datatype/xsd/datetime/CalendarFormatter
        at org.geotools.xml.impl.AttributeEncodeExecutor.visit(AttributeEncodeExecutor.java:73)
        at org.geotools.xml.impl.BindingWalker$BindingExecutionChain.execute(BindingWalker.java:197)
        at org.geotools.xml.impl.BindingWalker.walk(BindingWalker.java:163)
        at org.geotools.xml.impl.BindingWalker.walk(BindingWalker.java:167)
        at org.geotools.xml.impl.ElementEncoder.encode(ElementEncoder.java:70)
        at org.geotools.xml.Encoder.encode(Encoder.java:839)
        at org.geotools.xml.Encoder.encode(Encoder.java:681)
        at org.geotools.xml.Encoder.encode(Encoder.java:471)
        at org.geoserver.wfs.xml.GML3OutputFormat.write(GML3OutputFormat.java:123)
        ....

Caused by: java.lang.NoClassDefFoundError: com/sun/msv/datatype/xsd/datetime/CalendarFormatter
        at com.sun.msv.datatype.xsd.DateTimeBaseType.serializeJavaObject(DateTimeBaseType.java:74)
        at com.sun.xml.bind.DatatypeConverterImpl.printDateTime(DatatypeConverterImpl.java:343)
        at javax.xml.bind.DatatypeConverter.printDateTime(DatatypeConverter.java:534)
        at org.geotools.xs.bindings.XSDateTimeBinding.encode(XSDateTimeBinding.java:119)
        at org.geotools.xml.impl.AttributeEncodeExecutor.visit(AttributeEncodeExecutor.java:68)

anyone could help ?
thanks.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

!DSPAM:4007,484da520213781137850744!

--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com

Thanks for answering :wink: !
Justin Deoliveira a écrit :

So it seems there is a problem with one of the libraries that GeoServer uses to encode dates. Can you give me a bit more information about the upgrade? Are you running in a servlet container or standalone jetty install? Are the old installation and the new installation completely separated?

i deployed the geoserver-1.6.4b.war in tomcat

It would also help if you told us a little about the data you are using? Which backend data source?

i use postgis, all date are like this one :
issue_time timestamp with time zone

-Justin

moved from 1.6.0.RC3 to 1.6.4b.
sorry for that mistake

Sébastien Geindre a écrit :

Thanks for answering :wink: !
Justin Deoliveira a écrit :
  

So it seems there is a problem with one of the libraries that GeoServer uses to encode dates. Can you give me a bit more information about the upgrade? Are you running in a servlet container or standalone jetty install? Are the old installation and the new installation completely separated?
    

i deployed the geoserver-1.6.4b.war in tomcat
  

It would also help if you told us a little about the data you are using? Which backend data source?
    

i use postgis, all date are like this one :
issue_time timestamp with time zone
  

-Justin
    
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Upgrading Geoserver
Is there any tutorial on how to upgrade from une version to another?
..or it is so trivial that no one wrote down the instructions.

As far as I can understand it shoud consist in just replacing the whole geoserver folder and restoring the data_dir but i wonder if the previously pubblished shapefiles will keep their SLDs and the other settings.

Marco Foi

Hi Sébastien,

I tried out 1.6.4b with tomcat and with a postgis database with a timestamp column similar to this and could not reproduce the problem. From the error message I would assume its a problem with your installation. I would ensure that there is no possibility of their being any copies of the any of the geoserver libraries on your classpath.

One thing that might be useful is if you were to try out the regular binary / jetty install to see if you have the same problem.

Sébastien Geindre wrote:

moved from 1.6.0.RC3 to 1.6.4b.
sorry for that mistake

Sébastien Geindre a écrit :

Thanks for answering :wink: !
Justin Deoliveira a écrit :
  

So it seems there is a problem with one of the libraries that GeoServer uses to encode dates. Can you give me a bit more information about the upgrade? Are you running in a servlet container or standalone jetty install? Are the old installation and the new installation completely separated?
    

i deployed the geoserver-1.6.4b.war in tomcat
  

It would also help if you told us a little about the data you are using? Which backend data source?
    

i use postgis, all date are like this one :
issue_time timestamp with time zone
  

-Justin
    
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

!DSPAM:4007,484e5921220221849620573!

--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com

Marco Foi ha scritto:

Upgrading Geoserver
Is there any tutorial on how to upgrade from une version to another?
..or it is so trivial that no one wrote down the instructions.

As far as I can understand it shoud consist in just replacing the whole geoserver folder and restoring the data_dir but i wonder if the previously pubblished shapefiles will keep their SLDs and the other settings.

Everything should keep its settings unless you moved files around.
Just copy the data directory or make the new geoserver use the
one you already have by setting the GEOSERVER_DATA_DIR param
in web.xml and you should be ok.

Cheers
Andrea

Is it possible to have 2 GEOSERVER_DATA_DIR served by 2 different geoserver deployed as war application in tomcat container for example ??

Andrea Aime a écrit :

Marco Foi ha scritto:
  

Upgrading Geoserver
Is there any tutorial on how to upgrade from une version to another?
..or it is so trivial that no one wrote down the instructions.

As far as I can understand it shoud consist in just replacing the whole geoserver folder and restoring the data_dir but i wonder if the previously pubblished shapefiles will keep their SLDs and the other settings.
    
Everything should keep its settings unless you moved files around.
Just copy the data directory or make the new geoserver use the
one you already have by setting the GEOSERVER_DATA_DIR param
in web.xml and you should be ok.

Cheers
Andrea

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Sébastien Geindre ha scritto:

Is it possible to have 2 GEOSERVER_DATA_DIR served by 2 different geoserver deployed as war application in tomcat container for example ??

Yes, it is, we do it all the time in OpenPlans. Setup two different
data directories, unpack the geoserver.war into a directory structure,
copy it and call the two copies gs1 and gs2.
Enter the gs1/WEB-INF/web.xml and change the web.xml so that
GEOSERVER_DATA_DIR points to the first data directory (and
remove the comment markers around that param, otherwise geoserver
won't read it), do the same with the second copy.
Move the two directories into the deploy area of your web container
and you're done, now you have two geoservers using separate
data directories at:
http://localhost:8080/gs1
http://localhost:8080/gs2

Hope this helps.
If you two want to put togheter a "deploy and
upgrade" howto for GeoSever, well, that would be very cool :slight_smile:

Cheers
Andrea

thanks.

i try again and it works.
i suppressed old geoserver (1.3) before...

i think it is impossible to deploy 2 different versions of geoserver...:wink:

Justin Deoliveira a écrit :

Hi Sébastien,

I tried out 1.6.4b with tomcat and with a postgis database with a timestamp column similar to this and could not reproduce the problem. From the error message I would assume its a problem with your installation. I would ensure that there is no possibility of their being any copies of the any of the geoserver libraries on your classpath.

One thing that might be useful is if you were to try out the regular binary / jetty install to see if you have the same problem.

Sébastien Geindre wrote:

moved from 1.6.0.RC3 to 1.6.4b.
sorry for that mistake

Sébastien Geindre a écrit :

Thanks for answering :wink: !
Justin Deoliveira a écrit :

So it seems there is a problem with one of the libraries that GeoServer uses to encode dates. Can you give me a bit more information about the upgrade? Are you running in a servlet container or standalone jetty install? Are the old installation and the new installation completely separated?
    

i deployed the geoserver-1.6.4b.war in tomcat

It would also help if you told us a little about the data you are using? Which backend data source?
    

i use postgis, all date are like this one :
issue_time timestamp with time zone

-Justin
    
-------------------------------------------------------------------------

Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

-------------------------------------------------------------------------

Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

!DSPAM:4007,484e5921220221849620573!

Sébastien Geindre ha scritto:

thanks.

i try again and it works.
i suppressed old geoserver (1.3) before...

i think it is impossible to deploy 2 different versions of geoserver...:wink:

It was impossible up to 1.5.something due to a problem in GeoTools,
but that has since been fixed afaik.
Cheers
Andrea