New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scheduler GUI fails if user asks logs for a job and disconnects immediatly after. #221

Closed
activeeon-bot opened this Issue Mar 31, 2009 · 1 comment

Comments

Projects
None yet
1 participant
@activeeon-bot

activeeon-bot commented Mar 31, 2009

Original issue created by Germain SIGETY on 31, Mar 2009 at 18:29 PM – SCHEDULING-227

User gets logs for a job, and disconnects immediately after. A stack trace appears :

2009-03-31 17:46:31.297::INFO: Logging to STDERR via org.mortbay.log.StdErrLog
2009-03-31 17:46:31.336::INFO: jetty-6.1.11
2009-03-31 17:46:31.432::INFO: Started SelectChannelConnector@0.0.0.0:42565
76483@paquito.inria.fr – (link: INFO oactive.remoteobject) Remote Object Factory provider <pamr, class org.objectweb.proactive.extra.messagerouting.remoteobject.MessageRoutingRemoteObjectFactory> found
76483@paquito.inria.fr – (link: INFO communication.rmi) Created a new registry on port 6641
76483@paquito.inria.fr – (link: INFO proactive.mop) Generating class : pa.stub.org.ow2.proactive.scheduler.gui.data.StubJobsController
76483@paquito.inria.fr – (link: INFO proactive.mop) Generating class : pa.stub.org.ow2.proactive.scheduler.gui.data.
StubSchedulerProxy
76483@paquito.inria.fr – (link: INFO admin.factory) Job successfully created !
Exception in thread “Thread-12” java.lang.IllegalStateException: Timer already cancelled.
at java.util.Timer.sched(Timer.java:354)
at java.util.Timer.schedule(Timer.java:170)
at org.ow2.proactive.scheduler.gui.data.JobOutputAppender.append(JobOutputAppender.java:105)
at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)
at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65)
at org.apache.log4j.Category.callAppenders(Category.java:203)
at org.ow2.proactive.scheduler.common.util.SimpleLoggerServer$ConnectionHandler.run(SimpleLoggerServer.java:228)
at java.lang.Thread.run(Thread.java:619)

After if user reconnects with the instance of Scheduler GUI, and asks again for logs, logs are not displayed.

@activeeon-bot

This comment has been minimized.

Show comment
Hide comment
@activeeon-bot

activeeon-bot Apr 1, 2009

Original comment posted by Christian Delbé on 01, Apr 2009 at 20:42 PM

One warning from log4j on core side remains (the socketappender still try to connect to dead log server).

activeeon-bot commented Apr 1, 2009

Original comment posted by Christian Delbé on 01, Apr 2009 at 20:42 PM

One warning from log4j on core side remains (the socketappender still try to connect to dead log server).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment