Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hazelcast can not match hostnames when wildcards are used in interfaces configs. #2396

Closed
ahmetmircik opened this issue May 6, 2014 · 0 comments

Comments

Projects
None yet
2 participants
@ahmetmircik
Copy link
Member

commented May 6, 2014

Affects all versions of 2.x & 3.x
An example not working configuration is here:

<network> 
   <join> 
       <tcp-ip enabled="true">
              <hostname>host-test</hostname> 
              <hostname>host-test2</hostname> 
       </tcp-ip> 
    </join> 
     <interfaces enabled="true”> 
        <interface>127.0.0.*</interface> 
        <interface>10.0.2.*</interface> 
        <interface>10.10.1.*</interface> 
        <interface>10.0.1.*</interface> 
     </interfaces> 
</network>

@ahmetmircik ahmetmircik added this to the 2.6.9 milestone May 6, 2014

mdogan added a commit to mdogan/hazelcast that referenced this issue May 6, 2014

mdogan added a commit to mdogan/hazelcast that referenced this issue May 6, 2014

@mdogan mdogan closed this in cb521ba May 6, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.