[Geoserver-users] GeoServer Version not supporting Chrome?

2017-12-05 Thread uymichelle 
Hi All,

My current GeoServer version 2.4.4 is able to show the maps (polygons) on
all types of browser (IE, Chrome and Firefox). However, when I tried to
upgrade to 2.11.0 and above version (haven't try the 2.5.0 - 2.10.5), the
map (or polygons) can only show up on IE but not chrome and Firefox. Does
anyone of you know if it's about configuration problem? or other issues? how
to solve it?

Thank you very much. 

Michelle



--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Unlimited strength cryptography in Oracle JDK 8u151 and later

2017-12-05 Thread Kristian Thy 
Installing the jars still works for 32-bit Oracle JRE 8u151 on Windows.

Cheers,
Kristian

On Wed, Dec 06, Ben Caradoc-Davies wrote:
> Anyone using Oracle JDK 8u151 or later who installed the unlimited strength
> policy jars, please report back on whether this method still works.
> 
> Kind regards,
> Ben.
> 
> On 06/12/17 10:18, Ben Caradoc-Davies wrote:
> >Oracle JDK 8u151 introduces a new mechanism to enable unlimited strength
> >cryptography. For each new JDK installation, in
> >jre/lib/security/java.security uncomment the line:
> >
> >#crypto.policy=unlimited
> >
> >to read:
> >
> >crypto.policy=unlimited
> >
> >The old mechanism (installing policy jars) *should* still work:
> >http://docs.geoserver.org/latest/en/user/production/java.html#oracle-java
> >
> >OpenJDK has unlimited strength cryptography by default and is not affected
> >by this change.
> >
> >See:
> >http://www.oracle.com/technetwork/java/javase/8u151-relnotes-3850493.html
> >
> >"New Features
> >
> >security-libs/javax.crypto
> >New Security property to control crypto policy
> >
> >This release introduces a new feature whereby the JCE jurisdiction policy
> >files used by the JDK can be controlled via a new Security property. In
> >older releases, JCE jurisdiction files had to be downloaded and installed
> >separately to allow unlimited cryptography to be used by the JDK. The
> >download and install steps are no longer necessary. To enable unlimited
> >cryptography, one can use the new crypto.policy Security property. If the
> >new Security property (crypto.policy) is set in the java.security file, or
> >has been set dynamically by using the Security.setProperty() call before
> >the JCE framework has been initialized, that setting will be honored. By
> >default, the property will be undefined. If the property is undefined and
> >the legacy JCE jurisdiction files don't exist in the legacy lib/security
> >directory, then the default cryptographic level will remain at 'limited'.
> >To configure the JDK to use unlimited cryptography, set the crypto.policy
> >to a value of 'unlimited'. See the notes in the java.security file
> >shipping with this release for more information."
> >
> >Kind regards,
> >
> 
> -- 
> Ben Caradoc-Davies 
> Director
> Transient Software Limited 
> New Zealand

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Unlimited strength cryptography in Oracle JDK 8u151 and later

2017-12-05 Thread Ben Caradoc-Davies 
Anyone using Oracle JDK 8u151 or later who installed the unlimited 
strength policy jars, please report back on whether this method still works.


Kind regards,
Ben.

On 06/12/17 10:18, Ben Caradoc-Davies wrote:
Oracle JDK 8u151 introduces a new mechanism to enable unlimited strength 
cryptography. For each new JDK installation, in 
jre/lib/security/java.security uncomment the line:


#crypto.policy=unlimited

to read:

crypto.policy=unlimited

The old mechanism (installing policy jars) *should* still work:
http://docs.geoserver.org/latest/en/user/production/java.html#oracle-java

OpenJDK has unlimited strength cryptography by default and is not 
affected by this change.


See:
http://www.oracle.com/technetwork/java/javase/8u151-relnotes-3850493.html

"New Features

security-libs/javax.crypto
New Security property to control crypto policy

This release introduces a new feature whereby the JCE jurisdiction 
policy files used by the JDK can be controlled via a new Security 
property. In older releases, JCE jurisdiction files had to be downloaded 
and installed separately to allow unlimited cryptography to be used by 
the JDK. The download and install steps are no longer necessary. To 
enable unlimited cryptography, one can use the new crypto.policy 
Security property. If the new Security property (crypto.policy) is set 
in the java.security file, or has been set dynamically by using the 
Security.setProperty() call before the JCE framework has been 
initialized, that setting will be honored. By default, the property will 
be undefined. If the property is undefined and the legacy JCE 
jurisdiction files don't exist in the legacy lib/security directory, 
then the default cryptographic level will remain at 'limited'. To 
configure the JDK to use unlimited cryptography, set the crypto.policy 
to a value of 'unlimited'. See the notes in the java.security file 
shipping with this release for more information."


Kind regards,



--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] FAIL - Application at context path [/geoserver] could not be started - Geoserver v2.12.0 - Java v1.8.151

