Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3525
@netguy204 I think you are affected by a different issue. In your case,
there are no damaged jar files, but it looks like the classloader has been
closed.
Flink creates classloaders per job and caches them across different tasks
of that job. It closes the dynamically created classloaders when all tasks from
the job are done.
Is it possible that a classloader passes between jobs, meaning that another
job uses a class loaders that was created for another job? Do you store some
objects / classes / classloaders somewhere in a static context or a cache or
interner so that it can be that one job created them and another job re-uses
them?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
