[JBoss-dev] JNDI Problem

2001-09-12 Thread Andreas Schaefer

Hi Geeks

I tried to register the following EJB at the JNDI server
ejb/jmx/ejb/adaptor
and it caused an
AlreadyBoundException; remaining name 'ejb'
on J2eeDeployer.startModules.

This works fine with JBoss 2.4 on the same box.

Andy ideas ?

Andy


___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] JNDI - Problem

2001-09-10 Thread Jason Dillon

What is trying to connect to 127.0.0.2 ?  Why is any machine configured to
use 127.0.0.2 as its ip addr?

--jason


On Mon, 10 Sep 2001, Andreas Schaefer wrote:

 Hi Geeks

 Maybe it is just me but I have a problem to access
 JBoss JNDI naming service from Windows to an
 Linux box but vice versa is working fine.
 Environment:
 - SuSE Linux 7.1, Kernel 2.4, IBM Java 2, JNDI naming bound to 1099,
   JBoss 2.4 with Jetty, EJB successfully deployed
 -Windows 2000, Java Version 1.3.1 and 1.4, Java application trying to access
   the deployed EJB on the remote server

 Any ideas ? - Andy

 That is the stack trace:
 JNDI Context properties:
 {java.naming.factory.initial=org.jnp.interfaces.NamingC
 ontextFactory, java.naming.provider.url=mpg-dev-2:1099,
 java.naming.factory.url.
 pkgs=org.jboss.naming:org.jnp.interfaces}
 javax.naming.CommunicationException.  Root exception is
 java.rmi.ConnectExceptio
 n: Connection refused to host: 127.0.0.2; nested exception is:
 java.net.ConnectException: Connection refused: connect
 at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)
 at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
 at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
 at sun.rmi.server.UnicastRef.invoke(Unknown Source)
 at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
 at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:349)
 at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:333)
 at javax.naming.InitialContext.lookup(Unknown Source)
 at
 org.jboss.connector.ejb.EJBConnector.getAdaptorBean(EJBConnector.java
 :177)
 at
 org.jboss.connector.ejb.EJBConnector.init(EJBConnector.java:127)
 at
 org.jboss.connector.ejb.EJBConnector.init(EJBConnector.java:113)
 at test.jboss.jmx.TestClient.init(TestClient.java:80)
 at test.jboss.jmx.TestClient$1.run(TestClient.java:62)
 at java.security.AccessController.doPrivileged(Native Method)
 at test.jboss.jmx.TestClient.main(TestClient.java:59)
 Caused by: java.net.ConnectException: Connection refused: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(Unknown Source)
 at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
 at java.net.PlainSocketImpl.connect(Unknown Source)
 at java.net.Socket.connect(Unknown Source)
 at java.net.Socket.connect(Unknown Source)
 at java.net.Socket.init(Unknown Source)
 at java.net.Socket.init(Unknown Source)
 at
 sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(Unknown S
 ource)
 at
 sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(Unknown S
 ource)
 ... 15 more


 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development



___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] JNDI - Problem

2001-09-10 Thread Andreas Schaefer

Good question, I have no idea.

Strange is that local lookups from the Linux server are
working fine, too. Only when W2K tries to make the
lookup it fails this way. I will try to make the lookup
from another Linux box.

Andy

- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 10, 2001 5:31 PM
Subject: Re: [JBoss-dev] JNDI - Problem


 What is trying to connect to 127.0.0.2 ?  Why is any machine configured to
 use 127.0.0.2 as its ip addr?

 --jason



___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development