2017-12-05 Thread Abdool, Sameer 
Ben,

I did copy the JCE jar files as previously done but to no avail. I also 
performed an install of  Ju151 as well as Ju144 side by side and assess 
behaviour so that failed as well. Hence I diverted away from thinking the Java 
Policy files were at fault.

Downgraded tomcat version to 8.5 and no success still, thinking that maybe 
tomcat 9.0.1 was not stable enough combined with Ju151 as it's relying on the 
jvm.dll

I even gone as far as checking the windows registry settings for Java.

I really tried different approach but did not read the Ju151 release notes 
about the new security feature nor understood the log entries properly.

I'll let you know how it goes tomorrow.

Regards,
Sameer

Get Outlook for Android



From: Ben Caradoc-Davies
Sent: Tuesday, 5 December, 21:03
Subject: Re: [Geoserver-users] FAIL - Application at context path [/geoserver] 
could not be started - Geoserver v2.12.0 - Java v1.8.151
To: Abdool, Sameer
Cc: 'geoserver-users@lists.sourceforge.net'


Sameer, the crypto policy change in Oracle JDK 8u151 is new (seven weeks old) 
and yes, you are right, not yet documented in the GeoServer manual. The new 
behaviour is supposed to be backwards compatible, so I suspect that your new 
JDK does not have the policy files installed (breaking your configuration 
because encrypted resources cannot be unencrypted). Did you install the policy 
files in your Oracle JDK 8u151? 
http://docs.geoserver.org/latest/en/user/production/java.html The change will 
not affect OpenJDK, which does not have crypto restrictions. I will file a Jira 
issue to update the docs. I look forward to your confirmation that you are able 
to start GeoServer after changing your crypto.policy setting to unlimited (by 
uncommenting this line in java.security) or by installing the policy files. 
Kind regards, Ben. On 06/12/17 09:26, Abdool, Sameer wrote: > Hi Ben, > > Thank 
you very much for the detailed explanation. I was too focused on JCE 
jurisdiction files replacement at first then diverted onto something else away 
from the real problem. > > Can't wait to try the fix tomorrow and will of 
course keep you posted. > > By the way I could not find anything about what you 
mentioned in the Geoserver documentation apart from Java 1.9 incompatibility. 
Unless I've missed something. Maybe worth noting for future reference. > > Kind 
Regards, > Sameer > > Get Outlook for Android > > > > From: Ben Caradoc-Davies 
> Sent: Tuesday, 5 December, 20:16 > Subject: Re: [Geoserver-users] FAIL - 
Application at context path [/geoserver] could not be started - Geoserver 
v2.12.0 - Java v1.8.151 > To: Abdool, Sameer, 
'geoserver-users@lists.sourceforge.net' > > > Sameer, it is not a bug: it is a 
"feature" (of Oracle JDK 8u151): 
http://www.oracle.com/technetwork/java/javase/8u151-relnotes-3850493.html "New 
Features security-libs/javax.crypto New Security property to control crypto 
policy This release introduces a new feature whereby the JCE jurisdiction 
policy files used by the JDK can be controlled via a new Security property. In 
older releases, JCE jurisdiction files had to be downloaded and installed 
separately to allow unlimited cryptography to be used by the JDK. The download 
and install steps are no longer necessary. To enable unlimited cryptography, 
one can use the new crypto.policy Security property. If the new Security 
property (crypto.policy) is set in the java.security file, or has been set 
dynamically by using the Security.setProperty() call before the JCE framework 
has been initialized, that setting will be honored. By default, the property 
will be undefined. If the property is undefined and the legacy JCE jurisdiction 
files don't exist in the legacy lib/security directory, then the default 
cryptographic level will remain at 'limited'. To configure the JDK to use 
unlimited cryptography, set the crypto.policy to a value of 'unlimited'. See 
the notes in the java.security file shipping with this release for more 
information." The evidence that this is your problem can be found in 
geoserver.log. This is only a WARN so not immediately fatal (GeoServer 
continues when a data store cannot be loaded). There are several of these: 
2017-12-04 10:14:57,078 WARN [org.geoserver] - Failed to load data store 'OS 
MasterMap' com.thoughtworks.xstream.converters.ConversionException:  
Debugging information  cause-exception : 
org.jasypt.exceptions.EncryptionOperationNotPossibleException cause-message : 
Encryption raised an exception. A possible cause is you are using strong 
encryption algorithms and you have not installed the Java Cryptography 
Extension (JCE) Unlimit ed Strength Jurisdiction Policy Files in this Java 
Virtual Machine class : org.geoserver.catalog.impl.DataStoreInfoImpl 
required-type : org.geoserver.catalog.impl.DataStoreInfoImpl converter-type : 
org.geoserver.config.util.XStreamPersister$StoreInfoConverter line number : 39 
version : 2.12.0

