The Return of Rajnikanth

Rajanikanth makes onions cry.

Rajanikanth can delete the Recycling Bin..

Bill Gates lives in constant fear that Rajanikanth' PC will crash..

Ghosts are actually caused by Rajanikanth killing people faster than Death can process them.

Rajanikanth can build a snowman..... out of rain.

Rajanikanth can strangle you with a cordless phone.

Rajanikanth can drown a fish.

Rajanikanth can play the violin....... ...with a piano.

When Rajanikanth enters a room, he doesn't turn the lights on,......... .... he turns the dark off.

Rajanikanth once had a heart attack...... ......... his heart lost.

When Rajanikanth looks in a mirror the mirror shatters, because not even glass is stupid enough to get in between Rajanikanth and Rajanikanth.

Brett Favre can throw a football over 50 yards. Rajanikanth can throw Brett Favre even further.

The last digit of pi is Rajanikanth. He is the end of all things.

Rajanikanth does not know where you live, but he knows where you will die.

Bullets dodge Rajanikanth.

A Handicap parking sign does not signify that this spot is for handicapped people. It is actually in fact a warning, that the spot belongs to Rajanikanth and that you will be handicapped if you park there.

Rajanikanth' calendar goes straight from March 31st to April 2nd, no one fools Rajanikanth.

If you spell Rajanikanth wrong on Google it doesn't say, 'Did you mean Rajanikanth?' It simply replies, 'Run while you still have the chance.'

Rajanikanth can do a wheelie on a unicycle.

Once a cobra bit Rajanikanth' leg. After five days of excruciating pain, the cobra died.

When Rajanikanth gives you the finger, he's telling you how many seconds you have left to live.

Rajanikanth can kill two stones with one bird.

Rajanikanth was once on Celebrity Wheel of Fortune and was the first to spin. The next 29 minutes of the show consisted of everyone standing around awkwardly, waiting for the wheel to stop.

Leading hand sanitizers claim they can kill 99.9 percent of germs. Rajanikanth can kill 100 percent of whatever he wants.

There is no such thing as global warming. Rajanikanth was cold, so he turned the sun up.

Rajanikanth can set ants on fire with a magnifying glass. At night.

Rajanikanth has a deep and abiding respect for human life… unless it gets in his way.

It takes Rajanikanth 20 minutes to watch 60 Minutes.

Rajanikanth once shot down a German fighter plane with his finger, by yelling, 'Bang!'

In an average living room there are 1,242 objects Rajanikanth could use to kill you, including the room itself.

Behind every successful man, there is a woman. Behind every dead man, there is Rajanikanth.

Rajanikanth destroyed the periodic table, because Rajanikanth only recognizes the element of surprise.

Rajanikanth got his drivers license at the age of 16 Seconds.

With the rising cost of gasoline, Rajanikanth is beginning to worry about his drinking habit.

The square root of Rajanikanth is pain. Do not try to square Rajanikanth, the result is death.

When you say 'no one's perfect', Rajanikanth takes this as a personal insult.

History

One day a group of boys
Decided to have a race
They chose to climb a great big tree
And set off at a pace

The rest of their friends gathered
To see the boys at play
They talked about it to themselves
"Will they make it?" "No way!"

They called up to the children
"You'll never make it up that tree"
But the boys just kept on climbing
And said "just watch and you will see"

But the others, how they shouted
And thought the boys tried to ignore
They began to drop out one by one
Another, another and then more

But one boy kept on climbing
And made it to the top of the tree
He never lost faith but believed in himself
And said "this won't defeat me"

The others were quite amazed
At the squirrel at the top of the tree
"How on earth did he do it?" they said
"Well", said one, "he's completely deaf, you see"

So the motto of this poem is
You can reach the top of the tree
Just don't listen to what others say
Just believe in yourself and you'll see......... .

DIfference between NMS and EMS

The telecommunications management network (TMN) provides a framework for achieving interconnectivity and communication across heterogeneous operating systems and telecommunications networks.

TMN describes telecom network management from several viewpoints: a logical or business model, a functional model, and a set of standard interfaces. Each of these is critically important and interdependent.

TMN is the overall management network but a subset of it i.e. NMS deals with a group of devices that can be logically grouped such as the kind of technology it is supporting (WLAN, CDMA, GSM, WIMAX, etc) or it can be vendor specific also. EMS is a subset of NMS where in the focus is upon each device or element of that particular network which is managed by one NMS... which in turn gets managed via TMN.

Another way to look at it is....

TMN gives a holistic overview a birds eye view of the overall managed network... a TMN can be broken down into logical entities as NMS... and each of these network elements or devices which fall under a NMS which can be managed independently needs an EMS to be present.

Pass by value in java not by reference

package gc;

public class Swap
{
int i=10;
String s="hello";
String t="world";
public static void swap(Swap integer)
{
String temp = integer.s;
integer.s=integer.t;
integer.t=temp;
}
public static void main(String[] args){


Swap integer=new Swap();
swap(integer);
add(integer);
System.out.println(integer.i);
System.out.println(integer.s+"=="+integer.t);

}

public static void add(Swap integer)
{
//MInteger integer1=new MInteger();
integer.i=0;;
}

}

Eliminating memory leaks

It is almost impossible to improve the performance of your code if your application is impacted by memory leaks. Memory leaks can be in either Java or native code. In native code, memory leaks are caused by the programmer forgetting to free a memory block. Java memory leaks are often caused by saving an object reference in a class level collection and forgetting to remove it at the proper time. There are also other kinds of problems with managing resources that impact performance, such as not closing JDBC Statements/ResultSets in a finally block (many JDBC drivers store a Statement reference in the Connection object). Fixing memory/resource leaks in the application not only has a great impact on performance but also system stability, as you will consume fewer resources.

There are some great tools in the marketplace that make it easy to find Java memory leaks. There are also tools for finding native memory leaks, but you shouldn’t need them unless your company is writing native code. It should suffice to monitor the memory used at the operating system level over a period of time while the client load test is running. In theory, if the application is repeating the same operations, total process memory should not creep up over time (it should level off). If the total memory of the Java process increases each time the client load test is run, then you probably have a memory leak to track down.

To determine if the memory leak is caused by a Java memory leak, you should monitor the Java memory used. The following code can be used for this purpose in the application:

System.out.println(“Java memory in use = “ + Runtime.getRuntime().totalMemory() –
Runtime.getRuntime().freeMemory());

You would want to view this information after running the client test load. If the Java memory is increasing in proportion to the total process memory increase, then you are probably leaking Java memory. If the Java memory is stabilized but the total process memory is increasing, you are probably leaking native memory. You have to make a judgment call on whether this technique applies to your application. If the application is designed to consume additional memory after each client request, then this technique will not help you determine if you have a memory leak. You will have to use commercially available Java/native memory leak finding tools instead.

Preventing memory leaks

You can prevent memory leaks by watching for some common problems. Collection classes, such as hashtables and vectors, are common places to find the cause of a memory leak. This is particularly true if the class has been declared static and exists for the life of the application.

Another common problem occurs when you register a class as an event listener without bothering to unregister when the class is no longer needed. Also, many times member variables of a class that point to other classes simply need to be set to null at the appropriate time.