[Geoserver-users] Gridsets disappearing?

2014-09-08 Thread Nick Ves
Hi all,

I just started to getting accustomed with geoserver I just encountered
this behavior:

I am creating some gridsets for some test locations but after a server
restart the gridset definitions are just missing or deleted?! Very
baffling because everything seems to be running normaly up to that
point


I am just wondering if someone has encountered the same behaviour and
if so can he share the knowledge on what might be the problem?

Nikos

--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users


[Geoserver-users] How Interrupt Geoserver from proccessing previous requests of a user?

2014-09-08 Thread Ali Madad
Hello to all dears

We have a problem on presenting WMS services as below:

 When a user repeatedly requests different zooms (without letting Geoserver to 
finish previous requests preparation), it seems that all requests stacked in a 
queue and Geoserver proccesses all of them one after another till the last one. 
In this order Geoserver becames too busy to response to another users requests. 

We was hopping there be a way to tune Geoserver so that it interrupts all 
proccesses for previous requests of a user, and just responses to the last 
requests of them. In other words it neglects previous requests of users and 
just proccess their last orders.

Best regards
Ali Madad




,   copied from Bayat

--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users


[Geoserver-users] Problems starting multiple instances of GeoServer concurrently

2014-09-08 Thread Jack Mitchell
Hi List,

I have created a GeoServer setup with 10 separate Tomcat processes each
running Geoserver (with HAProxy as a load balancer, running on Solaris
x86). This works great most of the time, but sometimes on startup some of
the instances are failing (see stack trace below).

>From what I am seeing, it looks like each instance is reading its config
from the shared data directory, and also each instance is reading and then
writing out 3 files (wms.xml, wfs.xml and wcs.xml). Then there is a race -
if another instance starts up, it reads only part of one of those files and
gets upset. If I add a 5 second delay between starting each instance, the
problem goes away (except on startup, which ignores my delay). Without a
delay, between 0 and 4 instances fail to initialize.

Has anyone else run into this issue? And does anyone know why (and where!)
these files are being written back out (without any changes)?

Thanks

Jack

2014-09-08 15:26:15,213 WARN [support.DisposableBeanAdapter] - Invocation
of destroy method failed on bean with name 'geoServerLoader':
org.springframework.beans.factory.BeanCreationNotAllowedException: Error
creating bean with name 'metaTileCache': Singleton bean creation not
allowed while the singletons of this factory
are in destruction (Do not request a bean from a BeanFactory in a destroy
method implementation!)
2014-09-08 15:26:15,225 ERROR [context.ContextLoader] - Context
initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'wmsServiceInterceptor-kmlReflector' defined in URL
[jar:file:/opt1/geoserver/apache-tomcat-7.0.54/instance4/webapps/geoserver/WEB-INF/lib/gs-kml-2.5.jar!/applicationContext.xml]:
Cannot resolve reference to bean 'wms' while setting constructor argument;
nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'wms' defined in URL
[jar:file:/opt1/geoserver/apache-tomcat-7.0.54/instance4/webapps/geoserver/WEB-INF/lib/gs-wms-2.5.jar!/applicationContext.xml]:
Cannot resolve reference to bean 'geoServer' while setting constructor
argument; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'geoServer' defined in URL
[jar:file:/opt1/geoserver/apache-tomcat-7.0.54/instance4/webapps/geoserver/WEB-INF/lib/gs-main-2.5.jar!/applicationContext.xml]:
Initialization of bean failed; nested exception is
java.lang.RuntimeException: java.lang.NullPointerException
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:329)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:107)
at
org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:616)
at
org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:148)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1035)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:939)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
2014-09-08 15:19:46,975 WARN [turbojpeg.TurboJPEGMapResponse] - The turbo
jpeg encoder is available for usage
2014-09-08 15:26:15,213 WARN [support.DisposableBeanAdapter] - Invocation
of destroy method failed on bean with name 'geoServerLoader':
org.springframework.beans.factory.BeanCreationNotAllowedException: Error
creating bean with name 'metaTileCache': Singleton bean creation not
allowed while the singletons of this factory
are in destruction (Do not request a bean from a BeanFactory in a destroy
method implementation!)
2014-09-08 15:26:15,225 ERROR [context.ContextLoader] - Context
initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'wmsServiceInterceptor-kmlReflector' defined in URL
[jar:file:/opt1/geoserver/apache-tomcat-7.0.54/instance4/webapps/geoserver/WEB-INF/lib/gs-kml-2.5.jar!/applicationContext.xml]:
Cannot resolve referen