Re: [Geoserver-users] FAIL - Application at context path [/geoserver] could not be started - Geoserver v2.12.0 - Java v1.8.151

2017-12-05 Thread Ben Caradoc-Davies 
Thank you, Sameer. It is possible that backwards-compatibility (support 
for policy jars) does not work as documented by Oracle for 8u151 or 
later. This will be a very important finding for many GeoServer users.


Kind regards,
Ben.

On 06/12/17 10:18, Abdool, Sameer wrote:

Ben,

I did copy the JCE jar files as previously done but to no avail. I also 
performed an install of  Ju151 as well as Ju144 side by side and assess 
behaviour so that failed as well. Hence I diverted away from thinking the Java 
Policy files were at fault.

Downgraded tomcat version to 8.5 and no success still, thinking that maybe 
tomcat 9.0.1 was not stable enough combined with Ju151 as it's relying on the 
jvm.dll

I even gone as far as checking the windows registry settings for Java.

I really tried different approach but did not read the Ju151 release notes 
about the new security feature nor understood the log entries properly.

I'll let you know how it goes tomorrow.

Regards,
Sameer


--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] FAIL - Application at context path [/geoserver] could not be started - Geoserver v2.12.0 - Java v1.8.151

2017-12-05 Thread Ben Caradoc-Davies 

Sameer,

I do not think that should make any difference.

Kind regards,
Ben.

On 06/12/17 10:22, Abdool, Sameer wrote:

Ben,

I forgot to mention that I'm using JRE rather than the JDK.
I guess that won't make any difference or will it?

Cheers,
Sameer


--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] FAIL - Application at context path [/geoserver] could not be started - Geoserver v2.12.0 - Java v1.8.151

2017-12-05 Thread Abdool, Sameer 
Ben,

I forgot to mention that I'm using JRE rather than the JDK.
I guess that won't make any difference or will it?

Cheers,
Sameer

Get Outlook for Android


From: Ben Caradoc-Davies 
Sent: Tuesday, December 5, 2017 9:02:29 PM
To: Abdool, Sameer
Cc: 'geoserver-users@lists.sourceforge.net'
Subject: Re: [Geoserver-users] FAIL - Application at context path [/geoserver] 
could not be started - Geoserver v2.12.0 - Java v1.8.151

Sameer,

the crypto policy change in Oracle JDK 8u151 is new (seven weeks old)
and yes, you are right, not yet documented in the GeoServer manual. The
new behaviour is supposed to be backwards compatible, so I suspect that
your new JDK does not have the policy files installed (breaking your
configuration because encrypted resources cannot be unencrypted). Did
you install the policy files in your Oracle JDK 8u151?
http://docs.geoserver.org/latest/en/user/production/java.html

