Sorry to ask questions instead of give answers, but do you really need JBoss
with Tomcat on the servlet machine? You could just run plain Tomcat there.
Cheers
-----Original Message-----
From: Anatoly Akkerman [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 27, 2001 4:48 PM
To: jboss-user mailing list; JBoss-Dev
Subject: [jBoss-Dev] sharing JNDI namespace between 2 instances of JBoss
Hi,
I am trying to deploy an EAR piecewise on 2 separate instances of JBoss:
WAR on one
EJBs on another
In order to do that I've setup
Computer1
JBoss w/o tomcat, EJBs are in the deploy
NamingService running on port XXXX
Computer2
JBoss with EmbeddedTomcat, WAR in the deploy directory
jndi.properties java.naming.provider.url entry is set to Computer1:XXXX
Deployment succeeds and appropriate entries from the jboss-web.xml are
processed and added into java:comp/env space for Computer2 JBoss. (I am
printing out the listing for the whole Context on deployment)
But when the servlets try to resolve the java:comp/env entries for the
beans that were added by JbossWebXmlReader, it throws a NamingException.
No message is provided with the NamingException, the only thing I was able
to extract, is the message from the root cause exception:
"Type code out of range, is 125"
I suspect it has to do with the "java:comp/env" space issues, that these
are local to the VM (?) while the InitialContext that the servlets are
getting, belongs to the NamingService from Computer1.
I am very new to JNDI, please, forgive me if I am not making sense.
-------------------------------------------------------------------------
Anatoly Akkerman
Computer Science Dept.
Courant Institute of Mathematical Sciences, NYU
719 Broadway, #715 Tel: 212 998-3525
New York, NY 10003 Fax: 212 995-4123
-------------------------------------------------------------------------
