1.) execute java -version or java -fullversion commands
a.) java -version
- The output provides the following information:
- The first line indicates the Java standard edition class library level.
- The second line includes information about the build level of the runtime environment. Service refresh (SR), fix pack (FP), and APAR (Interim fixes only) numbers are appended to the build string.
- The third line indicates the build level of the Java virtual machine.
- Subsequent lines provide detailed information about the levels of components that make up the runtime environment.
- Exact build dates and versions change for service refreshes and fix packs.
b.) java -fullversion
- The output only lists the build information for the runtime environment.
2.) execute manageSDK commands:
- app_server_root/bin/managesdk -listAvailable -verbose
- (Displays a list of all SDK names available to the product installation)
- app_server_root/bin/managesdk -listEnabledProfile -profileName AppSrv02 -verbose
- (Displays a list of all SDK names that a specified profile, and its node and servers, is currently configured to use)
- app_server_root/bin/managesdk -listEnabledProfileAll -verbose
- (Displays a list of all profiles in an installation and the SDK names that each profile, and its node and servers)
3.) execute versioninfo -long command:
- To receive not only information about the Installed Fixpacks, but also Interim Fixpacks (iFixes), also pertaining to Java.
4.) Review Log Files:
a.) Check SystemOut.log on Traditional Full Profile WebSphere for 'Start Display Current Environment, Java version ='. Native_StdErr.log should also contain
b.) Ceck Console.log & Messages.log in Liberty Profile for or 'java.version ='.
5.) Generate a Javacore text dump and check section ENVINFO subcomponent dump routine for tag 1CIJAVAVERSION.
a.) from the Administrative Integrated Solutions Console:
- Navigate to Troubleshooting > Java dumps and cores
- Select the server(s) to collect dumps from
- Click on Java Core
b.) using javadump (server javadump <server_name>)
c.) using Unix (kill -3 PID) command
d.) using Windows CTRL+BREAK
e.) using WSAdmin command line interface:
Launch wsadmin from the bin directory of the application server profile (such as <WAS_HOME>\profiles\<PROFILE_NAME>\bin\wsadmin). Make sure you connect to the correct SOAP port for the application server or deployment manager.
Run the following commands:
set jvm [$AdminControl completeObjectName type=JVM,process=SERVER_NAME,*]
$AdminControl invoke $jvm dumpThreads
jvm = AdminControl.completeObjectName('type=JVM,process=SERVER_NAME,*')