The change will not affect OpenJDK, which does not have crypto restrictions.

I will file a Jira issue to update the docs. I look forward to your
confirmation that you are able to start GeoServer after changing your
crypto.policy setting to unlimited (by uncommenting this line in
java.security) or by installing the policy files.

Kind regards,
Ben.

On 06/12/17 09:26, Abdool, Sameer wrote:
> Hi Ben,
>
> Thank you very much for the detailed explanation. I was too focused on JCE 
> jurisdiction  files replacement at first then diverted onto something else 
> away from the real  problem.
>
> Can't wait to try the fix tomorrow and will of course keep you posted.
>
> By the way I could not find anything about what you mentioned in the 
> Geoserver documentation apart from Java 1.9 incompatibility. Unless I've 
> missed something. Maybe worth noting for future reference.
>
> Kind Regards,
> Sameer
>
> Get Outlook for Android
>
>
>
> From: Ben Caradoc-Davies
> Sent: Tuesday, 5 December, 20:16
> Subject: Re: [Geoserver-users] FAIL - Application at context path 
> [/geoserver] could not be started - Geoserver v2.12.0 - Java v1.8.151
> To: Abdool, Sameer, 'geoserver-users@lists.sourceforge.net'
>
>
> Sameer, it is not a bug: it is a "feature" (of Oracle JDK 8u151): 
> http://www.oracle.com/technetwork/java/javase/8u151-relnotes-3850493.html 
> "New Features security-libs/javax.crypto New Security property to control 
> crypto policy This release introduces a new feature whereby the JCE 
> jurisdiction policy files used by the JDK can be controlled via a new 
> Security property. In older releases, JCE jurisdiction files had to be 
> downloaded and installed separately to allow unlimited cryptography to be 
> used by the JDK. The download and install steps are no longer necessary. To 
> enable unlimited cryptography, one can use the new crypto.policy Security 
> property. If the new Security property (crypto.policy) is set in the 
> java.security file, or has been set dynamically by using the 
> Security.setProperty() call before the JCE framework has been initialized, 
> that setting will be honored. By default, the property will be undefined. If 
> the property is undefined and the legacy JCE jurisdiction files don't exist 
> in the legacy lib/security directory, then the default cryptographic level 
> will remain at 'limited'. To configure the JDK to use unlimited cryptography, 
> set the crypto.policy to a value of 'unlimited'. See the notes in the 
> java.security file shipping with this release for more information." The 
> evidence that this is your problem can be found in geoserver.log. This is 
> only a WARN so not immediately fatal (GeoServer continues when a data store 
> cannot be loaded). There are several of these: 2017-12-04 10:14:57,078 WARN 
> [org.geoserver] - Failed to load data store 'OS MasterMap' 
> com.thoughtworks.xstream.converters.ConversionException:  Debugging 
> information  cause-exception : 
> org.jasypt.exceptions.EncryptionOperationNotPossibleException cause-message : 
> Encryption raised an exception. A possible cause is you are using strong 
> encryption algorithms and you have not installed the Java Cryptography 
> Extension (JCE) Unlimit ed Strength Jurisdiction Policy Files in this Java 
> Virtual Machine class : org.geoserver.catalog.impl.DataStoreInfoImpl 
> required-type : org.geoserver.catalog.impl.DataStoreInfoImpl converter-type : 
> org.geoserver.config.util.XStreamPersister$StoreInfoConverter line number : 
> 39 version : 2.12.0 --- The ERROR that results in 
> the failure to initialise the geoserver context is caused by the embedded 
> GeoWebCache failing to locate a missing layer (presumably caused by a failure 
> to load a data store supplying the layer): 2017-12-04 10:14:59,733 ERROR 
> [context.ContextLoader] - Context initialization failed 
> org.springframework.beans.factory.BeanCreationException: Error creating bean 
> with name 'gwcFacade'

[Geoserver-users] Unlimited strength cryptography in Oracle JDK 8u151 and later

