Connection problems

[sundancer77]

JBoss gurus,

I just downloaded the JBoss 4.0.0 DR2 release a few days back and I was able to start the server, deploy my application without any problems.

When I try to connect to the application from a remote client, I get the following error:

java.rmi.RemoteException: Failure looking up home javax.naming.CommunicationException [Root exception is java.io.InvalidClassException: org.jboss.invocation.remoting.RemotingAdapter; unable to create instance]

I have already had the jndi properties for the client to have the following:
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=jnp://myhostname:1099 java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces

I also have on my server startup the following java startup parameter -Djava.rmi.server.hostname=myhostname

I am not sure why I am seeing the above exceptions. Any ideas/suggestions?

Thanks.

[heismann]

> java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces

Is this a typo?

Under 3.2.1 I'm using the following:

java.naming.factory.url.pkgs=org.jnp.interfaces

[jch888]

in jndi.properties it has the org.jboss.naming package in there for the class org.jboss.naming.HttpContextNaming Factory. That's used for using the JNDI over Http.

[gpower]

We're finding similar problems with 4.0.0DR2. At the moment we're just trying to get a reference to a session bean from a remote (outside VM) client, but with no success so far.
It appears that the default transport mechanism has been changed; after throwing various jars into our client config it's now busy creating an Axis server/taking over the world etc.
It would be great if we could curtail such notions and simply get a reference to the session bean :) - do we need to modify our client jndi.properties file or must we reconfigure the JBoss server (the remoting service or similar)?
Any help would be much appreciated: losing hair fast!