Hi there,
We just install the new version Geoserver 2.4 and from now we seem to receive some strange date format in our request.
All date output create by our trigger look like this: 1969-12-31.
Is there maybe a bug in the 2.4 version ?
Martin C.
Hi Martin,
That’s the ISO standard for date formatting. https://en.wikipedia.org/wiki/ISO_8601
Could you be clearer what the problem is for you?
Jonathan
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
···
On 17 October 2013 19:38, Chamberland, Martin <Martin.Chamberland@anonymised.com> wrote:
Hi there,
We just install the new version Geoserver 2.4 and from now we seem to receive some strange date format in our request.
All date output create by our trigger look like this: 1969-12-31.
Is there maybe a bug in the 2.4 version ?
Martin C.
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Did you have time to take a look at our problem ?
Thank’s!
Martin C.
De : Jonathan Moules [mailto:jonathanmoules@anonymised.com]
Envoyé : 21 octobre 2013 08:40
À : Chamberland, Martin
Cc : geoserver-users@anonymised.comourceforge.net
Objet : Re: [Geoserver-users] date BUG 2.4 Geoserver
Hi Martin,
That’s the ISO standard for date formatting. https://en.wikipedia.org/wiki/ISO_8601
Could you be clearer what the problem is for you?
Jonathan
On 17 October 2013 19:38, Chamberland, Martin <Martin.Chamberland@anonymised.com> wrote:
Hi there,
We just install the new version Geoserver 2.4 and from now we seem to receive some strange date format in our request.
All date output create by our trigger look like this: 1969-12-31.
Is there maybe a bug in the 2.4 version ?
Martin C.
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
Hi Martin,
I’m not sure what you’re asking here - without further information I suspect you won’t get any help as it’s not clear what you want.
Jonathan
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
···
On 22 October 2013 14:32, Chamberland, Martin <Martin.Chamberland@anonymised.com> wrote:
Did you have time to take a look at our problem ?
Thank’s!
Martin C.
De : Jonathan Moules [mailto:jonathanmoules@anonymised.com]
Envoyé : 21 octobre 2013 08:40
À : Chamberland, Martin
Cc : geoserver-users@lists.sourceforge.net
Objet : Re: [Geoserver-users] date BUG 2.4 GeoserverHi Martin,
That’s the ISO standard for date formatting. https://en.wikipedia.org/wiki/ISO_8601
Could you be clearer what the problem is for you?
Jonathan
On 17 October 2013 19:38, Chamberland, Martin <Martin.Chamberland@anonymised.com> wrote:
Hi there,
We just install the new version Geoserver 2.4 and from now we seem to receive some strange date format in our request.
All date output create by our trigger look like this: 1969-12-31.
Is there maybe a bug in the 2.4 version ?
Martin C.
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-usersThis transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
On Tue, Oct 22, 2013 at 3:32 PM, Chamberland, Martin <
Martin.Chamberland@anonymised.com> wrote:
Did you have time to take a look at our problem ?
As Jonathan already pointed out, the output you are getting seems to be
correct.
OGC services are supposed to return the dates in ISO format, not in a
language specific one,
e.g., if you have a WFS service returning a date in a format such as 12/31/1969
it's definitely
broken.
Maybe you should explain better what format you are using, and what date
you are expecting
in the output.
Cheers
Andrea
--
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
It’s pretty hard for me to explain correctly because english in not my first language. Let’s try my best.
We where running geoserver 2.2.3 for a long time and everything was running fine. The only problem (that is not one) we had was that in the output date, there was a “Z” after all date.
So we were sure that is was a bug, so we decide to update to geoserver 2.4 (latest one) to fix the issue. Meantine (continuing searching) we discover that it’s not a bug but just normal that the “Z” appear there. But as we where now running 2.4, now all date that we output from our Oracle database are “1969-12-31”, every date are the same.
I hope i was enough clear, sorry again for poor English explanation.
Martin C.
De : Jonathan Moules [mailto:jonathanmoules@anonymised.com]
Envoyé : 22 octobre 2013 09:50
À : Chamberland, Martin
Cc : geoserver-users@anonymised.comourceforge.net
Objet : Re: [Geoserver-users] date BUG 2.4 Geoserver
Hi Martin,
I’m not sure what you’re asking here - without further information I suspect you won’t get any help as it’s not clear what you want.
Jonathan
On 22 October 2013 14:32, Chamberland, Martin <Martin.Chamberland@anonymised.com> wrote:
Did you have time to take a look at our problem ?
Thank’s!
Martin C.
De : Jonathan Moules [mailto:jonathanmoules@anonymised.com]
Envoyé : 21 octobre 2013 08:40
À : Chamberland, Martin
Cc : geoserver-users@lists.sourceforge.net
Objet : Re: [Geoserver-users] date BUG 2.4 Geoserver
Hi Martin,
That’s the ISO standard for date formatting. https://en.wikipedia.org/wiki/ISO_8601
Could you be clearer what the problem is for you?
Jonathan
On 17 October 2013 19:38, Chamberland, Martin <Martin.Chamberland@anonymised.com> wrote:
Hi there,
We just install the new version Geoserver 2.4 and from now we seem to receive some strange date format in our request.
All date output create by our trigger look like this: 1969-12-31.
Is there maybe a bug in the 2.4 version ?
Martin C.
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
I believe the problem that Martin is having is that all the dates are the epoch (1969-12-31), in other words, the app is not reading the system time, or the system time (use ‘date’ on a Unix system) is seriously messed up. The problem is probably going to me in whatever code is accessing system time (new Date() for example. Did geoserver change anything about accessing system time in the 2.4 release?
···
On Wed, Oct 23, 2013 at 5:40 AM, Chamberland, Martin <Martin.Chamberland@anonymised.com.2842…> wrote:
It’s pretty hard for me to explain correctly because english in not my first language. Let’s try my best.
We where running geoserver 2.2.3 for a long time and everything was running fine. The only problem (that is not one) we had was that in the output date, there was a “Z” after all date.
So we were sure that is was a bug, so we decide to update to geoserver 2.4 (latest one) to fix the issue. Meantine (continuing searching) we discover that it’s not a bug but just normal that the “Z” appear there. But as we where now running 2.4, now all date that we output from our Oracle database are “1969-12-31”, every date are the same.
I hope i was enough clear, sorry again for poor English explanation.
Martin C.
De : Jonathan Moules [mailto:jonathanmoules@anonymised.com]
Envoyé : 22 octobre 2013 09:50
À : Chamberland, Martin
Cc : geoserver-users@lists.sourceforge.net
Objet : Re: [Geoserver-users] date BUG 2.4 GeoserverHi Martin,
I’m not sure what you’re asking here - without further information I suspect you won’t get any help as it’s not clear what you want.
Jonathan
On 22 October 2013 14:32, Chamberland, Martin <Martin.Chamberland@anonymised.com> wrote:
Did you have time to take a look at our problem ?
Thank’s!
Martin C.
De : Jonathan Moules [mailto:jonathanmoules@anonymised.com]
Envoyé : 21 octobre 2013 08:40
À : Chamberland, Martin
Cc : geoserver-users@lists.sourceforge.net
Objet : Re: [Geoserver-users] date BUG 2.4 GeoserverHi Martin,
That’s the ISO standard for date formatting. https://en.wikipedia.org/wiki/ISO_8601
Could you be clearer what the problem is for you?
Jonathan
On 17 October 2013 19:38, Chamberland, Martin <Martin.Chamberland@anonymised.com> wrote:
Hi there,
We just install the new version Geoserver 2.4 and from now we seem to receive some strange date format in our request.
All date output create by our trigger look like this: 1969-12-31.
Is there maybe a bug in the 2.4 version ?
Martin C.
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-usersThis transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
On Wed, Oct 23, 2013 at 5:21 PM, Garey Mills <gmills@anonymised.com>wrote:
I believe the problem that Martin is having is that all the dates are the
epoch (1969-12-31), in other words, the app is not reading the system
time, or the system time (use 'date' on a Unix system) is seriously messed
up. The problem is probably going to me in whatever code is accessing
system time (new Date() for example. Did geoserver change anything about
accessing system time in the 2.4 release?
Had a quick look, don't see anything in the last year of changes...
Unfortunately cannot do a quick test locally, reinstalled my machine
recently and Oracle is super-duper painful
to install on Ubuntu, waiting for some real work to justify spending half a
day getting the sucker up again.
Cheers
Andrea
--
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
We run Geoserver 2.4 on Debian Wheezy 7.2 server. (in fact still not up to date, 7.1 server)
bye
De : Garey Mills [mailto:gmills@anonymised.com]
Envoyé : 23 octobre 2013 11:21
À : Chamberland, Martin
Cc : Jonathan Moules; geoserver-users@lists.sourceforge.net
Objet : Re: [Geoserver-users] date BUG 2.4 Geoserver
I believe the problem that Martin is having is that all the dates are the epoch (1969-12-31), in other words, the app is not reading the system time, or the system time (use ‘date’ on a Unix system) is seriously messed up. The problem is probably going to me in whatever code is accessing system time (new Date() for example. Did geoserver change anything about accessing system time in the 2.4 release?
On Wed, Oct 23, 2013 at 5:40 AM, Chamberland, Martin <Martin.Chamberland@anonymised.com> wrote:
It’s pretty hard for me to explain correctly because english in not my first language. Let’s try my best.
We where running geoserver 2.2.3 for a long time and everything was running fine. The only problem (that is not one) we had was that in the output date, there was a “Z” after all date.
So we were sure that is was a bug, so we decide to update to geoserver 2.4 (latest one) to fix the issue. Meantine (continuing searching) we discover that it’s not a bug but just normal that the “Z” appear there. But as we where now running 2.4, now all date that we output from our Oracle database are “1969-12-31”, every date are the same.
I hope i was enough clear, sorry again for poor English explanation.
Martin C.
De : Jonathan Moules [mailto:jonathanmoules@anonymised.com]
Envoyé : 22 octobre 2013 09:50
À : Chamberland, Martin
Cc : geoserver-users@lists.sourceforge.net
Objet : Re: [Geoserver-users] date BUG 2.4 Geoserver
Hi Martin,
I’m not sure what you’re asking here - without further information I suspect you won’t get any help as it’s not clear what you want.
Jonathan
On 22 October 2013 14:32, Chamberland, Martin <Martin.Chamberland@anonymised.com> wrote:
Did you have time to take a look at our problem ?
Thank’s!
Martin C.
De : Jonathan Moules [mailto:jonathanmoules@anonymised.com]
Envoyé : 21 octobre 2013 08:40
À : Chamberland, Martin
Cc : geoserver-users@lists.sourceforge.net
Objet : Re: [Geoserver-users] date BUG 2.4 Geoserver
Hi Martin,
That’s the ISO standard for date formatting. https://en.wikipedia.org/wiki/ISO_8601
Could you be clearer what the problem is for you?
Jonathan
On 17 October 2013 19:38, Chamberland, Martin <Martin.Chamberland@anonymised.com.2842…> wrote:
Hi there,
We just install the new version Geoserver 2.4 and from now we seem to receive some strange date format in our request.
All date output create by our trigger look like this: 1969-12-31.
Is there maybe a bug in the 2.4 version ?
Martin C.
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Our Linux server, Debian Wheezy 7.2 is configure to use NTP.
Command just ran couple of minutes ago: #date
jeudi 24 octobre 2013, 08:18:49 (UTC-0400)
Everything looks good from my point.
Any other thing i’m not aware of on my Linux server ?
Thx Garey !
Martin C.
De : Garey Mills [mailto:gmills@anonymised.com]
Envoyé : 23 octobre 2013 11:21
À : Chamberland, Martin
Cc : Jonathan Moules; geoserver-users@anonymised.comforge.net
Objet : Re: [Geoserver-users] date BUG 2.4 Geoserver
I believe the problem that Martin is having is that all the dates are the epoch (1969-12-31), in other words, the app is not reading the system time, or the system time (use ‘date’ on a Unix system) is seriously messed up. The problem is probably going to me in whatever code is accessing system time (new Date() for example. Did geoserver change anything about accessing system time in the 2.4 release?
On Wed, Oct 23, 2013 at 5:40 AM, Chamberland, Martin <Martin.Chamberland@anonymised.com> wrote:
It’s pretty hard for me to explain correctly because english in not my first language. Let’s try my best.
We where running geoserver 2.2.3 for a long time and everything was running fine. The only problem (that is not one) we had was that in the output date, there was a “Z” after all date.
So we were sure that is was a bug, so we decide to update to geoserver 2.4 (latest one) to fix the issue. Meantine (continuing searching) we discover that it’s not a bug but just normal that the “Z” appear there. But as we where now running 2.4, now all date that we output from our Oracle database are “1969-12-31”, every date are the same.
I hope i was enough clear, sorry again for poor English explanation.
Martin C.
De : Jonathan Moules [mailto:jonathanmoules@anonymised.com]
Envoyé : 22 octobre 2013 09:50
À : Chamberland, Martin
Cc : geoserver-users@lists.sourceforge.net
Objet : Re: [Geoserver-users] date BUG 2.4 Geoserver
Hi Martin,
I’m not sure what you’re asking here - without further information I suspect you won’t get any help as it’s not clear what you want.
Jonathan
On 22 October 2013 14:32, Chamberland, Martin <Martin.Chamberland@anonymised.com2…> wrote:
Did you have time to take a look at our problem ?
Thank’s!
Martin C.
De : Jonathan Moules [mailto:jonathanmoules@anonymised.com]
Envoyé : 21 octobre 2013 08:40
À : Chamberland, Martin
Cc : geoserver-users@lists.sourceforge.net
Objet : Re: [Geoserver-users] date BUG 2.4 Geoserver
Hi Martin,
That’s the ISO standard for date formatting. https://en.wikipedia.org/wiki/ISO_8601
Could you be clearer what the problem is for you?
Jonathan
On 17 October 2013 19:38, Chamberland, Martin <Martin.Chamberland@anonymised.com> wrote:
Hi there,
We just install the new version Geoserver 2.4 and from now we seem to receive some strange date format in our request.
All date output create by our trigger look like this: 1969-12-31.
Is there maybe a bug in the 2.4 version ?
Martin C.
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@anonymised.comt
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Hi there,
Anyone find a fix or why we receive date “1969-12-31” when we access Oracle database from Geoserver 2.4.1 ?
Is my explanation not enough clear ?
PS: maybe someone in French can help me translate my real problem, any French people ?? J
De : Garey Mills [mailto:gmills@anonymised.com]
Envoyé : 23 octobre 2013 11:21
À : Chamberland, Martin
Cc : Jonathan Moules; geoserver-users@anonymised.comforge.net
Objet : Re: [Geoserver-users] date BUG 2.4 Geoserver
I believe the problem that Martin is having is that all the dates are the epoch (1969-12-31), in other words, the app is not reading the system time, or the system time (use ‘date’ on a Unix system) is seriously messed up. The problem is probably going to me in whatever code is accessing system time (new Date() for example. Did geoserver change anything about accessing system time in the 2.4 release?
On Wed, Oct 23, 2013 at 5:40 AM, Chamberland, Martin <Martin.Chamberland@anonymised.com> wrote:
It’s pretty hard for me to explain correctly because english in not my first language. Let’s try my best.
We where running geoserver 2.2.3 for a long time and everything was running fine. The only problem (that is not one) we had was that in the output date, there was a “Z” after all date.
So we were sure that is was a bug, so we decide to update to geoserver 2.4 (latest one) to fix the issue. Meantine (continuing searching) we discover that it’s not a bug but just normal that the “Z” appear there. But as we where now running 2.4, now all date that we output from our Oracle database are “1969-12-31”, every date are the same.
I hope i was enough clear, sorry again for poor English explanation.
Martin C.
De : Jonathan Moules [mailto:jonathanmoules@anonymised.com]
Envoyé : 22 octobre 2013 09:50
À : Chamberland, Martin
Cc : geoserver-users@lists.sourceforge.net
Objet : Re: [Geoserver-users] date BUG 2.4 Geoserver
Hi Martin,
I’m not sure what you’re asking here - without further information I suspect you won’t get any help as it’s not clear what you want.
Jonathan
On 22 October 2013 14:32, Chamberland, Martin <Martin.Chamberland@anonymised.com2…> wrote:
Did you have time to take a look at our problem ?
Thank’s!
Martin C.
De : Jonathan Moules [mailto:jonathanmoules@anonymised.com]
Envoyé : 21 octobre 2013 08:40
À : Chamberland, Martin
Cc : geoserver-users@lists.sourceforge.net
Objet : Re: [Geoserver-users] date BUG 2.4 Geoserver
Hi Martin,
That’s the ISO standard for date formatting. https://en.wikipedia.org/wiki/ISO_8601
Could you be clearer what the problem is for you?
Jonathan
On 17 October 2013 19:38, Chamberland, Martin <Martin.Chamberland@anonymised.com> wrote:
Hi there,
We just install the new version Geoserver 2.4 and from now we seem to receive some strange date format in our request.
All date output create by our trigger look like this: 1969-12-31.
Is there maybe a bug in the 2.4 version ?
Martin C.
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@anonymised.comt
https://lists.sourceforge.net/lists/listinfo/geoserver-users
On Mon, Oct 28, 2013 at 8:44 PM, Chamberland, Martin <
Martin.Chamberland@anonymised.com> wrote:
Hi there, ****
** **
Anyone find a fix or why we receive date “1969-12-31” when we access
Oracle database from Geoserver 2.4.1 ?****Is my explanation not enough clear ?
The explanation is clear, it's just very hard to find an open source
developer having both enough spare time, and willing to use it on
an Oracle issue (Oracle being commercial software).
My suggestion, make a (possibly small) dump of your dataset, create a
ticket on jira.codehaus.org with a description, attach the
dump there, and wait (and/or look into commercial software support).
Cheers
Andrea
--
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------