If your problem is only with client unable to talk to the server, don't touch the server-side jndi.properties file. Leave it as commented.
Just uncomment the client side jndi.properties file and when you run the your test client, make sure that the jndi.properties file is in the classpath. BTW, What kind of error did you get anyway? Mitch -----Original Message----- From: Hanson, Matthew [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 12, 2003 12:07 PM To: '[EMAIL PROTECTED]' Subject: RE: [JBoss-user] Run Client Using RMI thanks for the response... there are jndi.properties files in both the client directory and, in our case, $JBOSS_HOME/server/default/conf. (a) here is the property (with comment) from the server dir: # Do NOT uncomment this line as it causes in VM calls to go over # RMI! #java.naming.provider.url=localhost i had originally assumed that i should not uncomment this line, because i was told not to :) :)... hopefully i was just wrong and, as normal, should ignore orders :)... (b) the client properties file java.naming.provider.url property was definitely uncommented before deployment. i modified that property to change it from localhost to my win machine's ip... that hadn't helped. i think you are saying i should uncomment the server property. please let me know which properties file is should modify, ok? if that's all i gotta do, i would be psyched. thanks! matt hanson! -----Original Message----- From: Kim, Yong [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 12, 2003 9:09 AM To: '[EMAIL PROTECTED]' Subject: RE: [JBoss-user] Run Client Using RMI Hi, Matthew. All I had to do was to uncomment the line below in the jndi.properties file and replace the "localhost" with property hostname or IP. Make sure jndi.properties file is in your classpath. #java.naming.provider.url=localhost I have a standalone Java appliation that's sending a JMS message to the queue on the server by looking up the queue using JNDI. I know it works, so... Mitchell -----Original Message----- From: Hanson, Matthew [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 12, 2003 9:24 AM To: '[EMAIL PROTECTED]' Subject: RE: [JBoss-user] Run Client Using RMI Alright, folks... I'm now getting desperate... I know it is possible to connect to a Win NT4.0 machine running jboss-3.0.4_tomcat-4.1.12 from an HP-UX machine. I have not been able to find out how to do it on the forums. I am a little unclear about how the Win NT4.0 IP should be declared on the client machine (jndi.properties?) and what server configuration changes need to occur. I don't wanna flood the user group here, but the forums have me going in every direction. I have seen posts saying to just change jndi.properties on the client to point to the right host. Then I have seen posts saying HTTP invokation is the only way for this to work. Then I see that I may need to use jproxy or SOAP to get this done. I just have a simple client needing to call the server from a different machine. There has to be a source of information that can guide me through the changes needed to every file that is affected by the client move. I'm sure this can include additions/deletions/modifications to xml files to config of both server and client. I'm sure this can include changing the word "localhost" to a real host or IP in one or a great many files. I'm sure this can include changes to source files and xdoclet/jboss tags. The forums and replies to my post only ever address one subset of all of these potential changes. And the coverage of the required change is usually so high level that it amounts to guesswork as to what the exact change entails... Is there no place where I can find out how to accomplish my task? I hope I can get this to work. If anyone can make my situation clear, please help me. Thanks - Matt Hanson Here is my original post: > Hi-- > > OK - Please don't slam me too hard for this mail. I > wanna move my jboss > client from the machine where jboss is installed > (i.e., localhost) to our hp > machine. I just wanna make sure that the test > client can make the call > properly over the network. Someone has surely > answered this question before > - make configuration file changes are required to do > this? > > For what I've read so far, I believe most of the > client changes entail > updating the jndi.properties > 'java.naming.provider.url=localhost' entry to > 'java.naming.provider.url=jnp://somehostname:1099/'. > Are there other > changes that are needed beside this? To the client > only? Both client > and/or server? For localhost, can I simply change > this val to the IP for > the machine where jboss is running? I tried this, > but the app timed out, so > I know I'm still dumb on some of the issues. > > Please help! > > Thanks! > Matt Hanson! -----Original Message----- From: Hanson, Matthew [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 11, 2003 10:41 AM To: '[EMAIL PROTECTED]' Subject: RE: [JBoss-user] Run Client Using RMI hi - adding to my last post... jboss currently is running on an NT4.0 machine, and i am trying to port the client to our hp-ux machine... the communication layer between these types of hardware is very fuzzy to me... i am not ready to move everything over to unix, so i would like to test things very incrementally... even if this configuration seems illogical, is it possible? thanks! -----Original Message----- From: Nicholas [mailto:[EMAIL PROTECTED]] Sent: Monday, February 10, 2003 9:56 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] Run Client Using RMI For remote [and local] connections, I have never used the "decorated" URL you showed in your email. I simply used: java.naming.provider.url=<hostname>:<port> If it is timing out, make sure you can actually ping the server from your client box......:) Also, make sure all the "required stuff" (that is a technical term) is in your client classpath. Lastly, make sure you are infact running the JNDI port on the port you are trying to connect to. Cheers. //Nicholas --- "Hanson, Matthew" <[EMAIL PROTECTED]> wrote: > Hi-- > > OK - Please don't slam me too hard for this mail. I > wanna move my jboss > client from the machine where jboss is installed > (i.e., localhost) to our hp > machine. I just wanna make sure that the test > client can make the call > properly over the network. Someone has surely > answered this question before > - make configuration file changes are required to do > this? > > For what I've read so far, I believe most of the > client changes entail > updating the jndi.properties > 'java.naming.provider.url=localhost' entry to > 'java.naming.provider.url=jnp://somehostname:1099/'. > Are there other > changes that are needed beside this? To the client > only? Both client > and/or server? For localhost, can I simply change > this val to the IP for > the machine where jboss is running? I tried this, > but the app timed out, so > I know I'm still dumb on some of the issues. > > Please help! > > Thanks! > Matt Hanson! > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = > Something 2 See! > http://www.vasoftware.com > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user ===== Nicholas Whitehead Home: (973) 377 9335 Cell: (201) 615 2716 Work: (212) 622 5639 [EMAIL PROTECTED] ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
