Good catch! That should do it if you have access to the local storage of the JobManager.
On Wed, Jul 20, 2016 at 5:25 PM, Aljoscha Krettek <aljos...@apache.org> wrote: > Hi, > in the JobManager log there should be a line like this: > 2016-07-20 17:19:00,552 INFO > org.apache.flink.runtime.webmonitor.WebRuntimeMonitor - Using directory > /some/dir for web frontend JAR file uploads > > if you manually delete the offending jar file from that directory it could > solve your problem. > > Cheers, > Aljoscha > > On Wed, 20 Jul 2016 at 15:37 Maximilian Michels <m...@apache.org> wrote: >> >> Hi Gary, >> >> That is a bug. The main method might actually be there but it fails to >> load a class: >> > Caused by: java.lang.ClassNotFoundException: >> > org.shaded.apache.flink.streaming.api.functions.source.SourceFunction >> >> It looks like internal Flink classes have been shaded but not included >> in the job jar. >> >> AFAIK there is no way to recover this. You'll have to restart the web >> frontend which is currently tied to the JobManager. You'll have to >> restart the JobManager. >> >> Cheers, >> Max >> >> On Wed, Jul 20, 2016 at 2:52 PM, Gary Yao <gary....@zalando.de> wrote: >> > Hi all, >> > >> > I accidentally packaged a Flink Job for which the main method could not >> > be looked up. This breaks the Flink Dashboard's job submission page >> > (no jobs are displayed). I opened a ticket: >> > >> > https://issues.apache.org/jira/browse/FLINK-4236 >> > >> > Is there a way to recover from this without restarting the JobManager? >> > >> > Best, >> > Gary
