Issue1001

Symptom:
Attached Jython program doesn't work as intended on Jython 2.2 and 
2.2.1. It works fine on Jython 2.1. Tried it with Sun Java 1.5.0_13.
The program should print System.currentTimeMillis() per each 5 seconds 
for 60 seconds period (12-13 times), but with Jython 2.2, it won't 
print anything then finishes after 60 seconds. The program uses 
java.util.concurrent libraries which are available at Java 5.0 and 
later. Not sure where the root cause relies.

System.currentTimeMillis returns a long which is wrapped in a PyLong
when exposed to Python. As of 2.2, PyLong is a newstyle type so it only
exposes python methods on it. In 2.1 it mistakenly exposed the Java
method toString. Your System.currentTimeMillis().toString() throws an
AttributeError looking for toString. You can use
str(System.currentTimeMillis()) instead.

Thanks a lot pointing out the problem, also for a very agile answer. 
That solved my problem.
> 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!

>> 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.