Can we stop the server from generating a client jar

Question

When an EAR module is deployed, the server generates a large (a few MB) client jar inside the deployment directory. AFAIK this jar is never used for anything unless you have ACC clients. Please correct me if I'm wrong!
Recently, we've had some worrying exceptions logged, indicating that there is a problem reading this client jar, and the context indicates that the server is attempting to set up a class loader for it. Everything works fine anyway.
We have a few hundred EAR's deployed in each of our servers, and the EAR's contain on avarage about 30-40 entity beans, so you can imagine that we worry about every unnecessary resource allocation.
Also, every exception logged requires attention from the admins so we would really like to get rid of these jars if we can, and if they are in fact unnecessary.
TIA,
Gunnar Grim

Answer 1

Hello, Gunnar.
You are correct that the generated jar is for launching clients using ACC. (Historically some users have taken the generated app client jar and added it to the classpath for non-ACC clients, but this is not an officially supported use of it.)
You said that recently exceptions have been reported, which I assume means that this was not always true. It would seem that something in the environment or the applications has changed to trigger the exceptions. Identifying whatever that change has been might help identify the root cause of the new problem. Have you changed anything in the environment or the applications around the time the exceptions began appearing?
Can you post an example of one of the exceptions you are concerned about?
Also, what version of the product are you using?
- Tim