Jaikoz- Discussion Forum

Hi the 503 error could be misleading I have just discovered the following bug that will affect a small amount of files.

I would need you to send me your logs with Action/Create Support Files to check but I think you are encountering the follow error.

The error will only occur for tracks that have no artist, no album and a track no of the form x/y. What happens is Jaikoz constructs a query based partly on the track no but because track no isn't a simple number (i.e 1 versus 1/10) it fails to extract the number properly and the query sent to Musicbrainz is invalid. The workaround is to manually change the trackno field or run Action/Local Correct/Track No Correct to change fields from x/y to x . Of course this means you lose the TotalTrack information. This will definently be fixed fopr next release.

That is DEFINITELY the issue I'm experiencing, Paul. I checked the file it was consistently reaching on timeout and it fits the characteristics you describe:

-no artist
-no album
-track in fraction form

Removing the track from Jaikoz ("Close File") resolved the issue and I'm now querying MusicBrainz for files beyond the point where it was timing out.

Not a fix, per say, but at least a workaround until the next release

paultaylor wrote:

The error will only occur for tracks that have no artist, no album and a track no of the form x/y. What happens is Jaikoz constructs a query based partly on the track no but because track no isn't a simple number (i.e 1 versus 1/10) it fails to extract the number properly and the query sent to Musicbrainz is invalid. The workaround is to manually change the trackno field or run Action/Local Correct/Track No Correct to change fields from x/y to x . Of course this means you lose the TotalTrack information. This will definently be fixed fopr next release.

I was about to post about a "503 Busy" problem I had, when I decided to search the forums first and found this post. This is probably the same problem I am having. The console (which is always open because I start Jaikoz with jaikoz.bat) even shows the partial queries used:

debug output wrote:

19/10/2008 19.04.01:com.jthink.jaikoz.manipulate.musicbrainzhelper.MusicBrainzServerQuery:performQuery:WARNING: URL:http://musicbrainz.org/ws/1/track/?type=xml&limit=10&query=track:"Psycho Theme" AND () AND qdur:(85 86 87 88 89 ) failed with error code:503

The track in question only has a title ("Psycho Theme") and a track number specified. The track number is not in the format TrackNumber/TotalTracks; it's actually just "00". It also has a MusicIP ID, "f40d920b-dea0-5e9d-a8d9-c0d9bd3bcb36", should that matter. :)

Do you already have an idea when a version with this fixed will be released?

Nocturnal wrote:

The track in question only has a title ("Psycho Theme") and a track number specified. The track number is not in the format TrackNumber/TotalTracks; it's actually just "00". It also has a MusicIP ID, "f40d920b-dea0-5e9d-a8d9-c0d9bd3bcb36", should that matter. :)

Do you already have an idea when a version with this fixed will be released?

Ok so '00' breaks it as well, This issue is fixed in dev but it might be a month before there is another release so you'll have to work round it for now by modifying the track no field, or entering something in the artist or album field.

The MusicIP Id is irrelevent to this problem

A reply in less than an hour, that's fast support!

Paul,

I found another issue. I had a song with the title:

Pavane Pour Une Infante Defunte\

The trailing backslash was causing the 503 error when connecting to MusicBrainz. The only error reported on the console was "MiniProcess 0 having problems connecting to MusicBrainz Service, may be down or just busy"...

Removing the trailing slash got rid of the problem. I don't know if it is improper escaping of characters in Jaikoz or an issue with MusicBrainz.

-jim

Thanks JIm, problem verified

Is this random in nature?

If I get this failure, simply retrying will allow it to go further before perhaps failing again. Sometimes with a retry and will then fail around where it failed before.

However, with persistence, I can get it to complete.

I have been considering a downgrade to 2.6.0 just to remove the issues. Is this safe with the existing preference file or should I remove that and redo my settings.

Is this problem in 2.6.0 as well. I don't recall seeing it before.

Christian

The error is due to the track being in the format TrackNumber/TotalTracks, so the best workaround is to run Track Correct with the default settings it will chnage the value to just Track Number, and then you shouldnt normaly get this problem. There are a couple of other issues that can give the same erro but these are rarer, if you want to send me your support files I can confirm if this is the problem you are having.