Re: [JBoss-user] Re: JBoss-user -- confirmation of subscription -- request 343542
Connection refused to host: 127.0.0.1 Java is not getting the instruction to connect to a remote host - it is still trying to connect to JBoss locally. Where are you providing the remote host ip address? I put it in jndi.properties and everything works fine. - Original Message - From: Kobi Schecider [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, May 13, 2001 2:51 AM Subject: [JBoss-user] Re: JBoss-user -- confirmation of subscription -- request 343542 Hi everyone, I am new to JBoss and have been trying to get the interestclient example running (the client and the EBJ running on different machines) without success. This example is the one found in chapter 1 of JBoss' online documentation. I setup the software according to the tutorial and the FAQ (there is one entry that mentions how to run a client application remotely.) But I am consistantly getting exceptions. The following is my configuration: RedHat Linux 6.2 Sun JDK 1.3 standard edition, (jndi, rmiregistry, providerutil located in jdk1.3/jre/lib/ext) JBoss 2.2.1 Since I don't have a DSN server, I use the IP address of the server running JBoss for java.naming.provider.url. My machines, relying solely on hosts files, are on a home network. My client code is kept inside a directory together the EBJ jar and a copy of everything inside JBoss-2.2.1/client. The following is how I invoke the client and the results I got: java -cp all the jar files in the client directory InterestClient Got context javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is: java.net.ConnectException: Connection refused: no further information] My CLASSPATH is empty. The same configuration (with the java.naming.provider.url set to localhost) works perfectly when both client and JBoss server are running on the same machine. I experienced the same problem with JONAS. Could this be caused by an incorrect JDK configuration? Basically, the examples (both JBoss and JONAS) work fine as long as both the client and the EJB server are on the same machine. I would greatly appreciate if anyone can shed some light on this. Thanks in advance. Kobi _ Get your FREE download of MSN Explorer at http://explorer.msn.com ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Re: JBoss-user -- confirmation of subscription -- request 343542
Hi everyone, I am new to JBoss and have been trying to get the interestclient example running (the client and the EBJ running on different machines) without success. This example is the one found in chapter 1 of JBoss' online documentation. I setup the software according to the tutorial and the FAQ (there is one entry that mentions how to run a client application remotely.) But I am consistantly getting exceptions. The following is my configuration: RedHat Linux 6.2 Sun JDK 1.3 standard edition, (jndi, rmiregistry, providerutil located in jdk1.3/jre/lib/ext) JBoss 2.2.1 Since I don't have a DSN server, I use the IP address of the server running JBoss for java.naming.provider.url. My machines, relying solely on hosts files, are on a home network. My client code is kept inside a directory together the EBJ jar and a copy of everything inside JBoss-2.2.1/client. The following is how I invoke the client and the results I got: java -cp all the jar files in the client directory InterestClient Got context javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is: java.net.ConnectException: Connection refused: no further information] My CLASSPATH is empty. The same configuration (with the java.naming.provider.url set to localhost) works perfectly when both client and JBoss server are running on the same machine. I experienced the same problem with JONAS. Could this be caused by an incorrect JDK configuration? Basically, the examples (both JBoss and JONAS) work fine as long as both the client and the EJB server are on the same machine. I would greatly appreciate if anyone can shed some light on this. Thanks in advance. Kobi _ Get your FREE download of MSN Explorer at http://explorer.msn.com ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Re: JBoss-user -- confirmation of subscription --request 343542
The client is not finding the RMI Registry Server because it assumes it is running on the same machine (127.0.0.1). You should be able to fix this by invoking the client with an explicit declaration of the hostname or IP address of the machine on which the RMI Registry Server is actually running, like this (all on one line): java -Djava.rmi.server.hostname=xxx.xxx.xxx.xxx -cp all the jar files in the client directory InterestClient where xxx.xxx.xxx.xxx is the IP address of the machine which hosts the RMI Registry Server in dotted-quad notation. Where the RMI Registry Server is actually running, by default it will install a TCP listener on port 1099. You should be able to see it: $ netstat -tan | grep 1099 tcp0 0 0.0.0.0:10990.0.0.0:* LISTEN This is actually a configurable system property; see: http://java.sun.com/products/jdk/1.2/docs/guide/rmi/faq.html#nethostname http://java.sun.com/j2se/1.3/docs/guide/rmi/faq.html#nethostname -- Mike On 2001-05-13 at 06:51 -, Kobi Schecider wrote: I am new to JBoss and have been trying to get the interestclient example running (the client and the EBJ running on different machines) without * * * java -cp all the jar files in the client directory InterestClient Got context javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is: java.net.ConnectException: Connection refused: no further information] My CLASSPATH is empty. The same configuration (with the java.naming.provider.url set to localhost) works perfectly when both client and JBoss server are running on the same machine. ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Re: JBoss-user -- confirmation of subscription -- request 343542
Hi Michael, Thanks for your help. I read the following web page as recommended: http://java.sun.com/j2se/1.3/docs/guide/rmi/faq.html#domain When I specify the java.rmi.server.hostname on the server side. Both jonas and jboss work. Thanks a lot, I really appreciate your help. Kobi From: Michael Bilow [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] Re: JBoss-user -- confirmation of subscription -- request 343542 Date: Sun, 13 May 2001 14:00:49 -0400 (EDT) The client is not finding the RMI Registry Server because it assumes it is running on the same machine (127.0.0.1). You should be able to fix this by invoking the client with an explicit declaration of the hostname or IP address of the machine on which the RMI Registry Server is actually running, like this (all on one line): java -Djava.rmi.server.hostname=xxx.xxx.xxx.xxx -cp all the jar files in the client directory InterestClient where xxx.xxx.xxx.xxx is the IP address of the machine which hosts the RMI Registry Server in dotted-quad notation. Where the RMI Registry Server is actually running, by default it will install a TCP listener on port 1099. You should be able to see it: $ netstat -tan | grep 1099 tcp0 0 0.0.0.0:10990.0.0.0:* LISTEN This is actually a configurable system property; see: http://java.sun.com/products/jdk/1.2/docs/guide/rmi/faq.html#nethostname http://java.sun.com/j2se/1.3/docs/guide/rmi/faq.html#nethostname -- Mike On 2001-05-13 at 06:51 -, Kobi Schecider wrote: I am new to JBoss and have been trying to get the interestclient example running (the client and the EBJ running on different machines) without * * * java -cp all the jar files in the client directory InterestClient Got context javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is: java.net.ConnectException: Connection refused: no further information] My CLASSPATH is empty. The same configuration (with the java.naming.provider.url set to localhost) works perfectly when both client and JBoss server are running on the same machine. ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user _ Get your FREE download of MSN Explorer at http://explorer.msn.com ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
