REST Client Tool

• REST Client is a Java application to test RESTful webservices.
• It will save the development and testing time.
• It can be used to test variety of HTTP communications with headers.

more information at http://code.google.com/p/rest-client/

Google Search Tricks

Some useful information

http://prezi.com/mohshuoe-qcf/google-search-tricks/

the style of presentation in the above link is really good...

How to connect JProfiler in remote Linux machine

Prerequisite: JProfiler should be installed on local windows and remote linux machine (both machines should have same version of JProfiler)

Please follow the steps to connect the JProfiler from windows to  remote linux box (where server is located)

Step 1:

Before running the remote JBoss, include the below three lines in the run.sh file of the JBoss (Linux machine),

JAVA_OPTS = "$JAVA_OPTS –Xrunjprofiler:port=8849 -Xbootclasspath/a: /u/ofs/profiler /jprofiler/jprofiler7/bin/agent.jar"

LD_LIBRARY_PATH="/u/ofs/profiler/jprofiler/jprofiler7/bin/linux-x86"

export LD_LIBRARY_PATH

For Example -  “/u/ofs/profiler/jprofiler/jprofiler7” is the JProfiler installed location.

The run.sh file is located in the JBoss installed location under bin directory (%JBOSS_HOME%/bin).

Step 2:

Open JProfiler from Start -> All Programs -> JProfiler7 -> JProfiler

   Select ‘Session -> Start Center (Ctrl + O)’ to open JProfiler start center.

Select ‘New Session’ tab and click ‘New Remote Integration’.

Step 3:

Select ‘On a remote computer’ in the profiled application location and select the ‘Platform of the remote computer’.

Step 4:

Select JVM vendor, Version and Mode of the remote JBoss.

Step 5:

Select startup mode based on the requirement.

Step 6:

Enter remote machine address.

 

Step 7:

Specify the JProfiler installed directory location of the remote machine.

 

Step 8:

Select the port for the profiling connection.

Step 9:

Review the information

 Step 10:
Complete the integration

 

Step 11:

Select the Initial profiling settings (Instrumentation/Sampling) based on the requirement.

 

Step 12:

Based on the need, session startup setting can be selected.

• Profiling Settings, Filter settings, Trigger settings, Probe settings can be edited.
• Recording CPU data, recording allocations, and enabling triggers can be configured during the startup.
• Now the JBoss is ready for profiling.

 

Step  13:

The detailed profiling results of the JBoss will be displayed as shown below.

How to diagnose memory leaks in live environment

What will you do when you have the performance issue in production environment? Usually installing any debugging tools in production environment is not allowed.

The best way to go is to take a heap dump and analyze it using some tool.

Now we have another question in the mind, which tool is best to analyze the heap dump.

The following is some of the available free tools in the market.

1. Heap Memory Analyzer from IBM
2. JHAT from Oracle Java 
3. Eclipse Memory Analyzer

My vote is for Eclipse Memory Analyzer due to the following reason

1. Quickly calculate the retained sizes of objects, see who is preventing the Garbage Collector from collecting objects.
2. Automatically run a report to extract leak suspects.

For more information please refer here http://www.eclipse.org/mat//

Balsamiq Mockups - Design Prototypes within 5 minutes

I started using this Balsamiq tool for my sample project. It is easy to design and I have completed my sample prototype within 5 minutes. Even you can design the UI prototype for IPhone also.

The only drawback is it's not free...But

1. you can use the trial version for 7 days

2. you can use the "Web Demo" feature for unlimited days(not allowed to save the project)

3. you can buy the product for just $77.

Please take a look and spend 5 mins of your time. If you feel it is worthy consider it for your projects otherwise leave it...