2017-12-05 Thread Ben Caradoc-Davies 
Oracle JDK 8u151 introduces a new mechanism to enable unlimited strength 
cryptography. For each new JDK installation, in 
jre/lib/security/java.security uncomment the line:


#crypto.policy=unlimited

to read:

crypto.policy=unlimited

The old mechanism (installing policy jars) *should* still work:
http://docs.geoserver.org/latest/en/user/production/java.html#oracle-java

OpenJDK has unlimited strength cryptography by default and is not 
affected by this change.


See:
http://www.oracle.com/technetwork/java/javase/8u151-relnotes-3850493.html

"New Features

security-libs/javax.crypto
New Security property to control crypto policy

This release introduces a new feature whereby the JCE jurisdiction 
policy files used by the JDK can be controlled via a new Security 
property. In older releases, JCE jurisdiction files had to be downloaded 
and installed separately to allow unlimited cryptography to be used by 
the JDK. The download and install steps are no longer necessary. To 
enable unlimited cryptography, one can use the new crypto.policy 
Security property. If the new Security property (crypto.policy) is set 
in the java.security file, or has been set dynamically by using the 
Security.setProperty() call before the JCE framework has been 
initialized, that setting will be honored. By default, the property will 
be undefined. If the property is undefined and the legacy JCE 
jurisdiction files don't exist in the legacy lib/security directory, 
then the default cryptographic level will remain at 'limited'. To 
configure the JDK to use unlimited cryptography, set the crypto.policy 
to a value of 'unlimited'. See the notes in the java.security file 
shipping with this release for more information."


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] FAIL - Application at context path [/geoserver] could not be started - Geoserver v2.12.0 - Java v1.8.151

2017-12-05 Thread Ben Caradoc-Davies 

Sameer,

the crypto policy change in Oracle JDK 8u151 is new (seven weeks old) 
and yes, you are right, not yet documented in the GeoServer manual. The 
new behaviour is supposed to be backwards compatible, so I suspect that 
your new JDK does not have the policy files installed (breaking your 
configuration because encrypted resources cannot be unencrypted). Did 
you install the policy files in your Oracle JDK 8u151?

http://docs.geoserver.org/latest/en/user/production/java.html

The change will not affect OpenJDK, which does not have crypto restrictions.

I will file a Jira issue to update the docs. I look forward to your 
confirmation that you are able to start GeoServer after changing your 
crypto.policy setting to unlimited (by uncommenting this line in 
java.security) or by installing the policy files.


Kind regards,
Ben.

On 06/12/17 09:26, Abdool, Sameer wrote:

Hi Ben,

Thank you very much for the detailed explanation. I was too focused on JCE 
jurisdiction  files replacement at first then diverted onto something else away 
from the real  problem.

Can't wait to try the fix tomorrow and will of course keep you posted.

By the way I could not find anything about what you mentioned in the Geoserver 
documentation apart from Java 1.9 incompatibility. Unless I've missed 
something. Maybe worth noting for future reference.

Kind Regards,
Sameer

Get Outlook for Android



From: Ben Caradoc-Davies
Sent: Tuesday, 5 December, 20:16
Subject: Re: [Geoserver-users] FAIL - Application at context path [/geoserver] 
could not be started - Geoserver v2.12.0 - Java v1.8.151
To: Abdool, Sameer, 'geoserver-users@lists.sourceforge.net'


