• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Liutauras Vilda
  • Tim Cooke
  • Jeanne Boyarsky
  • Bear Bibeault
  • Knute Snortum
  • paul wheaton
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Ron McLeod
  • Piet Souris
  • Ganesh Patekar
  • Tim Holloway
  • Carey Brown
  • salvin francis

Weblogic CLOSE_WAIT issue

Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

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.

Then YOU must do the pig's work! Read this tiny ad. READ IT!
professionally read, modify and write PDF files from Java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!