tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 52636] JNDIRealm fails with CommunicationException and SocketTimeoutException
Date Fri, 10 Feb 2012 10:24:29 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=52636

Colin <colin.schaefer@beeline-group.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |

--- Comment #2 from Colin <colin.schaefer@beeline-group.com> 2012-02-10 10:24:29 UTC
---
Hi Konstantin,

our AD is serving 50+ servers fine without any timeouts and errors (before and
after the update). The tomcat is the only system throwing errors after the
update.

The configuration works fine, because after a restart of the tomcat, login is
possible for a short while obviously until the timeout occurs (as stated in the
other issues). As the logs state the "PartialNamingException" is not the root
exception, so there is no configuration error. The root Exceptions are
Communication and SocketTimeout.

I will not change the core timeouts and settings of my central directory
service for a single system not handling a socket timeout.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message