How to Manually generate javacores for WAS processes ?

This is the method recommended in situations where the server hangs shortly after startup. It is also recommended when other not work, or when the system is under extremely heavy load.

This method uses an alternative method for starting an application server in a mode which accepts the Ctrl + Break keyboard combination to trigger a javacore. This method requires some preparation steps, and the affected server will need to be restarted. This method has the advantage that generating javacores does not require the additional overhead of using another tool (such as the administrative console or wsadmin tool).

Procedure:

1. Open the command prompt.
   
   
2. Navigate to "bin" subdirectory under the server's profile root (<WAS_HOME>\profiles\<PROFILE_NAME>\bin)
   
   
3. From the "bin" subdirectory, execute the one of the following commands. Choose the command from the list below based on the type of server that the javacore will be generated from.
   
   
   Application Servers
   startServer.bat SERVER_NAME -script
   
   
   Nodeagents
   startNode.bat -script
   
   
   Deployment Managers (DMGR)
   startManager.bat -script
   
   
4. This will generate a script named start_<SERVER_NAME>.bat in the current directory.
   
   
5. Stop the server that requires the javacore.
   
   
6. Using the new script, start the application server (or nodeagent or deployment manager).
   start_ server1 .bat
   
   
7. While the server is running, from the same command prompt window, issue the keyboard combination Ctrl + Break. Output on the screen should immediately display that a javacore is being generated.
   
   
8. Repeat step 7 as many times as required to collect javacores.
   
   
9. Note the location of the javacores and collect them. They will usually be output to the current directory or the profile root.

10. The server can be stopped either by issuing a stopServer.bat command, or terminated immediately with a keyboard combination Ctrl + C.

Hope this post will help for your environment.

Related Post:

• Manually generating Heapdump.
• Enable Automated Heap dump generation
• Generating Heapdump, javacore and coredump by using WAS console.
  
  

“Effort only fully releases its reward after a person refuses to quit.”

Regards,

Akhilesh B. Humbe

Generating Heapdump, javacore and coredump by using WAS console.

It is much more easy to generate heapdump, coredump and javacores with WAS v8.0 and v8.5

You can produce javacores (and heapdumps and coredumps) from the admin console by following the steps below, referenced in the Information Center article Collecting Java dumps and core files using the administrative console.

Procedure:

1. Navigate to Troubleshooting > Java dumps and cores
2. Select the server(s) to collect dumps from
3. Click on Java Core, System Dump, or Heap Dump to produce the specified file.
4. Navigate to "bin" subdirectory under the server's profile root and collect the dump file.

Related Post:

• Manually generating javacores.
• Manually generating Heapdump.
• Enable Automated Heap dump generation.

“Effort only fully releases its reward after a person refuses to quit.”

Regards,

Akhilesh B. Humbe

WebSphere Application Server V8.5 Fix Pack Installation

Hi all,

Here we are going to discuss the scenario where I installed the fix pack_2 on Websphere Application server v8.5. For Installation we are using Installation manager instated of Update Installer. Installation manager is much simpler than Update Installer which was we used for v7.

Prerequisites:

1. Install IBM Installation Manager.
2. Install Websphere Application Server v8.5

Procedure:

1. To install Fix Pack 8.5.0.x using a local repository, download the respective .zip files for your respective products
   
   
   Note: If part1 and part2 .zip files exist, unzip the part1 and part2 .zip files to the same folder on your local machine. Both .zip files are required for installation of the fix pack. When unzipping part2, the Windows operating system might warn you that a directory with the same name already exists. Allow the tool to merge the directories; the tool does not overwrite any files.
   
   
2. Then point Installation Manager to the repository.xml file on your local machine. To add the repository:
   Start Installation Manager and in the top menu, click File > Preferences.

3. Select Repositories. Click Add Repository.
   Enter the path to the repository.xml file in the location containing the repository files and click ok

Note: Before Starting Installation  Stop all WebSphere Application Server and IBM HTTP Server processes and backup the configuration files 

4. On Installation Manager Home Screen Click on Update Logo.

5. In Update Packages screen it will list you the Package you Install. Check the package and click on Next.

6. Accept the terms in license agreement and click Next. Then on successive screen check the dependencies and Installation Directory, Shared Resource Directory and click on Update.

7. After successful Update you will get the following Screen showing updated version of your Environment click Finish.

Hope this will help you to Install the latest fix pack using Installation Manager in your environment. And follow the same steps to update the supplements (Web Server Plugins/JDK ) also.

Related Topic

• Installing fix packs for WebSphere Application Server V7.0

“Effort only fully releases its reward after a person refuses to quit.”

Regards,

Akhilesh B. Humbe