• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

HTTP POST works in servlet then stops after a while

 
Peter Odemwingie
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi there,

We have a Java Servlet which makes 100's of 1000's of http posts per day with no problem.

However recently the servlet times out when trying to make these connections, but if the same url is hit directly from the browser on the server there is no problem.

The only way to resolve is to restart the server, which is obviously not ideal.

Any ideas appreciated.
 
William P O'Sullivan
Ranch Hand
Posts: 859
Chrome IBM DB2 Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hmmm,

I wonder if you are exhausting some internal IP setting.

Try doing a netstat command over set intervals and plot the open or fin wait status(es).

WP
 
Jayesh A Lalwani
Rancher
Posts: 2756
32
Eclipse IDE Spring Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
So, you have a serrvlet on Server A that is doing HTTP posts to server B? Where did you run your browser, on Server A or Server B?

There could be 3 issues
a) Server B is throttling connections from Server A. Obviously if you have already tried opening the brower on Server A then this is not the case
b) Server A could have some memory leaks that makes everything run slowly on Server A
c) There are some network contention issues between the 2 servers. You just might be overloading the network. Maybe it was working fine before, and then you made some changes to the network topology that increases contention.
 
Peter Odemwingie
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Jayesh A Lalwani wrote:So, you have a serrvlet on Server A that is doing HTTP posts to server B? Where did you run your browser, on Server A or Server B?

There could be 3 issues
a) Server B is throttling connections from Server A. Obviously if you have already tried opening the brower on Server A then this is not the case
b) Server A could have some memory leaks that makes everything run slowly on Server A
c) There are some network contention issues between the 2 servers. You just might be overloading the network. Maybe it was working fine before, and then you made some changes to the network topology that increases contention.


Hi Jayesh,

Thanks for the reply.

Server B allows and expects posts from our server (Server A).

When the connections start timing out we can't reach Server B from within the Servlet hosted on Server A, but hitting the same url directly from a Web Browser on Server A does not cause a problem which is the strange thing.

And once the whole server is restarted the problem goes away.

If we can still reach Server B via a Web Browser I am wondering if it is more likely to be a Tomcat issue?

Best Regards
 
Peter Odemwingie
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
William P O'Sullivan wrote:Hmmm,

I wonder if you are exhausting some internal IP setting.

Try doing a netstat command over set intervals and plot the open or fin wait status(es).

WP


Hi William,

Thanks will give this a go.

Best Regards
 
Prasad Krishnegowda
Ranch Hand
Posts: 670
4
Eclipse IDE Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Peter Odemwingie wrote:And once the whole server is restarted the problem goes away.

Which Server you restart, server A or server B?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic