On Thu, May 27, 2010 at 3:45 PM, Simon Laws <[email protected]> wrote: > On Thu, May 27, 2010 at 2:17 PM, kelvin goodson <[email protected]> > wrote: >> I think I only see these errors when I am at home, and I haven't got a >> note of the errors here. I had assumed that others were still seeing >> them (maybe if I try the build again when I get home it won't happen). >> I had got into the habit of running mvn -fae. >> >> Kelvin. >> >> On Thu, May 27, 2010 at 1:57 PM, ant elder <[email protected]> wrote: >>> On Thu, May 27, 2010 at 1:43 PM, <[email protected]> wrote: >>>> Author: kelvingoodson >>>> Date: Thu May 27 12:43:27 2010 >>>> New Revision: 948807 >>>> >>>> URL: http://svn.apache.org/viewvc?rev=948807&view=rev >>>> Log: >>>> mention possibility of hazelcast related errors in the build >>>> >>>> Modified: >>>> tuscany/sca-java-2.x/branches/sca-java-2.0-M5/RELEASE_NOTES >>>> >>>> Modified: tuscany/sca-java-2.x/branches/sca-java-2.0-M5/RELEASE_NOTES >>>> URL: >>>> http://svn.apache.org/viewvc/tuscany/sca-java-2.x/branches/sca-java-2.0-M5/RELEASE_NOTES?rev=948807&r1=948806&r2=948807&view=diff >>>> ============================================================================== >>>> --- tuscany/sca-java-2.x/branches/sca-java-2.0-M5/RELEASE_NOTES (original) >>>> +++ tuscany/sca-java-2.x/branches/sca-java-2.0-M5/RELEASE_NOTES Thu May 27 >>>> 12:43:27 2010 >>>> @@ -37,6 +37,17 @@ Overview >>>> >>>> See the CHANGES file for a detailed list of the features in this release. >>>> >>>> +Known Issues >>>> +------------ >>>> + >>>> +If when building using the source distribution of tuscany you see build >>>> errors >>>> +relating to use of hazelcast, this is a known issue which occurs in some >>>> +environments where our use of hazelcast doesn't match up with your network >>>> +configuration. If you see these errors please contact us on the mailing >>>> list >>>> +as described below. You may wish to build using the >>>> +"mvn -fae" >>>> +command, so that the rest of the build completes before it reports the >>>> issue. >>>> + >>>> Support >>>> ------- >>>> >>> >>> Could we just try to fix this instead? I didn't know anyone was still >>> seeing errors, whats the problem, which tests are having errors? >>> >>> ...ant >>> >> > > I get it when I'm using a VPN so it's down to the way we handle > optional NICs. Possibly just an arbitrary order thing, i.e. which one > Hazelcast chooses to use. .When I drop of the VPN it then works. I > haven't got to looking any further so far. If it's going to be tricky > to fix I think we should note that it's a know problem. > > There is a work around that I think Ant previously suggested of > setting the bind property to "*" but it doesn't work consistently for > me. >
Can you do a full build and get a list of all the fails? They should all work if all the failing tests are updated to use the 127.0.0.1 loopback address which should avoid the issue. ...ant
