new InitialContext(remote) in servlet returns local jndi

[justkeys]

Problem:

Looking up a jndi tree of a remote jboss, works from java client, but when doing that from inside a servlet in a local jboss, it returns local jndi tree of local jboss.

Detailed:

In a java client, i lookup context

httpParentJndi.java.naming.factory.initial org.jboss.naming.HttpNamingContextFactory
httpParentJndi.java.naming.provider.url http://192.168.20.11:80/invoker/JNDIFactory
httpParentJndi.java.naming.factory.url.pkgs org.jboss.naming:org.jnp.interfaces;java.protocol.handler.pkgs

In that context, i look for queue/Q, and post a message.

On machine 20.11, i can see the message arriving (because there's a consumer there).

When i do exectly the same client code, from inside a servlet inside a jboss on my client machine, it doesn't work anymore. The queue/Q is looked up in the local jndi of the jboss the client machine (running the servlet)! This results in a naming exception. It simply ignores my jndi context parameters (telling to look for the jndi remotely).

[razor_harm]

Can you post your (servlet) code here?

[narayanrm]

have you looked at here?

http://www.jboss.org/wiki/Wiki.jsp?page=HowDoIConfigureAnMDBToTalkToARemoteQueue

[justkeys]

I changed to normal jndi and jms (without http):

java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=jnp://192.168.20.11:1099
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces

By simply changing these settings, it does work inside the war.

This means something is wrong with my HttpNamingContextFactory, when it is created by a thread owned by a war.

[steez]

We found this problem yesterday with RMI over SSL. When we perform a remote lookup in JBoss, the JNDI tree is returned from the calling JBoss instead of the remote.

What to do?

[adrian.brock]

Moderated: What makes you think you will get any jndi question answered in the JMS forum.
And "steez" needs to "READ THIS FIRST"

It is an FAQ anyway, if you'd even bothered to investigate the FAQ before posting.
/etc/hosts

[m.schiessl]

We exactly have the same problem under windows platform and jboss4.01sp1.

Changes to hosts did not solve our problem.
Did it solve the problem to you ?

Are there further possibilities to address the problem ?

Michael

[justkeys]

Adrian: i don't see which faq entry has anything to do with my question.

I know there are some faq entries about MDB's listening to a remote jboss, but that is not what i am pointing out.

[starksm64]

http://jira.jboss.com/jira/browse/JBAS-1442