Sameer, it is not a bug: it is a "feature" (of Oracle JDK 8u151): http://www.oracle.com/technetwork/java/javase/8u151-relnotes-3850493.html "New Features security-libs/javax.crypto New Security property to control crypto policy This release introduces a new feature whereby the JCE jurisdiction policy files used by the JDK can be controlled via a new Security property. In older releases, JCE jurisdiction files had to be downloaded and installed separately to allow unlimited cryptography to be used by the JDK. The download and install steps are no 
longer necessary. To enable unlimited cryptography, one can use the new crypto.policy Security property. If the new Security property (crypto.policy) is set in the java.security file, or has been set dynamically by using the Security.setProperty() call before the JCE framework has been initialized, that setting will be honored. By default, the property will be undefined. If the property is undefined and the legacy JCE jurisdiction files don't exist in the legacy lib/security directory, then the default cryptographic level will remain at 'limited'. To configure the 
JDK to use unlimited cryptography, set the crypto.policy to a value of 'unlimited'. See the notes in the java.security file shipping with this release for more information." The evidence that this is your problem can be found in geoserver.log. This is only a WARN so not immediately fatal (GeoServer continues when a data store cannot be loaded). There are several of these: 2017-12-04 10:14:57,078 WARN [org.geoserver] - Failed to load data store 'OS MasterMap' com.thoughtworks.xstream.converters.ConversionException:  Debugging information  
cause-exception : org.jasypt.exceptions.EncryptionOperationNotPossibleException cause-message : Encryption raised an exception. A possible cause is you are using strong encryption algorithms and you have not installed the Java Cryptography Extension (JCE) Unlimit ed Strength Jurisdiction Policy Files in this Java Virtual Machine class : org.geoserver.catalog.impl.DataStoreInfoImpl required-type : org.geoserver.catalog.impl.DataStoreInfoImpl converter-type : org.geoserver.config.util.XStreamPersister$StoreInfoConverter line number : 39 version : 2.12.0 
--- The ERROR that results in the failure to initialise the geoserver context is caused by the embedded GeoWebCache failing to locate a missing layer (presumably caused by a failure to load a data store supplying the layer): 2017-12-04 10:14:59,733 ERROR [context.ContextLoader] - Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'gwcFacade' defined in URL [jar:file:/C:/Program%20Files%20(x86)/Apache%20Software%20Foundation/Tomcat 
%209.0/webapps/geoserver/WEB-INF/lib/gs-gwc-2.12.0.jar!/applicationContext.xml]: Cannot resolve reference to bean 'DiskQuotaMonitor' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'DiskQuotaMonitor' defined in URL [jar:file:/C:/Program%20Files%20(x86)/Apache%20Software%20Foundation /Tomcat%209.0/webapps/geoserver/WEB-INF/lib/gs-gwc-2.12.0.jar!/geowebcache-diskquota-context.xml]: Invocation of init method failed; nested exception is

Re: [Geoserver-users] FAIL - Application at context path [/geoserver] could not be started - Geoserver v2.12.0 - Java v1.8.151

2017-12-05 Thread Abdool, Sameer 
Hi Ben,

Thank you very much for the detailed explanation. I was too focused on JCE 
jurisdiction  files replacement at first then diverted onto something else away 
from the real  problem.

Can't wait to try the fix tomorrow and will of course keep you posted.

By the way I could not find anything about what you mentioned in the Geoserver 
documentation apart from Java 1.9 incompatibility. Unless I've missed 
something. Maybe worth noting for future reference.

Kind Regards,
Sameer

Get Outlook for Android



From: Ben Caradoc-Davies
Sent: Tuesday, 5 December, 20:16
Subject: Re: [Geoserver-users] FAIL - Application at context path [/geoserver] 
could not be started - Geoserver v2.12.0 - Java v1.8.151
To: Abdool, Sameer, 'geoserver-users@lists.sourceforge.net'


