-
1. Re: problem with auto discovery - help required please
myname Jun 16, 2004 1:46 AM (in response to sreedevik)You might have a chance with that one: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=45361.
Regards
Volker -
2. Re: problem with auto discovery - help required please
sreedevik Jun 16, 2004 3:36 AM (in response to sreedevik)Thank you Volker .. It worked :-))))
I had to start the jboss instance with --host option.
Regards,
Sreedevi. -
3. Re: problem with auto discovery - help required please
fdutra Jun 21, 2004 10:35 AM (in response to sreedevik)I have a similiar problem but on two Linux in cluster with Jboss 3.2.3 .
I try to give the ip address to the Context.PROVIDER_URL properties as "server1:1100,server2:1100", but the problem remain only change the address on the message the failed to connect. By telnet I can connected with the servers and ports.
Using --host not works. I think that the problems is not the bind address(I also try configurate it on the cluster-service.xml).
The log error is
16:28:11,959 DEBUG [RecuperaInterfaz] org.jnp.interfaces.NamingContextFactory
16:28:11,959 DEBUG [RecuperaInterfaz] server2:1100,server1:1100
16:28:11,959 DEBUG [RecuperaInterfaz] org.jboss.naming:org.jnp.interfaces
16:28:11,966 WARN [NamingContext] Failed to connect to server2:1100
javax.naming.CommunicationException: Failed to retrieve stub from server server2:1100 [Root exception is java.io.StreamCorruptedException: unexpected block data]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:209)
Thanks for any help,
sorry for my english,
Fabrizio -
4. Re: problem with auto discovery - help required please
fdutra Jun 21, 2004 11:03 AM (in response to sreedevik)Nope problem
I found that the library jbossall-client.jar
of the client was not updated...
;-)