On Dec 19, 2006, at 11:44 AM, Mehul Pattni wrote:
Hi,
I'm having major performance issues during heavy load to the
system. I'm not getting out of memory but getting the famous
java.net.SocketException: Broken pipe
That is not a problem. That is a symptom of an application that is
too slow for the load it is under. Memory starvation can cause that,
as can about 10,000 other things.
These are my additional arguments in java monitor
maxHeapSize=100000
WO 4.5?
-WODirectConnectEnabled false
Here is what top reports. Any help would be greatly appreciated.
The >> and >>> is a symptom of an application that is _really_ too
slow for the load it is under. :-)
You have two choices:
1. Optimize your application
2. Run more instances and / or buy more hardware
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
