[JBoss-user] [JNDI/Naming/Network] - Re: Problems with remote calls from one JBoss to another (4.

Hello, it seems there is a conflict, as I have the same bean exposed over RMI/HTTPS. I've created a new bean instead, and this has solved the problem. Mikael View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3897422#3897422 Reply to the post : http://www.jbo

[JBoss-user] [JNDI/Naming/Network] - Re: Problems with remote calls from one JBoss to another (4.

After examining the network traffic with a firewall, i can see that when instance A tries to connect to B, A tries to connect to port 8443. This port is not open on B, but should be 8083, as this is the RMI codebase port. Regards, Mikael View the original post : http://www.jboss.com/index.htm

[JBoss-user] [JNDI/Naming/Network] - Problems with remote calls from one JBoss to another (4.0.2)

Hello, i've tried to make a remote call from one JBoss instance to another. I guess this is related to this bug http://jira.jboss.com/jira/browse/JBAS-1442. I'm using the standard way of setting up the context: | Properties properties = new Properties(); | properties.put(Context.INITIAL_CO

[JBoss-user] [Messaging, JMS & JBossMQ] - Re: new InitialContext(remote) in servlet returns local jndi

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? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871117#3871117 Reply to the post