Version 5

    Notes on Building and Implementing JBoss Profiler for Solaris


    • The default download does not contain the Solaris binary or the Solaris build script.

    • Download the JBoss Profiler CVS project into $HOME/jboss-profiler.

    • You can use CVSGrab if you are behind a firewall. Use the following command:


    cvsgrab -url


    • Go to the directory $HOME/jboss-profiler/native/solaris

    • Create a new directory $HOME/jboss-profiler/native/solaris/bin

    • Add the following lines to the file or set the environment before running the command:


    JAVA_HOME="<The JAVA Home>"
    export JAVA_HOME


    • Make sure g++ is in your path. To test this, type which g++.

    • Execute the file.

    • When the process is complete, you should find in the $HOME/jboss-profiler/native/solaris/bin directory.

    • Modify your <jboss-home>/ file to add a LD_LIBRARY_PATH entry. This tells the Java VM where to find the native library. The entry should look something like this:


    export LD_LIBRARY_PATH


    • Add the -XrunjbossInspector option to the Java command line as described in $HOME/jboss-profiler/readme.txt.

    • Now you are ready to start JBoss.

    • If you see this error, it means that the Java VM could not find the or could not load its dependencies.


    Error occurred during initialization of VM
    Could not find -Xrun library:


    • If this occurs, check the following:


      • Make sure your LD_LIBRARY_PATH contains the directory containing the file.

      • Start the application server using truss and look for any errors:


    truss ./ > t.txt 2> t.txt


    Then peer at the contents of t.txt.


      • The Java VM may be finding the file just fine, but cannot locate its dependencies. You may need to determine which libraries the depends on an add their directories to the LD_LIBRARY_PATH. Do this as follows:


        • Go to $HOME/jboss-profiler/native/solaris/bin

        • Issue the command ldd

        • You will see output like this:


    $ ldd
   =>        (file not found)
   =>     /usr/lib/
   =>         (file not found)
   =>     /usr/lib/
   =>    /usr/lib/


        • For every entry that says (file not found), find the location of that library and add it to your LD_LIBRARY_PATH.

        • You can issue a search for libraries like this:


    find / -name -print 2>&-