[Geoserver-users] Erdas Imagine Format Image Mosaic?

2014-09-08 Thread Garey Mills
Using Geoserver 2.5.2 with GDAL extensions installed on RHEL6, I have a
directory of '.img' files which should form a mosaic. Using gdalinfo I can
see that the '*.img' files are in Erdas Imagine format. Each file is
accompanied by an '*img.xml' and an '*.rrd' file.

When, however, I try to import the directory into Geoserver, (ImageMosaic
store, when creating the store I choose the directory containing the
images, I get the following message:

Could not list layers for this store, an error occurred retrieving them:
Failed to create reader from file:data/ and hints null

This error message appears in the logs as well

ImageMosaic docs say that GDAL image formats can be used. What might be the
problem?

Garey Mills


-- 
Generate messages about directories that cannot  be
read,  files  that  cannot be opened ... rather than being silent ...
(from `man du`)
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users


Re: [Geoserver-users] [Geoserver-devel] wms getCapabilities special characters

2014-09-08 Thread Bessette-Halsema, Dominique E
Thank Jukka


This helps a lot.  I agree that if there are restrictions, this should be 
included in the documentation.



Dominique Bessette





From: Rahkonen Jukka (Tike) [mailto:jukka.rahko...@mmmtike.fi]
Sent: Thursday, September 04, 2014 6:17 AM
To: 'Jody Garnett'; Bessette-Halsema, Dominique E
Cc: 'geoserver-users'
Subject: Re: [Geoserver-users] [Geoserver-devel] wms getCapabilities special 
characters



Hi,



This may be TL;DR. However, names with special characters are an eternal 
battle. If someone verifies that what I write makes sense it might be good to 
include it in some place in Geoserver documentation.



Short version: WMS standard allows anything in layer names but WFS standard 
puts strict rules for feature type names. By default Geoserver is using same 
names in both WMS and WFS services which means sooner or later troubles if the 
more strict rules are not followed.  Wise people follow the rule: Name must 
start with either a letter or underscore (_) and may contain only letters, 
digits, underscores (_), hyphens (-), and periods (.).



Long story: I have been fighting with peculiar WMS layer names and WFS feature 
type names sometimes and my current interpretation of what is valid and what is 
not is as follows.



In WMS almost anything is allowed in layer names. I base this on WMS 1.3.0 
schema http://schemas.opengis.net/wms/1.3.0/capabilities_1_3_0.xsd

It says:









The Name is typically for machine-to-machine communication.

  







AND:







Nested list of zero or more map Layers offered by this server.

  











So a layer name in WMS is defined to be just a string. Thanks to Andreas 
Eichner 
http://osgeo-org.1560.x6.nabble.com/cascading-wms-and-layer-names-encoding-td5058504.html
 I have learned that xs:string  is a

"... finite-length sequence of characters that match the Char production

from [XML 1.0 (Second Edition)]" whereby Char is defined as:



Char   ::= #x9 | #xA | #xD | [#x20-#xD7FF] |

[#xE000-#xFFFD] | [#x1-#x10] /* any Unicode character,

excluding the surrogate blocks, FFFE, and . */



or in other words: almost every character.”



However, in WFS situation is different. WFS 1.1.0 schema 
http://schemas.opengis.net/wfs/1.1.0/wfs.xsd specifies that feature type has a 
name that is of type QName







An element of this type that describes a feature in an application

namespace shall have an xml xmlns specifier, e.g.

xmlns:bo="http://www.BlueOx.org/BlueOx";

 









QName stands for qualified name 
http://books.xmlschemata.org/relaxng/ch19-77287.html and it is xsd:NCName with 
an optional prexif. Finally we get into NCName which has quite a many 
restrictions http://www.datypic.com/sc/xsd/t-xsd_NCName.html



Therefore a WFS typeName must start with either a letter or underscore (_) and 
may contain only letters, digits, underscores (_), hyphens (-), and periods 
(.). WFS typeName which begins with a number is invalid, as well as names with 
colons in any place in the body of the name because colon is reserved for the 
namespace in the xsd:QName.



-Jukka Rahkonen-







Lähettäjä: Jody Garnett [mailto:jody.garn...@gmail.com]
Lähetetty: 3. syyskuuta 2014 23:19
Vastaanottaja: Bessette-Halsema, Dominique E
Kopio: geoserver-users
Aihe: Re: [Geoserver-users] [Geoserver-devel] wms getCapabilities special 
characters



You should ask on the user list :) The devel-list is for those working on the 
GeoServer application.



The WMS and WFS specifications dictate what is allowed as a layer name - in 
particular the WFS specification should have some limitations based on the 
structure of XML documents (which uses the format "prefix:identifier" - where 
prefix is mapped to an XML schema namespace).



Check the specifications and let us know what you find? I expect in this case 
that even if GeoServer lets you add additional characters XML parsers and WFS 
clients will not be able to handle the situation.



(Note the GeoServer web application and REST API will often allow you to 
configure setting that do not work, when you spot an example please report the 
issue).

--

Jody








Jody Garnett



On Wed, Sep 3, 2014 at 10:28 AM, Bessette-Halsema, Dominique E 
mailto:dominique.besse...@gdit.com>> wrote:

I added a colon ‘:’ character to a grid name.  Is this allowed in the WMS 
getCapabilities?  Or is this a special character?  I know this isn’t the 
recommended naming convention but it is required and I need to go back and 
accurately explain why it may or may not work.



Where in the  geoserver code is the WMS getCapabilities name set?



For example:  imagery:goes_13.infrared.1km



In the WCS getCapabilities  the identifier has the correct name





infrared-goes_13 1km





-120.0038771 -65.0093883

-44.9961229 65.0093883



imagery:goes_13.infrared.1km







In the WMS getCapabilities the Name is not correct it cuts off after the colon



-

imagery

in

[Geoserver-users] Problem in deploying GEOSERVER with TJS service-reg

2014-09-08 Thread Jeya Singh.V
Dear sir,

Iam facing problem in deploying GEOSERVER with TJS service...

i followed the steps in the file, attached to this mail...

iam to unable to download the jars files from the following link
https://github.com/thijsbrentjens/geoserver/blob/tjs_2.2.x/binaries/libs-20131219.zip

And while executing the command iam getting following error:
[INFO] Table Joining Service Model(net.opengis.tjs) ... SUCCESS [
 3.506 s]
[INFO] TJS XML Support(xsd-tjs) ... SUCCESS [
 2.049 s]
[INFO] Geomix TJS Datasource suport(tjs-data) . SUCCESS [
 1.532 s]
[INFO] GeoMIX TJS for Geoserver(tjs-core) . FAILURE [
 3.246 s]
[INFO] GeoMIX TJS for Geoserver UI Module(tjs-web)  SKIPPED
[INFO] Geomix TJS(tjs)  SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 10.748 s
[INFO] Finished at: 2014-09-08T13:48:31+05:30
[INFO] Final Memory: 48M/510M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile
(default-compile) on project tjs-core: Compilation failure

Please kindly guide how to deploy geoserver with TJS service...


README.md
Description: Binary data
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users