vmdk fails to kick installer

Loaded the vmx file, along with vmdk as hard drive and 40GB file as another hard drive.
Loading process failed. So, went to boot manager > boot options menu, selected efi SCSI Device 1, and started over again.

Webcast replay: Best Practices for Installing WebSphere Application Server V7 Feature Packs

IBM Webcast on "Best Practices for Installing WebSphere Application Server V7 Feature Packs"


http://www-01.ibm.com/support/docview.wss?uid=swg27023316&myns=swgws&mynp=OCSSEQTP&mync=R

Java monitoring tools

There are a few tools you can use to monitor and identify performance inhibitors in your Java™ applications.

vmstat

Provides information about various system resources. It reports statistics on kernel threads in the run queue as well as in the wait queue, memory usage, paging space, disk I/O, interrupts, system calls, context switches, and CPU activity.

iostat

Reports detailed disk I/O information.

topas

Reports CPU, network, disk I/O, Workload Manager and process activity.

tprof

Profiles the application to pinpoint any hot routines or methods, which can be considered performance problems.

ps -mo THREAD

Shows to which CPU a process or thread is bound.

Java profilers [-Xrunhprof, Xrunjpa64]

Determines which routines or methods are the most heavily used.

java -verbose:gc

Checks the impact of garbage collection on your application. It reports total time spent doing garbage collection, average time per garbage collection, average memory collected per garbage collection, and average objects collected per garbage collection.

Here are 10 tools useful for Java application performance troubleshooting.

• jconsole comes together with JDK 1.5 and above. It is a Java Monitoring and Management Console - JMX-compliant graphical tool for monitoring a Java virtual machine. It can monitor both local and remote JVMs.

• VisualVM is a visual tool that integrates several existing JDK software tools and lightweight memory and CPU profiling capabilities. This tool is designed for both production and development time use and further enhances the capability of monitoring and performance analysis for the Java SE platform.

• HeapAnalyzer allows the finding of a possible Java™ heap leak area through its heuristic search engine and analysis of the JavaTM heap dump in Java applications. It analyzes Java heap dumps by parsing the Java heap dump, creating directional graphs, transforming them into directional trees, and executing the heuristic search engine.

• PerfAnal is a GUI-based tool for analyzing the performance of applications on the Java 2 Platform. You can use PerfAnal to identify performance problems in your code and locate code that needs tuning.

• JAMon is a free, simple, high performance, thread safe, Java API that allows developers to easily monitor production applications.

• Eclipse Memory Analyzer is a fast and feature-rich Java heap analyzer that helps you find memory leaks and reduce memory consumption.

• GCViewer is a free open source tool to visualize data produced by the Java VM options -verbose:gc and -Xloggc:<file>. It also calculates garbage collection related performance metrics (throughput, accumulated pauses, longest pause, etc.).

 

WASServiceCmd utility

I faced lot of issues with WebSphere services on Windows 2008 R2 64bit boxes.
WASService adds the WAS Services to Windows services list, but fails to stop/start them.

If I bounce the box, then services are getting started. If I stop them, it is setting the service status as blank. If I start it again, it throws "Windows could not start IBM WebSphere Application Server – servicename on local computer". When checked in the event logs "The IBM WebSphere Application Server V7.0 - CellManager01 service terminated with service-specific error %%134220456." is the message.

 

This is how I have added WAS Services to Windows Services

D:\IBM\WebSphere\AppServer\bin\WASService.exe -add CellManager01 -serverName dmgr -profilePath D:\IBM\WebSphere\AppServer\profiles\Dmgr01 -wasHome D:\IBM\WebSphere\AppServer -logFile D:\IBM\WebSphere\AppServer\profiles\Dmgr01\logs\dmgr\SystemOut.log -logRoot D:\IBM\WebSphere\AppServer\profiles\Dmgr01\logs\dmgr -restart true -startType automatic -stopArgs "-username xxxxxxxxx -password xxxxxxx" –encodeParams

To solve this, one can use WASServiceCmd Utility. This utility is easy to use, grabs all the info you need to pass, creates the service command, executes it.

Here is the technote about WASServiceCmd

http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg21397335

Here is my WASServiceCmd log entry
wasservice.exe -add "CellManager01" -serverName "dmgr" -profilePath "D:\IBM\WebSphere\AppServer\profiles\Dmgr01" -encodeParams -stopArgs "-username xxxxxxxx -password ******** -startType automatic -restart true
wasservice.exe -add "Node01" -serverName "nodeagent" -profilePath "D:\IBM\WebSphere\AppServer\profiles\wlmprime01" -encodeParams -stopArgs "-username xxxxxxx -password ******** -startType automatic -restart true

These services are now, properly working.
 
--
Thanks and Regards
Bhaskar Ramaraju
http://www.linkedin.com/in/ramarajubhaskar

Elevated user privileges

Problem: I have edited a file, say, httpd.conf on Windows 2008 R2 64 bit server. I saved the file and bounced the apache. But, my changes were not in effect. I looked deep into it, then realized that, Windows is storing a copy of httpd.conf on Desktop in VirtualData folder, under this folder, created entire folder structure and stored the file in there.
To avoid this, edit the files or run the commands as an administrator or disable User Access Control (UAC).

Technote from IBM

Running WebSphere Application Server command-line tools might require elevated Microsoft Windows user account privileges

Technote (troubleshooting)   Problem(Abstract) To successfully use some IBM WebSphere Application Server command-line tools, you might need to explicitly elevate Microsoft Windows user account privileges if you are not using the built-in administrator account to run the commands. This action is applicable to the Windows 7, Windows Vista, Windows Server 2008 R2, and Windows Server 2008 operating systems only. If Windows User Account Control (UAC) is disabled on your system, then this document is not applicable.   Cause You must use a Windows user account that has full Administrator account privileges for certain operations on Windows 7, Windows Vista, Windows Server 2008 R2, and Windows Server 2008 operating systems. Commands that involve Windows services or access to the Windows system registry require that type of full authority due to the Windows User Account Control implementation for those two operating systems. For example, if you use a regular administrator group account that is not the built-in Administrator account, then you will likely need to explicitly elevate your user account privileges when you run the launchpad or Profile management tool commands. This action assumes that your operating system is running with the default values for system-wide security policies that are related to the Windows User Account Control.

http://www-01.ibm.com/support/docview.wss?rs=180&context=SSEQTP&q1=Win7_2008_R2&uid=swg21315375&loc=en_US&cs=utf-8&lang=en
--
Thanks and Regards
Bhaskar Ramaraju
http://www.linkedin.com/in/ramarajubhaskar

Proxy Error Bad Gateway

InfoCenter is down.

To understand whats wrong - Proxy error, bad gateway etc, this is a temp state. Upstream server response is broken and so the message.

502 Bad Gateway

The server was acting as a gateway or proxy and received an invalid response from the upstream server.^[2]

503 Service Unavailable

The server is currently unavailable (because it is overloaded or down for maintenance).^[2] Generally, this is a temporary state.

504 Gateway Timeout

The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.^[2]