Message3056
>> Your System.currentTimeMillis().toString() throws an
>> AttributeError looking for toString.
>How did you figure out the exception? No exception occurs when I ran
>the program natively. Do I need to put some debug options to Jython so
>it runs in debug mode? If I know the way, I'll use it next time.
>Thanks!
The exception not showing actually has to do with java.util.concurrent,
not Jython. When an exception is thrown by code run in an
ScheduledExcutionThreadService, there's no where for the exception to be
caught immediately, so concurrent can't just print it out to the console
because it isn't sure that you don't want to catch it. However, when
you call get on the ScheduledFuture returned by schedule, it throws an
ExecutionException if the scheduled code threw and exception while it
was running. The ExcecutionException thrown will return the original
exception from getCause. |
|
Date |
User |
Action |
Args |
2008-02-29 17:15:13 | cgroves | set | spambayes_score: 0.00744895 -> 0.0074489526 recipients:
+ cgroves, leo_sakaguchi |
2008-02-29 17:15:13 | cgroves | set | spambayes_score: 0.00744895 -> 0.00744895 messageid: <1204305313.76.0.916072542733.issue1001@psf.upfronthosting.co.za> |
2008-02-29 17:15:13 | cgroves | link | issue1001 messages |
2008-02-29 17:15:12 | cgroves | create | |
|