soap connection refused/address already in use errors after server running for
long time
----------------------------------------------------------------------------------------
Key: JRUBY-5757
URL: http://jira.codehaus.org/browse/JRUBY-5757
Project: JRuby
Issue Type: Bug
Affects Versions: JRuby 1.6.1, JRuby 1.5.6
Environment: windows 7, rails 2.3.2,
Reporter: larry erickson
Assignee: Thomas E Enebo
Application start up multiple threads, each thread makes a soap connection.
After a certain amount of time or soap messages, the application starts
throwing soap errors and freezes. The soap errors are different based on which
version of jruby is running. Errors start occuring between 12-14 hours of
application running or between 200-300 thousand soap messages communicated.
Jruby 1.6.1 gives a Address is already In use: no further information error,
Jruby 1.5.6 gives a connection refused error.
Jruby 1.3.0 gives no errors and has ran 40+ hours and 1 million soap messages
without any problems.
These are the only jruby environments I have tried.
So in summary, on the same machine and not changing anything else except what
jruby I am using.
1.3.0 (no errors, seemingly could run forever (or at least 40hrs)).
1.5.6 (connection refused error after 12hrs, repeated at least 15
times)
1.6.1 (Address is already In use: no further information error)
This link
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6213296
describes how repeated socket connect() calls cause BindException in windows.
This may or may not be related to the problem.
I have added the jruby property -Xbacktrace.style=raw and will post the results
of that when the application crashes again in 12 hours.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
