The basic reason this occurs is because the JVM grabs the
environment variables when it starts - and since it can only be
started _once_ per job, all required jars need to be available when
it first starts. The "cure" of sign off and back on again works
because the JVM will be restarted in the new job.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.