Le 3/10/12 5:22 AM, Kiran Ayyagari a écrit :
are any of your applications using the same connection in multiple threads?
There are a few cases where you can get such an error. Basically, the
server has to processes a BindRequest for a session, and you may be in
one of those cases :
- you send another BndRequest which collides with the first one (your
srrver must be heavilly loaded)
- there is a SASL negociation pending, and the server receives another
BindRequest message for a Simple authentication (unlikely in your case)
- the server has not yet finished to process the Bind, but the Client
has sent another request without waiting for the BindResponse
I guess that the third case is what you face.
This is a bit problematic, because even if the client should have wait
for the BindResponse, we should stack the incomming requests to process
them once the Bind is done.
I suggest you fill a JIRA, there are some grey areas in the way we
handle such cases.
On Sat, Mar 10, 2012 at 5:25 AM, Spencer Burgoyne<[email protected]> wrote:
My company has decided to use an LDAP server for authentication of internal
applications and we decided to go with Apache Directory Server. I adjusted
one of our applications to use the server for authentication via a JNDIRealm
on Tomcat. As I developed and tested these changes, I would occasionally see
'ERR_732 Cannot process a Request while binding' but it usually only
occurred right after I restarted the server, so I didn't think much of it.
The server is now in use and the issue has been appearing sporadically for
many employees. I have googled like crazy but I cannot find any cause for
this issue that applies to our application. Here is the JNDI Realm that I am
using:
<?xml version="1.0" encoding="UTF-8"?>
<Context reloadable="true">
<Realm className="org.apache.catalina.realm.LdapJdbcRealm"
debug="99"
resourceName="LDAP Auth"
connectionName="xxxx"
connectionPassword="xxxx"
connectionURL="xxxx"
alternateURL="xxxx"
driverName="xxxx"
userPattern="uid={0}, xxxx, xxxx"
dbConnectionName="xxxx"
dbConnectionPassword="xxxx"
dbConnectionURL="xxxx"
userRoleTable="xxxx"
roleNameCol="xxxx"
userTable="xxxx"
userNameCol="xxxx"/>
</Context>
And the authentication does work often so I know these settings, for the
most part, must be correct. Have any other users encountered a similar
issue? Any help would be appreciate, thanks.
Spencer
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
