Hi, Unless you are multi-homing this suggests a problem with your ip configuration. I first saw this problem when somebody had configured their host table something like
127.0.0.1 localhost mydomain.com 192.168.0.1 mydomain.com RMI thought the remote ip address was 127.0.0.1 :-) I've also seen it reported on intranets with a broken dns/dhcp config Requests were being sent to the wrong host. I know some people prefer using the hostname, so JD's suggestion is valid and is less likely to be confused by broken config. Regards, Adrian >From: JD Brennan <[EMAIL PROTECTED]> >To: "'G.L. Grobe'" <[EMAIL PROTECTED]> >CC: [EMAIL PROTECTED] >Subject: RE: [JBoss-user] Can't find SerialContextProvider >Date: Fri, 15 Mar 2002 09:19:29 -0800 > >JBoss 2.4.4 default configuration returns localhost for >all lookups. Modify the jboss.properties file. >There's some commented out stuff at the top. > >I set java.rmi.server.hostname to my hostname and then >could access the server remotely. > >JD > >-----Original Message----- >From: G.L. Grobe [mailto:[EMAIL PROTECTED]] >Sent: Thursday, March 14, 2002 5:50 PM >To: [EMAIL PROTECTED] >Subject: [JBoss-user] Can't find SerialContextProvider > > >I've seen other posts about this topic, but they all suggest adding the >proper jar to the classpath. I've got a client which runs fine locally to >jboss, but now that I'm testing it over on a separate machine, I get the >following. > >I've followed as best I can to the section on 'coding and compiling the >test >client'. > >Any help much appreciated. > >--- jndi.properties --- ># note ... 192.168.0.10 is where my jboss server is running. > >java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory >java.naming.provider.url=jnp://192.168.0.10:1099 >java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces ># Do NOT uncomment this line as it causes in VM calls to go over ># RMI! >#java.naming.provider.url=localhost > >--- I have the following files in my clients classpath --- > >jaas.jar >jboss-client.jar >jboss.jar >jbosssx-client.jar >jnp-client.jar >oswego-concurrent.jar > >--- output --- > >javax.naming.CommunicationException: Can't find SerialContextProvider >at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.jav >a:63) >at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:120 >) >at javax.naming.InitialContext.lookup(InitialContext.java:350) >at com.neuroquest.cais.clients.builder.Builder.createSubscription(Builde >r.java:95) >at com.neuroquest.cais.clients.builder.Builder.main(Builder.java:173) > >--- more info ---------------- > >The client runs fine when it's on the same box as the server, but once >moved >to another box ... there seems to be a jndi problem of some sort. > >On my server it's as follows ... >--- >mybox(ACAIS):~/acais$ java -version >java version "1.3.0" >Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0) >Java HotSpot(TM) Client VM (build 1.3.0, mixed mode) > >And on my client machine ... >--- >C:\TEMP>java -version >java version "1.3.0" >Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-C) >Java HotSpot(TM) Client VM (build 1.3.0-C, mixed mode) > > >_______________________________________________ >JBoss-user mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-user _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
