SongKong Jaikoz

SongKong and Jaikoz Music Tagger Community Forum

Discogs returns error

#1 
30/07/2010 15.56.02:com.jthink.jaikoz.manipulate.discogshelper.DiscogsServerQuer
y:doQuery:SEVERE: Problem sending query to Discogs:http://www.discogs.com/search
?f=xml&type=releases&api_key=c76ed4c171&q=ludwig+van+beethoven+the+piano+sonatas
%2C+volume+vi%3A+sonatas+opp.+54%2C+57%2C+78%2C+79+and+81a+%28piano%3A+andr%C3%A
1s+schiff%29:null
javax.xml.bind.UnmarshalException
 - with linked exception:
[java.io.IOException: Server returned HTTP response code: 503 for URL: http://ww
w.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd]
        at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(
UnmarshallerImpl.java:213)
        at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(U
nmarshallerImpl.java:184)
        at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(Unknown Sou
rce)
        at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(Unknown Sou
rce)
        at com.jthink.jaikoz.manipulate.discogshelper.DiscogsServerQuery.doQuery
(DiscogsServerQuery.java:228)
        at com.jthink.jaikoz.manipulate.discogshelper.DiscogsRESTQuery.queryForC
andidateReleases(DiscogsRESTQuery.java:759)
        at com.jthink.jaikoz.manipulate.CorrectFromDiscogsReleaseAnalyser.analys
eData(CorrectFromDiscogsReleaseAnalyser.java:165)
        at com.jthink.jaikoz.manipulate.CorrectFromDiscogsReleaseAnalyser.runFro
mAutoCorrecter(CorrectFromDiscogsReleaseAnalyser.java:103)
        at com.jthink.jaikoz.manipulate.AnalyserFactory.runAnalyser(AnalyserFact
ory.java:264)
        at com.jthink.jaikoz.manipulate.AutoCorrecter.run(AutoCorrecter.java:233
)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: Server returned HTTP response code: 503 for URL:
 http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown So
urce)
        at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrent
Entity(Unknown Source)
        at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(
Unknown Source)
        at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEnti
ty(Unknown Source)
        at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSou
rce(Unknown Source)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDri
ver.dispatch(Unknown Source)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDri
ver.next(Unknown Source)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$Prolog
Driver.next(Unknown Source)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(U
nknown Source)
        at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next
(Unknown Source)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
l.scanDocument(Unknown Source)
        at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(U
nknown Source)
        at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(U
nknown Source)
        at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown So
urce)
        at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Un
known Source)
        at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.p
arse(Unknown Source)
        at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(
UnmarshallerImpl.java:211)
        ... 10 more

Also another error:

30/07/2010 15.56.31:com.jthink.jaikoz.manipulate.discogshelper.DiscogsServerQuer
y:doQuery:SEVERE: The following output was returned<!DOCTYPE html PUBLIC "-//W3C
//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transi
tional.dtd">
...
BLAH BLAH BLAH I AM A WEBPAGE
...
</body></html><!-- web06:myt:0.011 -->

EDIT: Could this have anything to do with

, from http://www.discogs.com/help/api ?

#2

This is a bug in Discogs, it doesn’t process all search urls correctly, for example it has problems with multiple sequential apostrophes in a query. Ive raised a bug at Discogs and I work round the case I know about.

I assume this error didnt halt Discogs lookup completely it just prevented a lookup for that specific song.

#3

Related error:
If you have correct metadata from discogs, and discogs lookup doesn’t succeed, your files won’t be fixed (correct folder from metadata).

It doesn’t seem as if discogs works for now, so I’ll just drop that from future testing.

#4

The 5000 requests is per ip address, and Jaikoz is only doing a couple of requests per release , not per song so I doubt you would have hit this limit.

The error is as I said before Discogs doesn’t parse all webservice requests correctly, but other than these edge cases works very well. I’m concerned that you say subsequent autocorrect tasks don’t work though if there is an error with Diascogs I’ll check this out again but Jaikoz 3.7.0 has now been released so if there is a problem it will have to go into the next release.

#5

[quote=paultaylor]I’m concerned that you say subsequent autocorrect tasks don’t work though if there is an error…
[/quote]

This definitely happens, and it doesn’t seem that there even needs to be an error for subsequent correcting of filename to fail.

Out of ~1800 files that I just did, 200 failed to have their filename corrected.

#6

Im getting lots of these errors

May 22, 2011 8:48:08 AM: SEVERE: There was a problem submitting a query to Discogs for song 1,022 with filename 09 - Main Ingredient.mp3: null

#7

Support files could be useful

#8

Sure :slight_smile: i have one, but must wait, im saving now :slight_smile: