Thanks Bongjae. By prefer IPv4, do you mean that if the system had
dual stack it would prefer IPv4 and if the system had only IPv6 it
would still continue to work with IPv6? If yes, I think that would be
fine.
We don't yet have any IPv6-only customer deployments but one can never
tell where Shoal would be used and hopefully the above preference
would be workable under those conditions.
Thanks
Shreedhar
On 03-Jul-2009, at 2:12 AM, Bongjae Chang <carryel_at_korea.com> wrote:
> Hi Shreedhar,
>
> I used the invalid URL format of IPv6.
>
> When I saw the following link,
>
> http://www.ietf.org/rfc/rfc2732.txt
>
> I could know that in URL, the literal address should be enclosed in
> "[" and "]" characters.
>
> For examples,
>
> "tcp://fe80:0:0:0:223:12ff:fe23:d00e%6:4000" is wrong.
>
> "tcp://[fe80:0:0:0:223:12ff:fe23:d00e%6]:4000" is correct.
>
> I fixed the error. :)
>
> In addition, if both IPv6 and IPv4 are supported, IPv4 is preferred.
>
> If your Mac supports IPv4, the branch version will use IPv4's
> address mainly.
>
> Thanks!
>
> --
> Bongjae Chang
>
>
> ----- Original Message -----
> From: Bongjae Chang
> To: dev_at_shoal.dev.java.net
> Sent: Friday, July 03, 2009 9:33 AM
> Subject: Re: [Shoal-Dev] [shoal-grizzly] How do I run the
> rungmsdemo.sh for this provider?
>
> Thanks Shreedhar,
>
> I haven't tested it on IPv6.
>
> I will fix the issue as soon as possible.
>
> Thank you!
>
> --
> Bongjae Chang
>
>
> ----- Original Message -----
> From: Shreedhar Ganapathy
> To: dev_at_shoal.dev.java.net
> Sent: Friday, July 03, 2009 7:51 AM
> Subject: Re: [Shoal-Dev] [shoal-grizzly] How do I run the
> rungmsdemo.sh for this provider?
>
> My Mac has IPv6 enabled and when I kill an instance in a two
> instance group, the remaining member gets the following when doing
> the HW/network failure check during failure suspicion check.
>
> The IPv6 address format or the %6 in the URI is causing the
> issue :
>
> [#|2009-07-02T13:47:02.519-0700|FINE|Shoal|ShoalLogger|
> _ThreadID=16;_ThreadName=FailureVerifier Thread for
> Group:g1;ClassName=HealthMonitor$FailureVerifier;MethodName=verify;|
> FV: Verifying state of s2 state = indoubt|#]
>
> [#|2009-07-02T13:47:02.520-0700|FINE|Shoal|ShoalLogger|
> _ThreadID=16;_ThreadName=FailureVerifier Thread for
> Group:g1;ClassName=SystemAdvertisementImpl;MethodName=getURIs;|
> Exception occurred :
> java.net.URISyntaxException: Malformed escape pair at index 35:
> tcp://fe80:0:0:0:223:12ff:fe23:d00e%6:4000
> at java.net.URI$Parser.fail(URI.java:2809)
> at java.net.URI$Parser.scanEscape(URI.java:2939)
> at java.net.URI$Parser.scan(URI.java:2962)
> at java.net.URI$Parser.parseAuthority(URI.java:3103)
> at java.net.URI$Parser.parseHierarchical(URI.java:3058)
> at java.net.URI$Parser.parse(URI.java:3014)
> at java.net.URI.<init>(URI.java:578)
> at
> com.sun.enterprise.ee.cms.impl.base.SystemAdvertisementImpl.getURIs
> (SystemAdvertisementImpl.java:282)
> at com.sun.enterprise.mgmt.HealthMonitor.isConnected
> (HealthMonitor.java:1423)
> at com.sun.enterprise.mgmt.HealthMonitor$FailureVerifier.verify
> (HealthMonitor.java:1302)
> at com.sun.enterprise.mgmt.HealthMonitor$FailureVerifier.run
> (HealthMonitor.java:1284)
> at java.lang.Thread.run(Thread.java:637)
> |#]
>
> [#|2009-07-02T13:47:02.520-0700|FINE|Shoal|ShoalLogger|
> _ThreadID=16;_ThreadName=FailureVerifier Thread for
> Group:g1;ClassName=SystemAdvertisementImpl;MethodName=getURIs;|
> Exception occurred :
> java.net.URISyntaxException: Malformed escape pair at index 24:
> tcp://fe80:0:0:0:0:0:0:1%1:4000
> at java.net.URI$Parser.fail(URI.java:2809)
> at java.net.URI$Parser.scanEscape(URI.java:2939)
> at java.net.URI$Parser.scan(URI.java:2962)
> at java.net.URI$Parser.parseAuthority(URI.java:3103)
> at java.net.URI$Parser.parseHierarchical(URI.java:3058)
> at java.net.URI$Parser.parse(URI.java:3014)
> at java.net.URI.<init>(URI.java:578)
> at
> com.sun.enterprise.ee.cms.impl.base.SystemAdvertisementImpl.getURIs
> (SystemAdvertisementImpl.java:282)
> at com.sun.enterprise.mgmt.HealthMonitor.isConnected
> (HealthMonitor.java:1423)
> at com.sun.enterprise.mgmt.HealthMonitor$FailureVerifier.verify
> (HealthMonitor.java:1302)
> at com.sun.enterprise.mgmt.HealthMonitor$FailureVerifier.run
> (HealthMonitor.java:1284)
> at java.lang.Thread.run(Thread.java:637)
> |#]
>
>
>
>
> Shreedhar Ganapathy wrote:
>>
>> Okay... my bad.
>> I hand edited the script file in vi and messed up the else block
>> before the java command.
>>
>> Got it to run with -DSHOAL_GROUP_COMMUNICATION_PROVIDER=grizzly
>> and adding the grizzly libraries to the classpath.
>>
>> Looks very zippy at startup.
>>
>>
>>
>> Shreedhar Ganapathy wrote:
>>>
>>>
>>>
>>> Shreedhar Ganapathy wrote:
>>>>
>>>> Hi Bongjae
>>>> I went through past emails on the nice abstraction work you are
>>>> doing to have transport provider abstracted. I was trying to see
>>>> if I could run the rungmsdemo.sh script to try out the Grizzly
>>>> based version.
>>>> I added the -DSHOAL_GROUP_COMMUNICATION_PROVIDE=grizzly JVM
>>>> option to the java command line in the script but I dont seem to
>>>> be able to run it.
>>>>
>>>> The script quits as soon as I launch it.
>>>>
>>>> Also is the property name correct? Should it be
>>>> SHOAL_GROUP_COMMUNICATION_PROVIDER with the R in the end. Should
>>>> grizzly be within quotes?
>>> None of the above work for me btw. Will keep you posted on what I
>>> find out. If you have any ideas meantime, let me know.
>>>>
>>>> Thanks for any insights
>>>> Shreedhar
>