Issue 16751

Registry console shows bad warning/error

16751
Reporter: mdoering
Type: Bug
Summary: Registry console shows bad warning/error
Description: When saving a dataset the registry console tries to show a warning in red on top, but it does have minimal height only and one cannot read anything, see screenshot from page http://registry.gbif-dev.org/web/index.html#/dataset/78ff18a6-1c32-11e2-af65-00145eb45e9a/edit
Priority: Major
Status: Open
Created: 2014-12-12 14:15:04.99
Updated: 2015-03-02 16:27:10.673

Attachment Screen Shot 2014-12-12 at 14.13.38.png



Author: trobertson@gbif.org
Created: 2014-12-12 15:25:52.855
Updated: 2014-12-12 15:25:52.855
        
Response is a 500
{code}
HTTP/1.1 500 Server Error
Date: Fri, 12 Dec 2014 14:22:56 GMT
Server: Jetty(9.1.z-SNAPSHOT)
Connection: close
Transfer-Encoding: chunked
Content-Type: text/plain; charset=UTF-8
{code}
    


Author: trobertson@gbif.org
Created: 2014-12-12 15:46:06.759
Updated: 2014-12-12 15:46:06.759
        
Caused by DoiGeneratorMQ it seems:

{code}
WARN  [2014-12-12 15:45:10,961+0100] [qtp1395048902-235] org.eclipse.jetty.servlet.ServletHandler: /dataset/78ff18a6-1c32-11e2-af65-00145eb45e9a
java.lang.NullPointerException: null
	at org.gbif.registry.doi.DoiGeneratorMQ.isGbif(DoiGeneratorMQ.java:84) ~[registry-ws-2.19-20141212.140817-35.jar:2.19-SNAPSHOT]
	at org.gbif.registry.ws.resources.DatasetResource.update(DatasetResource.java:510) ~[registry-ws-2.19-20141212.140817-35.jar:2.19-SNAPSHOT]
	at org.apache.bval.guice.ValidateMethodInterceptor.invoke(ValidateMethodInterceptor.java:92) ~[registry-ws-2.19-20141212.140817-35.jar:2.19-SNAPSHOT]
	at org.gbif.registry.ws.resources.DatasetResource.update(DatasetResource.java:118) ~[registry-ws-2.19-20141212.140817-35.jar:2.19-SNAPSHOT]
	at org.gbif.registry.ws.resources.BaseNetworkEntityResource.update(BaseNetworkEntityResource.java:250) ~[registry-ws-2.19-20141212.140817-35.jar:2.19-SNAPSHOT]

{code}
    


Author: trobertson@gbif.org
Created: 2015-03-02 14:46:27.912
Updated: 2015-03-02 14:46:27.912
        
The issue was that no message was returned with the 500 error.
The fix is the registry should provide a sensible message: "Error 500 returned from server"