I have a java application running on a single weblogic server instance. HTTP access to the application works only from a few IP addresses of our company, whereas for others the socket goes into the CLOSE_WAIT state. We have not been able to setup a correlation of which IP's work and which do not, but vaguely we have noticed that we face no issues for most machines which are a part of a project VLAN. The network team has established that there is no issue with the network connectivity from any IP address to the server IP address by installing TCP/IP sniffer and tracking the flow of packets between IPs. On investigation we found out that the sockets were getting changed to CLOSE_WAIT state (when the HTTP access failed) and the application simply failed to start. But we have not been able to identify a reason as to why this may be happenning?
If anyone has faced similar issues previously or if you are aware about the cause, then kindly throw some light as to why this may be happening and how this issue can be eliminated. Please help.
Would anybody like some fudge? I made it an hour ago. And it goes well with a tiny ad ...
Devious Experiments for a Truly Passive Greenhouse!