[Geoserver-devel] [JIRA] (GEOS-8203) Deleting workspace with JDBC Config returns error response

Steve Ikeoka created an issue

GeoServer / BugGEOS-8203

Deleting workspace with JDBC Config returns error response

Issue Type:

BugBug

Affects Versions:

2.10.1, 2.11.1

Assignee:

Unassigned

Components:

JDBCConfig

Created:

29/Jun/17 10:30 PM

Priority:

MediumMedium

Reporter:

Steve Ikeoka

Deleting a single workspace either through the UI or REST in both GeoServer 2.10 and 2.11 when JDBC Configuration is enabled will return an error response even though the workspace is successfully deleted. If multiple workspaces are deleted at the same time through the UI, then the first workspace will be successfully deleted but it will throw an error that prevents the rest of the workspaces from being deleted.

In both the UI and REST, the namespace will be removed before removing the workspace.
org.geoserver.catalog.NamespaceWorkspaceConsistencyListener also deletes the workspace when a namespace is deleted so I think that GeoServer actually tries to delete the workspace twice and the second delete causes the error.
org.geoserver.jdbcconfig.internal.ConfigDatabase.remove(Info) calls findObjectId(info) and tries to check for a null id but findObjectId throws an exception instead of returning null.

Add Comment

Add Comment

Get JIRA notifications on your phone! Download the JIRA Cloud app here.


This message was sent by Atlassian JIRA (v1000.1092.0#100053-sha1:6914530)

Atlassian logo