- August 20, 2007
- 2,161
- 747
- Moderator
- #31
AW: Trouble with Importing
ok, so I have done lot's of input and corrections to TVDB to correct missing infos - but that didn't help for the stopping of the importer (as expected, but it's a benefit anyway...).
The stopping seems to occur on different positions (series) and not always the same, so sounds like maybe a conflict of the parallel threads - that's why I asked for a possibility to serialize the import process parts for testing.
Thanks for the code link - it looks quite straight, maybe the exit appears in the calling routines... I tried to set up a compiler to add some more debuglogging, but failed so far, would need more time (and I am not a developer). If any one (imker, damien?) having a working TVseries dev environment and is willing to add some debugoutputs, I would appreciate this and could maybe narrow down, what's the reason of the stalling.
@Imker: The situation, where the exception are properly caught and written to the log are "no problem" - on those situations, the importer continues - it's the situation where nothing is written in log after "Decompressing stream" - no caught exception, nut also no unhandled exception:
...
00000003 - 14.08.2010 22:03:40 - Retrieving Data from: http://thetvdb.com/api/<apikey>/series/79811/all/de.zip
00000003 - 14.08.2010 22:03:40 - Decompressing Stream...
00000001 - 14.08.2010 22:03:47 - Online Parsing Completed in 01:42:48.7039584
00000001 - 14.08.2010 22:03:47 - Executing SQL: update options set value = '14.08.2010 22:03:47' where property = 'UpdateScanLastTime'
...
But as said - it's possible, that the calling routine exits for another reason (e.g. setting finished to true for an invalid reason?) - couldn't find that ... acccording log, it tries expanding and looking at the code, there is nothing in there ("while ((currEntry = zis.GetNextEntry()) != null)
" does't execute code at all, because there are no more logentries found) - so returning without data to the calling routine? and stopping importer? (just guesses, I know) ...
ok, so I have done lot's of input and corrections to TVDB to correct missing infos - but that didn't help for the stopping of the importer (as expected, but it's a benefit anyway...).
The stopping seems to occur on different positions (series) and not always the same, so sounds like maybe a conflict of the parallel threads - that's why I asked for a possibility to serialize the import process parts for testing.
Thanks for the code link - it looks quite straight, maybe the exit appears in the calling routines... I tried to set up a compiler to add some more debuglogging, but failed so far, would need more time (and I am not a developer). If any one (imker, damien?) having a working TVseries dev environment and is willing to add some debugoutputs, I would appreciate this and could maybe narrow down, what's the reason of the stalling.
@Imker: The situation, where the exception are properly caught and written to the log are "no problem" - on those situations, the importer continues - it's the situation where nothing is written in log after "Decompressing stream" - no caught exception, nut also no unhandled exception:
...
00000003 - 14.08.2010 22:03:40 - Retrieving Data from: http://thetvdb.com/api/<apikey>/series/79811/all/de.zip
00000003 - 14.08.2010 22:03:40 - Decompressing Stream...
00000001 - 14.08.2010 22:03:47 - Online Parsing Completed in 01:42:48.7039584
00000001 - 14.08.2010 22:03:47 - Executing SQL: update options set value = '14.08.2010 22:03:47' where property = 'UpdateScanLastTime'
...
But as said - it's possible, that the calling routine exits for another reason (e.g. setting finished to true for an invalid reason?) - couldn't find that ... acccording log, it tries expanding and looking at the code, there is nothing in there ("while ((currEntry = zis.GetNextEntry()) != null)
" does't execute code at all, because there are no more logentries found) - so returning without data to the calling routine? and stopping importer? (just guesses, I know) ...