Skip to main content

How to determine which jar a class is loaded from?

--
Did you ever encounter an runtime exception saying a method not found? How can the code compile if the method is not defined? Or after you made some changes to the code, you don't see it takes effect, even after you clean built, and redeploy for a couple of times? When these situations occurs, besides trying to pull your hair out, you can in fact find out which jar the class in trouble is loaded from. More than often, there is another jar file sitting the the classpath which contains the exact same class.
 

If you are handy in shell scripts, you may come up with a simple script using "find" to track down all the jar files in the class path that contains the class you are looking for.


    If you are not a script guru, you can try the following:
    Put this code snippet inside any one of the method of any one of the class:     Class klass = ClassInTrouble.class;
    CodeSource codeSource = klass.getProtectionDomain().getCodeSource();
    if ( codeSource != null) {
        System.out.println(codeSource.getLocation());
    }



When the method that contains this sniplet is called, it will print out something like:
file://c:/dev/source/lib/myjar.jar
 
Will the codeSource be null? The answer is yes. When a jar file is loaded by the system class loader, it's codeSource will be null. What jars will be loaded by the system class loader? the rule of thumb is that all the jars in the class path (not the ones you package in your application) will be loaded by the system class loader. Obviously the above code can't used to find out which jar a class is loaded from, if the jar is loaded by the system class loader. You can use the "verbose" java command line argument when you start the application:
java -verbose app

it will print out every class in each jar the system class loader loads, ie:

[Opened C:\dev\bea\JDK160~1\jre\lib\rt.jar]
[Loaded java.lang.Object from C:\dev\bea\JDK160~1\jre\lib\rt.jar]
[Loaded java.io.Serializable from C:\dev\bea\JDK160~1\jre\lib\rt.jar]
[Loaded java.lang.Comparable from C:\dev\bea\JDK160~1\jre\lib\rt.jar]
[Loaded java.lang.CharSequence from C:\dev\bea\JDK160~1\jre\lib\rt.jar]
[Loaded java.lang.String from C:\dev\bea\JDK160~1\jre\lib\rt.jar]
[Loaded java.lang.reflect.GenericDeclaration from C:\dev\bea\JDK160~1\jre\lib\rt.jar]
......

Comments

Popular posts from this blog

Asynchronous Vs. Synchronous Communications

Synchronous (One thread):   1 thread -> |<---A---->||<----B---------->||<------C----->| Synchronous (multi-threaded):   thread A -> |<---A---->| \ thread B ------------> ->|<----B---------->| \ thread C ----------------------------------> ->|<------C----->|

WebSphere MQ Interview Questions

What is MQ and what does it do? Ans. MQ stands for MESSAGE QUEUEING. WebSphere MQ allows application programs to use message queuing to participate in message-driven processing. Application programs can communicate across different platforms by using the appropriate message queuing software products. What is Message driven process? Ans . When messages arrive on a queue, they can automatically start an application using triggering. If necessary, the applications can be stopped when the message (or messages) have been processed. What are advantages of the MQ? Ans. 1. Integration. 2. Asynchrony 3. Assured Delivery 4. Scalability. How does it support the Integration? Ans. Because the MQ is independent of the Operating System you use i.e. it may be Windows, Solaris,AIX.It is independent of the protocol (i.e. TCP/IP, LU6.2, SNA, NetBIOS, UDP).It is not required that both the sender and receiver should be running on the same platform What is Asynchrony? Ans. With messag

Advantages & Disadvantages of Synchronous / Asynchronous Communications?

  Asynchronous Communication Advantages: Requests need not be targeted to specific server. Service need not be available when request is made. No blocking, so resources could be freed.  Could use connectionless protocol Disadvantages: Response times are unpredictable. Error handling usually more complex.  Usually requires connection-oriented protocol.  Harder to design apps Synchronous Communication Advantages: Easy to program Outcome is known immediately  Error recovery easier (usually)  Better real-time response (usually) Disadvantages: Service must be up and ready. Requestor blocks, held resources are “tied up”.  Usually requires connection-oriented protocol