search

hbz / lobid

Linking Open Bibliographic Data
https://lobid.org/
Eclipse Public License 2.0
16 stars 4 forks source link

No (mabxml) source found #228

Closed dr0i closed 7 years ago

dr0i commented 9 years ago

In the play logs there are many WARNing like this one:

2015-09-03 16:53:33,900 - [WARN] - from application in play-akka.actor.default-dispatcher-31 
No source data found for http://lobid.org/resource/HT013046158

While in fact the source is available, try the source tab in http://lobid.org/resource/HT013046158 and also http://lobid.org/resource?id=HT013046158&format=source .

fsteeg commented 9 years ago

Hm, strange. I tried to reproduce this locally, but I don't get the message when I access HT013046158.

It also shouldn't be possible that the XML is both appended and the message is logged in the same request, see: https://github.com/hbz/lobid/blob/master/app/controllers/Application.java#L264

Maybe these messages are caused by separate requests that failed? Like a timeout or a non-200 response from the API at some point (these should be the two scenarios that could cause the message).

dr0i commented 9 years ago

Are these timeouts logged so that this assumption can be proved? Would be good to have these logs in the play logs, can't find them now. I looked again and the issue remains.

fsteeg commented 9 years ago

Opened #229 for improved logging.

dr0i commented 9 years ago

Improved logging in lobid-staging doesn't show any http status codes, though there are still "No source data found" messages.

fsteeg commented 9 years ago

Added status code, opened #230, deployed to staging.

dr0i commented 9 years ago

New code has no effect.

fsteeg commented 9 years ago

Don't know what else to do, unassigning.

dr0i commented 9 years ago

Short status-quo:

Maybe these messages are caused by separate requests that failed? Like a timeout or a non-200 response from the API at some point (these should be the two scenarios that could cause the message).

If the code you commited is working, it must be another scenario.

dr0i commented 7 years ago

As this observation doesn't have any effect we can savely ignore it officially by closing this issue. Sic!