Paul,
sorry, no joy here. Issue still exists with BM Server busy.
Here is the spacing between requests that failed:
Feb 10, 2009 12:15:24 AM: WARNING: MiniProcess 0 having problems connecting to MusicBrainz Service, may be down or just busy, retry attempt 1
Feb 10, 2009 12:15:25 AM: WARNING: MiniProcess 0 having problems connecting to MusicBrainz Service, may be down or just busy, retry attempt 2
Feb 10, 2009 12:15:27 AM: WARNING: MiniProcess 0 having problems connecting to MusicBrainz Service, may be down or just busy, retry attempt 3
Feb 10, 2009 12:15:30 AM: WARNING: MiniProcess 0 having problems connecting to MusicBrainz Service, may be down or just busy, retry attempt 4
Feb 10, 2009 12:15:34 AM: WARNING: MiniProcess 0 having problems connecting to MusicBrainz Service, may be down or just busy, retry attempt 5
Feb 10, 2009 12:15:39 AM: WARNING: MiniProcess 0 having problems connecting to MusicBrainz Service, may be down or just busy, retry attempt 6
Feb 10, 2009 12:15:45 AM: WARNING: MiniProcess 0 having problems connecting to MusicBrainz Service, may be down or just busy, retry attempt 7
Feb 10, 2009 12:15:52 AM: WARNING: MiniProcess 0 having problems connecting to MusicBrainz Service, may be down or just busy, retry attempt 8
Feb 10, 2009 12:16:00 AM: WARNING: MiniProcess 0 having problems connecting to MusicBrainz Service, may be down or just busy, retry attempt 9
I thought there were supposed to have a more spaced out starting interval. This starts at 1 second and then increments by one (your new algo I guess). But sometimes when it failed in the past requests were spaced by 5 sec or 3 sec or 7 sec (has always done this). Is this design intent to make initial retries a random starting interval?
I still think the issue is environmental or an uninitialized (or corrupted) variable. It can fail consitantly on a specific file in one period of time but allowing it to sit for say an hour and then retrying will often have that file succeed. Other files around it have no problem at either point in time.
Is there a simple way to trace the exact request and response between Jaikoz and MB? This would at least allow us to isolate whether it is local or an MB interaction.
Christian