jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Serge Huber <shub...@jahia.com>
Subject Re: [VOTE] Release Apache Jackrabbit 2.2.4
Date Mon, 14 Feb 2011 09:42:33 GMT

Thank you very much for your detailed answer, I did indeed have something strange in my etc/hosts
file but once removed it didn't change anything.

Here is the information you requested : 

localhost:h2 loom$ cat /etc/hosts
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1	localhost
255.255.255.255	broadcasthost
::1             localhost 
fe80::1%lo0	localhost

./build.sh testNetwork 

localhost:localhost/10.X.37.XXX
  localhost/10.X.37.XXX
  localhost/10.X.129.2
  localhost/10.X.55.2
  localhost/192.168.74.1
  localhost/192.168.223.1
  localhost/fe80:0:0:0:225:4bff:fea6:8410%4
  localhost/fe80:0:0:0:21c:42ff:fe00:0%7
  localhost/fe80:0:0:0:21c:42ff:fe00:1%8
getLocalHost:localhost/127.0.0.1
  /127.0.0.1
byName:/127.0.0.1
ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=59901]
server accepting
client:/127.0.0.1:59901
server accepted:Socket[addr=/127.0.0.1,port=59902,localport=59901]
client:Socket[addr=/127.0.0.1,port=59901,localport=59902]
server read:123
client read:234
done
Done in 1430 ms
server closing
server done

I have VMWare and ShareTool installed, which are probably why all these interfaces are present.
I also obscured some adresses just to be on the same side :) 

I would prefer not to disable the test case, but rather improve it so that it handles this
configuration.

cheers,
  Serge... 

On 14 févr. 2011, at 09:48, Thomas Mueller wrote:

> Hi,
> 
>> Remote connections to this server are not allowed, see -tcpAllowOthers
>> [90117-149]
> 
> This looks more like a network problem with the H2 database than a problem
> with Jackrabbit. It might be a network configuration problem, or another
> service is already running on the ports 9001 or 9002. This test case
> starts two H2 servers on port 9001 and 9002, and then tries to connect to
> them over the local IP address (not localhost). To find out if it's a
> network config problem, could you check your /etc/hosts file for weird
> entries? I saw similar problems before, but I don't know the root cause.
> One option, of course, is to disable this test case, but that would be a
> bit sad, because it's the only clustering test case. To find out if it's
> really a network config problem, please download the H2 database
> (h2database.com), and run "./build.sh testNetwork" and send me the result
> (only the last part; the system properties are not relevant). See below
> for what I get on my machine (Mac OS X as well). It might be possible to
> work around the problem by setting the system property "h2.bindAddress" to
> "localhost" (but I didn't actually test this).
> 
> cat /etc/hosts
> 
> 127.0.0.1 localhost
> 255.255.255.255 broadcasthost
> ::1             localhost
> fe80::1%lo0 localhost
> 
> 
> 
> ./build.sh testNetwork
> 
> localhost:localhost/127.0.0.1
>  localhost/127.0.0.1
>  localhost/0:0:0:0:0:0:0:1
>  localhost/fe80:0:0:0:0:0:0:1%1
> getLocalHost:Thomas-Muellers-MacBook-Pro.local/10.131.197.10
>  /10.131.197.10
> byName:/10.131.197.10
> ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=63643]
> server accepting
> client:/10.131.197.10:63643
> server accepted:Socket[addr=/10.131.197.10,port=63644,localport=63643]
> client:Socket[addr=/10.131.197.10,port=63643,localport=63644]
> server read:123
> client read:234
> server closing
> server done
> done
> Done in 1742 ms
> 
> 
> Regards,
> Thomas
> 


Mime
View raw message