Bug #23978
closedHTTP 500 error while publishing in GRSF Admin and GRSF Public VREs
100%
Description
We encounter an error while trying to publish records in GRSF Admin (https://services.d4science.org/group/grsf_admin/) and GRSF (https://services.d4science.org/group/grsf) VREs.
We face the following HTTP 500 error:
java.lang.Exception: Method failed: HTTP/1.1 500 Internal Server Error; Response body: {"id":null,"knowledge_base_id":null,"product_url":null,"error":"Sorry but there was not possible to retrieve your fullname/email!"}
I think that it is related to #23679#note-3 where the same error occurred in GRSF PRE and was fixed.
Related issues
Updated by Yannis Marketakis over 2 years ago
- Blocks Task #23974: Approve-Merge-Archive GRSF records added
Updated by Yannis Marketakis over 2 years ago
- Related to Bug #23679: HTTP 500 error while publishing in GRSF PRE added
Updated by Luca Frosini over 2 years ago
It seems happening to me only in the first request.
Can you please confirm that a subsequent request is successful for you?
I'm going to investigate the issue.
Updated by Yannis Marketakis over 2 years ago
Hi @luca.frosini@isti.cnr.it
I just checked and it happens to me every time.
The GRSF publisher VRE is https://smart-grsf-admin.d4science.org/grsf-publisher-ws/rest/
Updated by Anne Elise Nieblas over 2 years ago
Hello, Has there been any progress on addressing this error? Thanks, Anne-Elise
Updated by Luca Frosini over 2 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
The patch to solve the issue in the service is going to be released see #23679. As soon as such a version will be deployed in production the issue should be solved.
Updated by Yannis Marketakis over 2 years ago
What are the plans/time schedule for the deployment? I just tried updating in GRSF Admin and I still face HTTP 500
Updated by Luca Frosini over 2 years ago
Yannis Marketakis wrote in #note-8:
What are the plans/time schedule for the deployment? I just tried updating in GRSF Admin and I still face HTTP 500
As soon as all the test in GRSF_Pre will be passed the service will be upgraded
Updated by Yannis Marketakis over 2 years ago
- Status changed from Feedback to Closed
I just tested that on GRSF Admin and it no longer raises a HTTP 500 error.
The issue can be closed.
Thanks