When using Cartaro distribution, I experience random 500 Internal Server errors, which I was unable to solve. I created WFS layer based on PostGIS field. When I'm using this layer in Openlayers, I experience errors like this randomly:

"NetworkError: 500 Internal Server Error - http://<my-ip-address>:8080/geoserver/cartaro/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=cartaro%3Amosty_2&outputFormat=text%2Fjavascript&srsName=EPSG%3A3857&bbox=-958826.0834375,5361598.9118751,4207094.0352625,7318386.8356251,EPSG%3A3857&format_options=callback%3AOpenLayers.Protocol.Script.registry.c2"

When I copy and paste this URL to browser, I'm able to reload it indefinitely without any problems. Also direct access like

http://<my-ip-address>:8080/geoserver/cartaro/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=cartaro:mosty_2&maxFeatures=50

works without any problems. I tried to look into my Geoserver log, but found nothing interesting, layers seems to be accessed dorrectly.

2013-10-11 09:17:07,222 INFO [geoserver.wfs] - 
Request: getServiceInfo
2013-10-11 09:17:07,229 INFO [geoserver.wfs] - 
Request: getFeature
    service = WFS
    version = 1.0.0
    baseUrl = <my-ip-address>:8080/geoserver/
    query[0]:
        filter = [  bbox POLYGON ((-958826.0834375 5361598.9118751, -958826.0834375 7318386.8356251, 4207094.0352625 7318386.8356251, 4207094.0352625 5361598.9118751, -958826.0834375 5361598.9118751)) ]
        srsName = EPSG:3857
        typeName[0] = {http://cartaro}mosty_2
    outputFormat = text/javascript
    resultType = results
    formatOptions = {CALLBACK=OpenLayers.Protocol.Script.registry.c2}
2013-10-11 09:17:07,231 INFO [wfs.json] - about to encode JSON

I configured my Geoserver Catalog mode to "challenge". Could this be the source of problem?

I am using latest Cartaro version, Geoserver 2.3.5

CommentFileSizeAuthor
Výběr_113.png812.96 KBmilos.kroulik
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

ulim’s picture

ulim CreditAttribution: ulim commented
Assigned: Unassigned » azuledu
ilpise’s picture

ilpise CreditAttribution: ilpise commented

I'm affected from the same random error.
I'm not using Cartaro but I've installed all the modules it uses.
In a first installation without the Cartaro extension for the drupal/geoserver users integration I've never experimented the error.
Moving the web site on another machine with the Cartaro extension for the drupal/geoserver users integration the random error is present.

Are you using the Cartaro extension for the drupal/geoserver users integration in your installation?

milos.kroulik’s picture

milos.kroulik CreditAttribution: milos.kroulik commented

Yes, that's how I tried to use it. However, I had to abandon this solution, so i don't know, if the issue is still present in recent versions of that integration.

Are you using the latest version?

friedjoff’s picture

friedjoff CreditAttribution: friedjoff commented

Hi,

we have made some improvements regarding this problem in the geoserver-sec-drupal plugin. Which version of the plugin are you using? Can you give more information on how to reproduce this behavior?

BTW: you can download the most recent version here: http://dl.geops.de/geoserver-sec-drupal/

ilpise’s picture

ilpise CreditAttribution: ilpise commented

I'm using the geoserver-sec-drupal-7.x-1.2.jar extension with Geoserver 2.4.3

The error became more frequent if you set enable and active some layers on the front page map.
I will try with the new geoserver-sec-drupal-7.x-1.3.jar in this days and make you know.

Thanks.

ilpise’s picture

ilpise CreditAttribution: ilpise commented

Just substitute the geoserver-sec-drupal-7.x-1.2.jar with the geoserver-sec-drupal-7.x-1.3.jar and the error seems to be gone away.

Thank you friedjoff.

friedjoff’s picture

friedjoff CreditAttribution: friedjoff commented
Status: Active » Closed (fixed)

Great!