External JNDI yields
quaxi Mar 2, 2006 5:55 AMHi,
I tried to configure an external JNDI store (Tibco EMS to lookup the Queues stored there) as presented in the JBOSS documentation, where I found an example on how to attach an LDAP server to JBOSS.
I changed it to
<mbean code="org.jboss.naming.ExternalContext" name="jboss.jndi:service=ExternalContext,jndiName=external/tibco"> <attribute name="JndiName">external/tibco</attribute> <attribute name="Properties"> java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory java.naming.provider.url=tibjmsnaming://localhost:7222 </attribute> <attribute name="InitialContext">javax.naming.InitialContext</attribute> <attribute name="RemoteAccess">true</attribute> </mbean>
(in the conf/jboss-service.xml file)
I got connection timeout exception which I resolved with the information found in previous post in ths forum by setting
jnp.disableDiscovery=true
in conf/jndi.properties
But now I get this Error:
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.jndi:service=ExternalContext,jndiName=external/tibco State: FAILED Reason: javax.naming.ConfigurationException: No valid Context.PROVIDER_URL was found
The jar with the needed classes are in the server/lib directory.
I also found that this was a problem in the previously mentioned thread but unfortunatley no solution was posted there.
run.bat --version shows this:
=============================================================================== . JBoss Bootstrap Environment . JBOSS_HOME: C:\jboss-4.0.3SP1\bin\\.. . JAVA: c:\jdk1.5.0_03\bin\java . JAVA_OPTS: -Dprogram.name=run.bat -Xms128m -Xmx512m . CLASSPATH: c:\jdk1.5.0_03\lib\tools.jar;D:\downloads\jboss-4.0.3SP1\jboss-4.0. 3SP1\bin\\run.jar . =============================================================================== . JBoss 4.0.3SP1 (build: CVSTag=JBoss_4_0_3_SP1 date=200510231054)
I am sure this must be a very silly config error somewhere,
thanks in advance for any help!
Martin