[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Regarding Octet String JDBC LDAP Bridge

To get some idea of the problem, I looked into the sources, especially into 'com.octetstring.jndi.JndiLdapConnection.java'. To my understanding there is a bug in method 'public boolean isClosed()'.

This method is called by the JndiLdapConnection()-constructor after having created an 'InitialDirContext' to check the context.
isClosed executes 'con.lookup(baseDN)', instead of 'con.lookup("")', which leads to a lookup of 'ldap://host:port/baseDN,baseDN' which fails if 'baseDN!=null'. Perhaps Marc Boorshtein would like to comment on that observation.

Another answer to this thread by C. Rahul mentions a workaround: create the connection with an empty baseDN. Even my 'INSERT INTO' works like that.

Prajakta Kalekar wrote: 
Yes, I am faced with the exact same problem.
Prajakta Kalekar.

-----Original Message-----
From: owner-openldap-software@OpenLDAP.org
[mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Clemens Helf
Sent: Wednesday, September 24, 2003 2:10 PM
To: openldap-software@OpenLDAP.org
Subject: Re: Regarding Octet String JDBC LDAP Bridge


I am experiencing the same problem with the same stack trace.

 From the stack trace, I concluded, that no query has been issued yet,
so there can be no overlap between a query and the connection. To verify
my point, I removed the query from the source code and the same
exception is thrown.

Despite the exception, the code continues to operate, so the exception
output is probably generated within a catch clause. I could successfully
execute a SELECT query despite the exception, but I was not able to
execute an INSERT INTO query.

Clemens Helf

Marc Boorshtein wrote:

This generally means that the base of the connection and the base of the
query overlap, for example when search o=People,c=us the connection
could be at c=us and the search base should be ou=People.

Marc Boorshtein

On Tue, 2003-09-16 at 01:13, Prajakta Kalekar wrote:


Hi,
	I am using Octet String's JDBC LDAP Driver for accessing iPlanet
Directory Server data.

After connection has been established, I get the following error:

javax.naming.NameNotFoundException: [LDAP: error code 32 - No Such 

Object];

remaining name 'o=enlistautomatedtesting.com'
	at com.sun.jndi.ldap.LdapCtx.mapErrorCode(Unknown Source)
	at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
	at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
	at com.sun.jndi.ldap.LdapCtx.c_lookup(Unknown Source)
	at com.sun.jndi.toolkit.ctx.ComponentContext.p_lookup(Unknown
Source)
	at com.sun.jndi.toolkit.ctx.PartialCompositeContext.lookup(Unknown
Source)
	at com.sun.jndi.toolkit.ctx.PartialCompositeContext.lookup(Unknown
Source)
	at javax.naming.InitialContext.lookup(Unknown Source)
	at
com.octetstring.jdbcLdap.jndi.JndiLdapConnection.isClosed(JndiLdapConnecti


on

.java:270)
	at
com.octetstring.jdbcLdap.jndi.JndiLdapConnection.<init>(JndiLdapConnection


.j

ava:241)
	at
com.octetstring.jdbcLdap.sql.JdbcLdapDriver.connect(JdbcLdapDriver.java:75


)

	at java.sql.DriverManager.getConnection(Unknown Source)
	at java.sql.DriverManager.getConnection(Unknown Source)
	at octetString.Connect.main(Connect.java:38)

	What can I do to overcome this problem? I require a solution to this
problem urgently. Any pointers will be extremely valuable.
Thank you,
Prajakta Kalekar.






--
Dr.-Ing. Clemens Helf           InformationsSysteme & Web-Anwendungen
Rechenzentrum
Universitaet Stuttgart          Tel:  ++49-711-685 5812
Allmandring 30                  Fax:  ++49-711-678 7626
D-70550 Stuttgart