On Mon, Mar 29, 2010 at 5:17 AM, Luciano Resende <[email protected]> wrote: > While trying to build latest 2.x modules, I'm getting the following > output from Hazelcast binding test cases... it seems that it keeps > re-trying... are others seeing this issue ? > > Mar 28, 2010 9:05:26 PM > org.apache.tuscany.sca.node.impl.NodeFactoryImpl loadContributions > INFO: Loading contribution: > file:/Users/lresende/opensource/apache/tuscany/java-sca-2.x/modules/binding-hazelcast-runtime/target/test-classes/ > Mar 28, 2010 9:05:28 PM > org.apache.tuscany.sca.endpoint.hazelcast.HazelcastEndpointRegistry > addEndpoint > INFO: Add endpoint - (@1162992854)Endpoint: URI = > TestService#service-binding(TestService/TestService) > Mar 28, 2010 9:05:28 PM org.apache.tuscany.sca.node.impl.NodeImpl start > INFO: Starting node: http://tuscany.apache.org/sca/1.1/nodes/default1 > domain: HazelcastBindingTestCase > Mar 28, 2010 9:05:28 PM com.hazelcast.system > INFO: [HazelcastBindingTestCase] Hazelcast 1.8.1 (20100304) starting > at Address[9.12.225.202:14821] > Mar 28, 2010 9:05:28 PM com.hazelcast.system > INFO: [HazelcastBindingTestCase] Copyright (C) 2008-2010 Hazelcast.com > Mar 28, 2010 9:05:38 PM com.hazelcast.impl.Node > WARNING: [HazelcastBindingTestCase] > =========================== > Couldn't connect to discovered master! tryCount: 22 > masterAddress: Address[9.12.225.202:14820] > connection: null=========================== > > Mar 28, 2010 9:05:49 PM com.hazelcast.impl.Node > WARNING: [HazelcastBindingTestCase] > =========================== > Couldn't connect to discovered master! tryCount: 22 > masterAddress: Address[9.12.225.202:14820] > connection: null=========================== > > ..... > > BTW, this is in a MacOS environment with java 1.6.0_17. >
Its working ok for me locally and the Hudson build is passing too, there've also not been any changes around that area for a while now either, has this never worked for you or is it a new failure? Its interesting that its using the IP address 9.12.225.202 so it could be some network issue, can you recreate it running just one of the tests we can trying telling it to use 127.0.0.1. ...ant
