Tag Info

Hot answers tagged

7

GeoServer is a Java web application packaged as a WAR file. It needs to be deployed in a Java servlet container of which Apache Tomcat is an implementation. You could also use another servlet engine like Jetty. So in order to use GeoServer, you will be obliged to use a Java servlet container. If you want to avoid the use of a servlet engine, you could also ...


3

Service parameter is mandatory for making requests to WMS services. Your URL should looks like: http://localhost:8080/geoserver/wms/filedata?request=GetCapabilities&service=WMS


3

Ciao, generally speaking I would give GeoServer an amount of heap memory between 1GB and 8GB. It is rather difficult that it will use more than that. It would actually be great if yoy could say more about what kind of data you are serving with GeoServer and which kind of requests you are usually sending to it. A stack trace might help as well. Generally ...


2

You should be pointing OpenLayers to a local proxy. Not the proxy on GeoServer. For example, my OpenLayers.ProxyHost property is like: OpenLayers.ProxyHost = "proxy/proxy.ashx?url="; But you might want something like this: OpenLayers.ProxyHost = "/cgi-bin/proxy.cgi?url="; Documentaion


2

Even though I've never used it, I think GeoNode already does most of what you are asking for.


2

Edit the tomcat configuration file (in conf/server.xml) and add an AccessLog Valve. The common log format already logs the username along with url and is common in the sense that most log processing tool can process it out of the box.


2

The short answer is you could, but you shouldn't. Messing with the internal Tomcat is not recommended and will likely give you issues with Esri technical support if you encounter issues with ArcGIS Server. I have done some playing about with the internal Tomcat at 10.1 and the message from Esri is, don't do it (understandably as it might have knock on ...


2

You forgetting to copy the *jni.so files to your shared library folder. As state on gdal java documentation http://trac.osgeo.org/gdal/wiki/GdalOgrInJavaBuildInstructionsUnix: To deploy you need gdal.jar in your class path, the 4 .so files (libgdalconstjni.so, libgdaljni.so, libogrjni.so and libosrjni.so) and libgdal.so in your shared library path. ...


2

I suspect an out of memory error: the first application to be accessed will issue a large (how many features are fetched with every layer?) WFS request which completes, but prevents further requests from being carried out successfully. This explains the works-after-restart behaviour as with a restart all JVM memory would be released and then reallocated ...


2

Your first app is attempting to load the web map from a file:// uri (see the Chrome console error: "Unable to load file://www.arcgis.com/sharing/...") and not http (or https) as it should. Are you sure you are hosting the html in a page served out by your web server and not just double clicking it to open directly from the file system?


2

The page Building and installing the PHP GDAL extension in the Drupal Community Documentation is helpful. The main part being to download and install from source, php5-gdal from its github repository. Some development tools may need to be installed before-hand. phpize ./configure make sudo make install Then configure and enable the module. sudo echo ...


2

Yes, you have to use proxy. The only format that allows cross-domain (and cross-port) access is JSONP, not pure JSON.


2

Yes, you can use exactly the same mechanism to limit access to any web application. If the web application doesn't have a context.xml file you can simply create an empty one and add what you need.


2

Location of cache directory must be accessible to the operating system, meaning that you must mount that folder (Linux) or map drive (Windows). After that you just put absolute path to that directory. Linux <context-param> <param-name>GEOWEBCACHE_CACHE_DIR</param-name> <param-value>/cache_directory</param-value> ...


1

The problem is not related to the version of tomcat but to new changes in geoNetwork that don't expect geoNetwork to be the ROOT application. I'm not sure if there is an issue already opened, but if not, you can open it. The fast solution will be to place geoNetwork not on the ROOT app. As tomcat wants to work on port 8080, I usually use an apache2 ...


1

Ciao, maybe I overlooked something but from the outside you are accessing http://mydomain.com/geoserver/ not http://mydomain.com:8080/geoserver/ as the default port for Apache HTTP is port 80, hence connecting to port 8080 on it would give you exactly that error. Regards, Simone.


1

This problem occurs when your .war is bigger than the value in config file of the tomcat manager. You need to set the config in web.xml from the tomcat manager. The file will normally be in %tomcat installation%\webapps\manager\WEB-INF\web.xml Look for: <multipart-config> <!-- 50MB max --> <max-file-size>52428800</max-file-size> ...


1

I would say start by reading through the documentation for OpenGeo Suite. It has good guides that should walk you through everything from installation to building and deploying an application. http://suite.opengeo.org/docs/latest/


1

I think so, but I would check this guide for more information: http://geoserver.geo-solutions.it/edu/en/clustering/load_balancing/microsoft_IIS.html Personal note, expose them on port 80 rather than 8080. Many close environmente won't let people access a link with port different from 80. Simone.


1

You cannot have different tomcats listening to the same port. Said that, it is good to have separated tomcats for big java apps, just because if one of them have problems like running out of memory, you can restart that app without having to bother the other app. Running out of memory is common for certain use cases on geoServer. So, it really depends on ...


1

I had a similar issue (java.lang.nullPointerException resulting in pink screen in layer preview), although I was not able to preview the layer at all. The cause was that the layer store was configured without a workspace. I was able to fix the problem by removing and rebuilding the layer store within a valid workspace. See this post from the Geoserver ...


1

I fixed it! If you layer in the Publishing tab, in the list of "Selected Styles" have records of styles, then we get this error. I deleted the source Geoserver 2.2 these records and to save the layer. Moved workspace to a new Geoserver abd can see all the layers!


1

The Suite 3.0.2 Ubuntu Packages don't work with Ubuntu 13.04. Officially they are for Ubuntu 10.04 or 10.10 and they seem to work on 12.04 without trouble, but they break on 13.04.


1

This has nothing to do with the servlet-api-2.5.jar (note that the message that refers to this file is an INFO message not an error message). If you want to stop that message appearing just delete the file. The problem starts with this message: 5 mai 2013 14:10:35 org.geoserver.platform.GeoServerExtensions checkContext GRAVE: Extension lookup occured, ...


1

I recall that geoserver 2.3 wants java 1.6 up, maybe your tomcat is using an older version.


1

As I can see you used projection 70066 and it looks like you faced with projection issue. Check Declared SRS and Lat/Lon Bounding Box options of your layer.


1

GDAL is a C++ library which offers wrappers for other languages: python, java, etc. So in addition to use the JAR file you need to have the libraries installed on each.


1

To work with geocoder in OTP please refer to this post. here There are some slight improvements to the above post though( I have to spent hours to figure them out!), these are as follows For Google basemap In config.js just add these codes after the OSM declaration in baselayers: new OpenLayers.Layer.Google( "Google"), Add the Google Maps ...


1

I figured it out. It was http proxy problem.


1

as @unicoletti says it is almost certainly not JAI as if it was the layer preview wouldn't work. More likely problems are javascript errors or the browser not being able to see the OpenLayers library. The easiest way to see what's up is to add firebug to firefox and look at the console to see what the error is.



Only top voted, non community-wiki answers of a minimum length are eligible