Hi guys,
 
I'm really glad this list is showing renewed signs of life!
 
I pulled the restructured codebase from CVS and created a handful of helper methods for supporting a headless data stream interface (okay, okay, screen scraping...). It's been in production since the first of the year and has run without a hitch on a Sun platform for a couple of months.
 
Recent developments have prompted a move to a Linux environment (suse 9) and now the fun begins...
 
I'm getting an IOException thrown in the readNegotiations method of the tnvt class right after the socket connection is established. The log message says the connection is closed but from browsing the code it appears it is really the connections input stream (bin) that is either closed or simply doesn't have any data.
 
I've written a little test code that simply connects and signs in then disconnects repeatedly. Once the exception occurs, the process is unsuccessful in establishing any more connections. However, I can restart my test app and it will connect successfully for a period of time (typically 50-60 times though I've seen as low as 10) and then quit again.
 
Because of the architecture and use of my application, I need to be able to connect repeatedly through out the day. I suspect this has something to do with the differences in the way Linux is allocating resources - though I've looked at the socket connections using lsof and it appears they are coming and going as expected.
 
I'm sort of at a loss here and am hoping perhaps one of you has some ideas or suggestions.
 
Regards,
Tara
 


Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web

Reply via email to