Hi Jitendra,
> * Can you see the output of netstat -a, if it gives any clues(like
> running out of sockets, resources etc)
I ran netstat -a 2 (re-poll every two seconds) but I didn't see anything stand out.
> * You can also play with these standard JDK system properties
> ||http.keepAlive=<boolean>, |http.maxConnections=<int>
I tried:
-Dhttp.keepAlive=false
-Dhttp.keepAlive=true
-Dhttp.maxConnections=1
-Dhttp.maxConnections=10
-Dhttp.keepAlive=false -Dhttp.maxConnections=1
-Dhttp.keepAlive=false -Dhttp.maxConnections=10
-Dhttp.keepAlive=true -Dhttp.maxConnections=1
-Dhttp.keepAlive=true -Dhttp.maxConnections=10
Unfortunately the error still occurs :(
> * There are some more minor fixes to Keep-Alive in 2.1.2(It is for
> doc/lit and body is mapped to void). You can give a try.
Do you have a link for the download?
> * Does this happen when client is running on someother machine(not in
> VMWare environment)
I misspoke. I saw that the machine was running the psuedo-network devices VMWare adds and came to
the wrong conclusion. VMWare is running on the machine, but I'm not running my application on it.
But just to be sure I uninstalled VMWare, but the problem still occurs.
Thanks,
Kirk