Clustering with 3.0.3/4 fails to retrieve stub from server

[dsturze]

Hi,

have been trying to get clustering to work but always get a exception, as below. Does anybody have it working. Saw other peoples posting with similar problems, but did see no solutions. Did they giveup?

javax.naming.CommunicationException: Failed to retrieve stub from server 192.168.0.3:1100 [Root exception is java.io.StreamCorruptedException: unexpected block data]
at de.ovsag.profiler.proxies.ProxyStateless.(ProxyStateless.java:26)

Have simplified the setup as far as possible:

- only one server (linux)
- JBoss 3.0.3 (tried 3.0.4 as well)
- JDK 1.4.1 (tried 1.3.1 as well)
- one stateless and one stateful session bean

Remarks:
- Startup and deployment shows no problems
- JBoss starts in standard ALL "mode"
- jboss.xml is true
- JNDI properties are as given in doc
- application works in DEFAULT "mode" (with modified jboss.xml and JNDI)
- both beans are accessable via a servlet

What is the problem? Routing? How to verify that nothing is blocked? I got a route and everything which even looks like a firewall is disabled (as far as I can tell)...

[slaboure]

Hello,

What is this class:

de.ovsag.profiler.proxies.ProxyStateless

Cheers,


sacha

[dsturze]

Hi,

de.ovsag.profiler.proxies.ProxyStateless is only a client side wrapper for the Stateless Session bean, this basically maps down to:

home=PortableRemoteObject.narrow(initialContext.lookup(jndiName),homeClass);

This is some form of lookup problem in the clustered environment.

JNDI checked via jmx-console is ok, as far as I can tell.

Running the app on the server to eliminate routing issues yields the same error...

[dsturze]

Hi,

the same applies for a windows 2k setup with jboss 3.0.4 and jdk 1.4.1

[slaboure]

What happens if you remove the PortableRemoteObject cast and replace it by a direct cast? If it fails as well, send the simplest EJB + client that exhibit this behaviour.

Cheers,


sacha