Scott, Thanks for the response. I thought of that (and probably should have mentioned it in my last post). In any regards when I have just this...
| <attribute name="Properties"> | java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory | java.naming.provider.url=ldap://myldap-server:389/ou=USER,ou=JMS,ou=Services,o=MyCompany%20Name | </attribute> | A start of JBoss via run.sh reveals the following: (a) tcpdump definately shows packets being sent to the ldap server. (I"ve also verified I can access the server anonymously via 'JXplorer' (a Java-based LDAP viewer)) (b) The server/default/log/server.log shows the following: | 2005-04-25 08:51:20,369 DEBUG [org.jboss.system.ServiceController] starting service jboss.jndi:service=ExternalContext,jndiName=external/ldap/jboss | 2005-04-25 08:51:20,369 DEBUG [org.jboss.naming.ExternalContext] Starting jboss.jndi:service=ExternalContext,jndiName=external/ldap/jboss | 2005-04-25 08:51:20,389 DEBUG [org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread] Running | 2005-04-25 08:51:20,389 DEBUG [org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread] Disabled, waiting for notification | 2005-04-25 08:51:20,808 DEBUG [org.jboss.naming.ExternalContext] [EMAIL PROTECTED], env={java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory, java.naming.provider.url=ldap://myldap-server:389/ou=USER,ou=JMS,ou=Services,o=MyCompany%20Name, jnp.disableDiscovery=true, java.naming.ldap.version=3, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces} | 2005-04-25 08:51:20,809 DEBUG [org.jboss.naming.ExternalContext] fullName=external/ldap/jboss | 2005-04-25 08:51:20,810 DEBUG [org.jboss.naming.ExternalContext] parentName=external/ldap | 2005-04-25 08:51:20,816 ERROR [org.jboss.naming.ExternalContext] Starting failed jboss.jndi:service=ExternalContext,jndiName=external/ldap/jboss | javax.naming.ConfigurationException: No valid Context.PROVIDER_URL was found | at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1277) | at org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:868) | ...stack trace continues... | Any idea what make of the "No valid Context.PROVIDER_URL was found"? In the mean time I'll keep searching and post back any further findings. (Just a sec... I noticed something...) Ok, I'm back.... IF I remove my "jnp.disableDiscovery=true" from the jndi.properties I no longer get the Context.PROVIDER_URL issue, but I'm back to the socket time-out. As mentioned I'll keep trying, but any insight/suggestions a JBoss guru may have will be met with showers of praise and thanks :) Regards, Tfsquare View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875282#3875282 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875282 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
