On WebSphere container and IBM JDK objects of type Method should not be cached. This is currently done in property descriptors (MapPropertyDescriptor for example). This results in extensive amount of ClassLoaders being created and not garbage collected as each method.invoke() reflective accessor results in new ClassLoader creation on given environment. Then classloaders gets attached to Dozer context.
Workaround is to increase Perm Size of JVM and perform "hard" restart from time to time. Issue is reproducible after several redeployments of the application.
Log in to post a comment.