Sameer, it is not a bug: it is a "feature" (of Oracle JDK 8u151): 
http://www.oracle.com/technetwork/java/javase/8u151-relnotes-3850493.html "New 
Features security-libs/javax.crypto New Security property to control crypto 
policy This release introduces a new feature whereby the JCE jurisdiction 
policy files used by the JDK can be controlled via a new Security property. In 
older releases, JCE jurisdiction files had to be downloaded and installed 
separately to allow unlimited cryptography to be used by the JDK. The download 
and install steps are no longer necessary. To enable unlimited cryptography, 
one can use the new crypto.policy Security property. If the new Security 
property (crypto.policy) is set in the java.security file, or has been set 
dynamically by using the Security.setProperty() call before the JCE framework 
has been initialized, that setting will be honored. By default, the property 
will be undefined. If the property is undefined and the legacy JCE jurisdiction 
files don't exist in the legacy lib/security directory, then the default 
cryptographic level will remain at 'limited'. To configure the JDK to use 
unlimited cryptography, set the crypto.policy to a value of 'unlimited'. See 
the notes in the java.security file shipping with this release for more 
information." The evidence that this is your problem can be found in 
geoserver.log. This is only a WARN so not immediately fatal (GeoServer 
continues when a data store cannot be loaded). There are several of these: 
2017-12-04 10:14:57,078 WARN [org.geoserver] - Failed to load data store 'OS 
MasterMap' com.thoughtworks.xstream.converters.ConversionException:  
Debugging information  cause-exception : 
org.jasypt.exceptions.EncryptionOperationNotPossibleException cause-message : 
Encryption raised an exception. A possible cause is you are using strong 
encryption algorithms and you have not installed the Java Cryptography 
Extension (JCE) Unlimit ed Strength Jurisdiction Policy Files in this Java 
Virtual Machine class : org.geoserver.catalog.impl.DataStoreInfoImpl 
required-type : org.geoserver.catalog.impl.DataStoreInfoImpl converter-type : 
org.geoserver.config.util.XStreamPersister$StoreInfoConverter line number : 39 
version : 2.12.0 --- The ERROR that results in the 
failure to initialise the geoserver context is caused by the embedded 
GeoWebCache failing to locate a missing layer (presumably caused by a failure 
to load a data store supplying the layer): 2017-12-04 10:14:59,733 ERROR 
[context.ContextLoader] - Context initialization failed 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'gwcFacade' defined in URL 
[jar:file:/C:/Program%20Files%20(x86)/Apache%20Software%20Foundation/Tomcat 
%209.0/webapps/geoserver/WEB-INF/lib/gs-gwc-2.12.0.jar!/applicationContext.xml]:
 Cannot resolve reference to bean 'DiskQuotaMonitor' while setting constructor 
argument; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'DiskQuotaMonitor' defined in URL 
[jar:file:/C:/Program%20Files%20(x86)/Apache%20Software%20Foundation 
/Tomcat%209.0/webapps/geoserver/WEB-INF/lib/gs-gwc-2.12.0.jar!/geowebcache-diskquota-context.xml]:
 Invocation of init method failed; nested exception is 
java.lang.IllegalStateException: Cou ld not locate a layer or layer group with 
id LayerGroupInfoImpl--3f96846b:15ebdb05dc8:-7fd2 within GeoServer 
configuration, the GWC configuration seems to be out of synch The likely 
solution is to follow the instructions in the Oracle JDK 8u151 release notes to 
configure the JDK to use unlimited cryptography. Kind regards, Ben. On 06/12/17 
03:11, Abdool, Sameer wrote: > -Original Message- > From: Abdool, 
Sameer > Sent: 05 December 2017 09:34 > To: 'Ben Caradoc-Davies' > Subject: RE: 
[Geoserver-users] FAIL - Application at context path [/geoserver] could not be 
started - Geoserver v2.12.0 - Java v1.8.151 > > Ben, > > Thank you for getting 
back to me. > Please find log files attached. > > Regards, > Sameer > > 
-Original Message- > From: Ben Caradoc-Davies 
[mailto:b...@transient.nz] > Sent:

Re: [Geoserver-users] FAIL - Application at context path [/geoserver] could not be started - Geoserver v2.12.0 - Java v1.8.151

2017-12-05 Thread Ben Caradoc-Davies 

Sameer,

it is not a bug: it is a "feature" (of Oracle JDK 8u151):
http://www.oracle.com/technetwork/java/javase/8u151-relnotes-3850493.html

"New Features

security-libs/javax.crypto
 New Security property to control crypto policy

This release introduces a new feature whereby the JCE jurisdiction 
policy files used by the JDK can be controlled via a new Security 
property. In older releases, JCE jurisdiction files had to be downloaded 
and installed separately to allow unlimited cryptography to be used by 
the JDK. The download and install steps are no longer necessary. To 
enable unlimited cryptography, one can use the new crypto.policy 
Security property. If the new Security property (crypto.policy) is set 
in the java.security file, or has been set dynamically by using the 
Security.setProperty() call before the JCE framework has been 
initialized, that setting will be honored. By default, the property will 
be undefined. If the property is undefined and the legacy JCE 
jurisdiction files don't exist in the legacy lib/security directory, 
then the default cryptographic level will remain at 'limited'. To 
configure the JDK to use unlimited cryptography, set the crypto.policy 
to a value of 'unlimited'. See the notes in the java.security file 
shipping with this release for more information."



