java.io.StreamCorruptedException under clustering - not the

[nitesh]

I have a very simple cluster of two nodes running on the same machine. I successfully deployed a HelloWorld Stateless Session Bean on the cluster.

Now when I try to look up the Home reference of my HelloWorld bean, I get the following exception:

javax.naming.CommunicationException: Failed to retrieve stub from server 10.1.3.76:1100 [Root exception is java.io.StreamCorruptedException: unexpected block data]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:248)
at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1294)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1382)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:579)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
at javax.naming.InitialContext.lookup(Unknown Source)
at com.tvworks.example.hello.test.HelloWorldTest.testHello(HelloWorldTest.java:50)

I came across similar exceptions on JBoss Clustering FAQ <http://wiki.jboss.org/wiki/Wiki.jsp?page=ClusteringFAQ> but this is not the case for me. There is nothing deployed in the default and the JBoss instances are not being started in default config. Both nodes are 'all' config and both of them have jbossha.jar in their lib directories.

Any help would be appreciated.

Thanks,

Nitesh

[nitesh]

The properties that I use to set up the InitialContext are:

p.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
p.put(Context.URL_PKG_PREFIXES, "jboss.naming:org.jnp.interfaces")
p.put(Context.PROVIDER_URL, "nvarma-lap:1100");

Another curious thing that I have noticed is that the exception stack references port 1200 whereas I specify port 1100 in the PROVIDER_URL.

javax.naming.CommunicationException: Failed to retrieve stub from server 10.180.0.34:1200 [Root exception is java.io.StreamCorruptedException: unexpected block data]

I haven't been able to overcome this problem. Any help will be much appreciated.

Regards,

Nitesh

[nitesh]

Found the problem. I was using jboss-client.jar on the client's classpath. On replacing this with jbossall-client.jar, the problem disappears.

This needs to go into JBoss Wiki!

Regards,

Nitesh

[belaban]

If you google for this string (in double quotes), the first hit is a page to the FAQ:

http://wiki.jboss.org/wiki/Wiki.jsp?page=ClusteringFAQ

It is at the bottom of the page