There are several reasons you might need to know from which JAR(s) file class is loaded.
Now it is quick and easy with BiWhy.
Problem:
There is a leftover from a private fix or previous version causing problems in the current version.
A frequent cause for this is an old file renamed as original_backup.jar
DON’T do this! Change extension instead, for example: original.jar_backup
JAVA is not looking for JARs by their names unless they are listed in MANIFEST.
It loads everything from CLASS_PATHs till it finds the class it needs.
original_balckup.jar is still a valid JAR file; if it is anywhere in CLASS_PATH, for example, next to original.jar, the class will be loaded from the first JAR that JAVA has found.
The process is not deterministic, so next time it might be loaded from another JAR, or different class loaders might load it from different JARs files.
As a result, we might have an assortment of problems, including intermittent.
Solution:
With BiWhy, you can quickly index your JARs.
Search multiple times in results with instant response.
Save, reopen index results or send them to remote support.
Index performance (whole BOBJ installation folder) test: ~2min on small sandbox (depends on the number of CPUs and disk).
Comments