....
On 21 April 2011 06:10, helcio silva <[email protected]> wrote:
> Hello to everybody.
>
> I am developing a distributed systems using the transactional
> mechanisms provided by River. For simplicity, I've tested all its
> componentes in a same machine first, and they worked. However, I am
> not having a happy when I distributed them on different machines -
> obviously, that's the way they should work...
>
> When my client try to fetch a proxy for its service, I have the
> following message:
>
> --> obtaining a proxy to service...java.rmi.ConnectException:
> connection refused or timed out to
> BasicObjectEndpoint[0b410d49-68c0-48dc-8ca1-a823493965d8,TcpEndpoint[127.0.1.1:53632]];
> nested exception is:
> (and a lot of exceptions are thrown away...)
>
We could do with seeing those exceptions please - or at least the
first few. In particular the exception above doesn't tell me which
piece of code is emitting this exception so I cannot make any
diagnosis.
> My opinion is that the client is trying to connect to its own
> machine, because the trace shows the '127.0.1.1' address. Am I
> correct? No? So, what is the point? I've used the current IP addresses
> when I was making all configuration files - I've not used hostnames on
> making those files.
Clearly you've missed something. Not uncommon given the typical Jini
config, nevertheless we need the exception traces above to help you.
>
> Another weird message (to me, at least) is provided by reggie, when
> it is started up:
>
> INFO: started reggie: 845b79d8-e188-4f2c-8400-21ce26c89a46, [public],
> ConstrainablelLookupLocator[[jini://xavante/], [null]]
>
> Why the hostname is shown on that message? Why the current
> machine's IP address is not shown, instead of its hostname?
>
I would strongly suspect that is because you haven't specified
something appropriate for this Reggie config item:
• unicastDiscoveryHost
Type: String
Default: InetAddress.getLocalHost().getHostName()
Description: Specifies the host name for unicast discovery, which
is advertised in multicast announcements and (protocol 2) unicast
discovery responses. This entry is obtained at service start and
restart.
> May you provide any glue, fellows? Thanks in advance.
>
> Wagner.
>