The evidence that this is your problem can be found in geoserver.log. 
This is only a WARN so not immediately fatal (GeoServer continues when a 
data store cannot be loaded). There are several of these:



2017-12-04 10:14:57,078 WARN [org.geoserver] - Failed to load data store 
'OS MasterMap'

com.thoughtworks.xstream.converters.ConversionException:
 Debugging information 
cause-exception : 
org.jasypt.exceptions.EncryptionOperationNotPossibleException
cause-message   : Encryption raised an exception. A possible cause 
is you are using strong encryption algorithms and you have not installed 
the Java Cryptography Extension (JCE) Unlimit

ed Strength Jurisdiction Policy Files in this Java Virtual Machine
class   : org.geoserver.catalog.impl.DataStoreInfoImpl
required-type   : org.geoserver.catalog.impl.DataStoreInfoImpl
converter-type  : 
org.geoserver.config.util.XStreamPersister$StoreInfoConverter

line number : 39
version : 2.12.0
---


The ERROR that results in the failure to initialise the geoserver 
context is caused by the embedded GeoWebCache failing to locate a 
missing layer (presumably caused by a failure to load a data store 
supplying the layer):



2017-12-04 10:14:59,733 ERROR [context.ContextLoader] - Context 
initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating 
bean with name 'gwcFacade' defined in URL 
[jar:file:/C:/Program%20Files%20(x86)/Apache%20Software%20Foundation/Tomcat
%209.0/webapps/geoserver/WEB-INF/lib/gs-gwc-2.12.0.jar!/applicationContext.xml]: 
Cannot resolve reference to bean 'DiskQuotaMonitor' while setting 
constructor argument; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating 
bean with name 'DiskQuotaMonitor' defined in URL 
[jar:file:/C:/Program%20Files%20(x86)/Apache%20Software%20Foundation
/Tomcat%209.0/webapps/geoserver/WEB-INF/lib/gs-gwc-2.12.0.jar!/geowebcache-diskquota-context.xml]: 
Invocation of init method failed; nested exception is 
java.lang.IllegalStateException: Cou
ld not locate a layer or layer group with id 
LayerGroupInfoImpl--3f96846b:15ebdb05dc8:-7fd2 within GeoServer 
configuration, the GWC configuration seems to be out of synch



The likely solution is to follow the instructions in the Oracle JDK 
8u151 release notes to configure the JDK to use unlimited cryptography.


Kind regards,
Ben.

On 06/12/17 03:11, Abdool, Sameer wrote:

-Original Message-
From: Abdool, Sameer
Sent: 05 December 2017 09:34
To: 'Ben Caradoc-Davies'
Subject: RE: [Geoserver-users] FAIL - Application at context path [/geoserver] 
could not be started - Geoserver v2.12.0 - Java v1.8.151

Ben,

Thank you for getting back to me.
Please find log files attached.

Regards,
Sameer

-Original Message-
From: Ben Caradoc-Davies [mailto:b...@transient.nz]
Sent: 04 December 2017 19:18
To: Abdool, Sameer ; 
'geoserver-users@lists.sourceforge.net' 
Subject: Re: [Geoserver-users] FAIL - Application at context path [/geoserver] 
could not be started - Geoserver v2.12.0 - Java v1.8.151

Sameer,

as you indicate below, the log files, especially full stack traces, are 
essential to investigate this problem.

Kind regards,
Ben.

On 04/12/17 23:49, Abdool, Sameer wrote:

Good Morning,

I'm currently using Geoserver v2.12.0 combined with Java v1.8.141.
Geoserver is running as a windows service though Apache Tomcat v9.0.1

I haven't had any issues so far until Java gets updated to a minor
higher that X.X.141 I then get the error message as displayed