[Swift-devel] "Timer was cancelled" error on Beagle on Swift script termination
Mihael Hategan
hategan at mcs.anl.gov
Sun Mar 27 16:23:58 CDT 2011
Actually I'm not so sure any more.
My java Timer does not seem to have a scheduleImpl method. What version
of java is this?
Mihael
On Sun, 2011-03-27 at 13:58 -0700, Mihael Hategan wrote:
> Thank you good sir!
>
> It seems that the problem occurs when the system is shutting down.
> During JVM finalization it turns out that timers cannot be used. When
> they are, the "Timer was cancelled" error appears.
>
> I'll see how this can be fixed.
>
> On Sun, 2011-03-27 at 15:49 -0500, Michael Wilde wrote:
> > On CI net, in /home/wilde/swift/lab, you can find "logs. Logs please. Logs!!!" :)
> >
> > login1$ grep -i 'timer.*cancel' catsn*.log
> > catsn-20110320-2218-tjaeo8md.log:java.lang.IllegalStateException: Timer was cancelled
> > catsn-20110320-2218-tjaeo8md.log:java.lang.IllegalStateException: Timer was cancelled
> > catsn-20110320-2218-tjaeo8md.log:java.lang.IllegalStateException: Timer was cancelled
> > catsn-20110320-2231-o3tft91h.log:java.lang.IllegalStateException: Timer was cancelled
> > catsn-20110320-2231-o3tft91h.log:java.lang.IllegalStateException: Timer was cancelled
> > catsn-20110320-2257-tpoi32je.log:java.lang.IllegalStateException: Timer was cancelled
> > catsn-20110320-2257-tpoi32je.log:java.lang.IllegalStateException: Timer was cancelled
> > catsn-20110320-2258-02gmt2c7.log:java.lang.IllegalStateException: Timer was cancelled
> > catsn-20110320-2258-02gmt2c7.log:java.lang.IllegalStateException: Timer was cancelled
> > catsn-20110320-2258-02gmt2c7.log:java.lang.IllegalStateException: Timer was cancelled
> > catsn-20110320-2258-02gmt2c7.log:java.lang.IllegalStateException: Timer was cancelled
> > catsn-20110320-2258-2ued34uf.log:java.lang.IllegalStateException: Timer was cancelled
> > catsn-20110320-2258-2ued34uf.log:java.lang.IllegalStateException: Timer was cancelled
> > catsn-20110320-2258-2ued34uf.log:java.lang.IllegalStateException: Timer was cancelled
> > catsn-20110320-2258-2ued34uf.log:java.lang.IllegalStateException: Timer was cancelled
> > catsn-20110321-1600-3j1159na.log:java.lang.IllegalStateException: Timer was cancelled
> > catsn-20110321-1600-3j1159na.log:java.lang.IllegalStateException: Timer was cancelled
> > catsn-20110324-1026-x6yxif12.log:java.lang.IllegalStateException: Timer was cancelled
> > catsn-20110324-1026-x6yxif12.log:java.lang.IllegalStateException: Timer was cancelled
> > catsn-20110324-1026-x6yxif12.log:java.lang.IllegalStateException: Timer was cancelled
> > catsn-20110324-1026-x6yxif12.log:java.lang.IllegalStateException: Timer was cancelled
> > login1$
> >
> >
> > ----- Original Message -----
> > > Ok. I need logs. Logs please. Logs!!!
> > >
> > > On Sat, 2011-03-26 at 02:26 -0700, Mihael Hategan wrote:
> > > > I will look at it on Sunday or Monday.
> > > >
> > > > Mihael
> > > >
> > > > On Sat, 2011-03-26 at 00:28 -0500, Ketan Maheshwari wrote:
> > > > > Hi,
> > > > >
> > > > > The timer error: "Timer was cancelled" persists on beagle. Does
> > > > > anybody been able to resolve it so far?
> > > > >
> > > > >
> > > > > The stack I got today is quite similar to the previous ones:
> > > > >
> > > > >
> > > > > =====
> > > > > Got exception in send
> > > > > java.lang.IllegalStateException: Timer was cancelled
> > > > > at java.util.Timer.scheduleImpl(Timer.java:564)
> > > > > at java.util.Timer.schedule(Timer.java:449)
> > > > > at
> > > > > org.globus.cog.karajan.workflow.service.commands.Command.setupReplyTimeoutChecker(Command.java:155)
> > > > > at
> > > > > org.globus.cog.karajan.workflow.service.commands.Command.dataSent(Command.java:149)
> > > > > at
> > > > > org.globus.cog.karajan.workflow.service.channels.AbstractPipedChannel.actualSend(AbstractPipedChannel.java:89)
> > > > > at
> > > > > org.globus.cog.karajan.workflow.service.channels.AbstractPipedChannel
> > > > > $Sender.run(AbstractPipedChannel.java:115)
> > > > > Got exception in send
> > > > > java.lang.IllegalStateException: Timer was cancelled
> > > > > at java.util.Timer.scheduleImpl(Timer.java:564)
> > > > > at java.util.Timer.schedule(Timer.java:449)
> > > > > at
> > > > > org.globus.cog.karajan.workflow.service.commands.Command.setupReplyTimeoutChecker(Command.java:155)
> > > > > at
> > > > > org.globus.cog.karajan.workflow.service.commands.Command.dataSent(Command.java:149)
> > > > > at
> > > > > org.globus.cog.karajan.workflow.service.channels.AbstractPipedChannel.actualSend(AbstractPipedChannel.java:89)
> > > > > at
> > > > > org.globus.cog.karajan.workflow.service.channels.AbstractPipedChannel
> > > > > $Sender.run(AbstractPipedChannel.java:115)
> > > > > java.lang.IllegalStateException: Timer was cancelled
> > > > > at java.util.Timer.scheduleImpl(Timer.java:564)
> > > > > at java.util.Timer.schedule(Timer.java:449)
> > > > > at
> > > > > org.globus.cog.karajan.workflow.service.commands.Command.setupReplyTimeoutChecker(Command.java:155)
> > > > > at
> > > > > org.globus.cog.karajan.workflow.service.commands.Command.dataSent(Command.java:149)
> > > > > at
> > > > > org.globus.cog.karajan.workflow.service.channels.AbstractStreamKarajanChannel$Sender.run(AbstractStreamKarajanChannel.java:253)
> > > > > Canceling job 21995.sdb
> > > > >
> > > > > =====
> > > > >
> > > > >
> > > > >
> > > > > Ketan
> > > > >
> > > > >
> > > > > On Mon, Mar 21, 2011 at 6:33 PM, Mihael Hategan
> > > > > <hategan at mcs.anl.gov>
> > > > > wrote:
> > > > > So it is related to PBS. Please send me logs with this
> > > > > problem. The
> > > > > timer thing shouldn't be happening.
> > > > >
> > > > >
> > > > > On Mon, 2011-03-21 at 17:30 -0400, Glen Hocky wrote:
> > > > > > I got rid of the problem by setting my project as per
> > > > > > Ti's
> > > > > > instructions
> > > > > >
> > > > > >
> > > > > > projects --available
> > > > > > projects --set PROJECT
> > > > > >
> > > > > > On Mon, Mar 21, 2011 at 4:44 PM, Mihael Hategan
> > > > > <hategan at mcs.anl.gov>
> > > > > > wrote:
> > > > > > On Mon, 2011-03-21 at 13:23 -0500, Michael Wilde
> > > > > wrote:
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > Mihael, all, do you have any thoughts on what
> > > > > > > that
> > > > > might be?
> > > > > >
> > > > > >
> > > > > > Yes, but what I think it is wouldn't (in any
> > > > > > obvious
> > > > > way I can
> > > > > > see) be
> > > > > > influenced by changes in the environment.
> > > > > >
> > > > > > If you look at the logs, is there anything else
> > > > > suspicious
> > > > > > going on?
> > > > > >
> > > > > > Mihael
> > > > > >
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Swift-devel mailing list
> > > > > > Swift-devel at ci.uchicago.edu
> > > > > >
> > > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Swift-devel mailing list
> > > > > Swift-devel at ci.uchicago.edu
> > > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Swift-devel mailing list
> > > > > Swift-devel at ci.uchicago.edu
> > > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > > >
> > > >
> > > > _______________________________________________
> > > > Swift-devel mailing list
> > > > Swift-devel at ci.uchicago.edu
> > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > >
> > >
> > > _______________________________________________
> > > Swift-devel mailing list
> > > Swift-devel at ci.uchicago.edu
> > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
More information about the Swift-devel
mailing list