GeoServer

GeoServer 1.7.x can randomly eat the data dir

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 1.7.0-RC2
  • Fix Version/s: 1.7.0-RC3, 2.0.x
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

That happened to me and Arne once. All the coverages and feature types gone, the datastore and coverage stores were still around thought.
This must be fixed, yet there are two things that would make it less fatal and easier to spot

  • istead of deleting the info.xml files, rename them to info.xml.bak
  • reload the catalog from the files on save, so that you know what's happening when the catalog goes away (instead of realizing that when you restart geoserver)

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Justin Deoliveira added a comment -

hard to track this one down... kind of like trying to chase a cloaked romulan warbird . I suggest we implement the backup strategy and hopefully the issue will become clear. Agreed?

Show
Justin Deoliveira added a comment - hard to track this one down... kind of like trying to chase a cloaked romulan warbird . I suggest we implement the backup strategy and hopefully the issue will become clear. Agreed?
Hide
Permalink
Andrea Aime added a comment -

I really think we should do the second one as well, so that the bug becomes apparent the moment it triggers. We should also solve GEOS-2203 so that feature types are preserved. And then yes, we sit and wait for the warbird to uncloak and fire a quantum torpedoe at it.

Show
Andrea Aime added a comment - I really think we should do the second one as well, so that the bug becomes apparent the moment it triggers. We should also solve GEOS-2203 so that feature types are preserved. And then yes, we sit and wait for the warbird to uncloak and fire a quantum torpedoe at it.
Hide
Permalink
Andrea Aime added a comment -

All these issues have been in "resolved" state for at least one month (many of them, much more than that). Since no one has reopened them, I'm mass-switching them to closed state. Reopen if you feel the issue has not been addressed properly.

Show
Andrea Aime added a comment - All these issues have been in "resolved" state for at least one month (many of them, much more than that). Since no one has reopened them, I'm mass-switching them to closed state. Reopen if you feel the issue has not been addressed properly.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.