Return-Path: 
 <dev-return-40550-apmail-directory-dev-archive=directory.apache.org@directory.apache.org>
X-Original-To: apmail-directory-dev-archive@www.apache.org
Delivered-To: apmail-directory-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 7988D9979
	for <apmail-directory-dev-archive@www.apache.org>;
 Sat, 10 Mar 2012 01:30:08 +0000 (UTC)
Received: (qmail 70842 invoked by uid 500); 10 Mar 2012 01:30:08 -0000
Delivered-To: apmail-directory-dev-archive@directory.apache.org
Received: (qmail 70737 invoked by uid 500); 10 Mar 2012 01:30:05 -0000
Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@directory.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@directory.apache.org>
List-Post: <mailto:dev@directory.apache.org>
List-Id: <dev.directory.apache.org>
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Delivered-To: mailing list dev@directory.apache.org
Delivered-To: moderator for dev@directory.apache.org
Received: (qmail 29135 invoked by uid 99); 9 Mar 2012 23:56:06 -0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of sburgoyne@part.net designates
 74.114.134.44 as permitted sender)
X-Virus-Scanned: Debian amavisd-new at part.net
Message-ID: <4F5A9886.3000704@part.net>
Date: Fri, 09 Mar 2012 16:55:50 -0700
From: Spencer Burgoyne <sburgoyne@part.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: dev@directory.apache.org
Subject: ERR_732
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

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