Skip to content

Improve error handling on GROBID server connection issues - 503 Service unaviable #9817

@mirek186

Description

@mirek186

JabRef version

5.9 (latest release)

Operating system

GNU / Linux

Details on version and operating system

No response

Checked with the latest development build

  • I made a backup of my libraries before testing the latest development version.
  • I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

  1. Fresh install of 5.9 version
  2. Click "New entry from plain text"
  3. Paste and push "Add to current library" example from docs:
O. Kopp, A. Armbruster, und O. Zimmermann, "Markdown Architectural Decision Records: Format and Tool Support", in 10th ZEUS Workshop, 2018.
  1. Receive 0 entries were parsed

Nothing in the logs when run with --debug flag.
I've opened Wireshark and traced the connection to http://grobid.jabref.org:8070/ and it's throwing 503 error, but that error is not correctly handled by JabRef.

The expected behaviour would be to show the message on the screen that the service is not available or it's unable to parse the file because XYZ instead of just 0 entries were parsed which would suggest something wrong with the format you've sent.

Appendix

...

Log File
Paste an excerpt of your log file here

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions