GeoServer

StatusPage "release locks" is unimplementable, either remove the option or implement releasing all in geotools LockingManager

Details

  • Type: Task Task
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.0-alpha1
  • Fix Version/s: 2.0.x
  • Component/s: Wicket UI
  • Labels:
    None
  • Number of attachments :
    0

Description

The old UI has the option "release all locks" in the status page.
It delegates to Data.lockReleaseAll()
Ironically, Data.lockReleaseAll() does nothing because there's no such method like LockingManager.releaseAll() in GeoTools, so it just iterates the datastores, grabs their LockingManagers and does nothing.

Understandably, there's no replacement for Data.lockReleaseAll() in the new configuration's Catalog

So we should either remove this option from StatusPage or see what to do about GeoTools' LockingManager.releaseAll()

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
David Winslow added a comment -

If we don't have the functionality in the current version, I say we take it out. People can just kill GeoServer if they need to release locks, right? (I would think this is better anyway since it guarantees no sudden requests will force GeoServer to re-acquire the locks.)

Show
David Winslow added a comment - If we don't have the functionality in the current version, I say we take it out. People can just kill GeoServer if they need to release locks, right? (I would think this is better anyway since it guarantees no sudden requests will force GeoServer to re-acquire the locks.)
Hide
Permalink
Andrea Aime added a comment -

I would say, just remove that portion of the GUI

Show
Andrea Aime added a comment - I would say, just remove that portion of the GUI

People

  • Assignee:
    Justin Deoliveira
    Reporter:
    Gabriel Roldan
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: