[jira] [Updated] (DISPATCH-1079) Setting socketAddressFamily/protocolFamily does not take effect

2019-06-07 Thread Ganesh Murthy (JIRA)


 [ 
https://issues.apache.org/jira/browse/DISPATCH-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ganesh Murthy updated DISPATCH-1079:

Fix Version/s: (was: 1.8.0)

> Setting socketAddressFamily/protocolFamily does not take effect
> ---
>
> Key: DISPATCH-1079
> URL: https://issues.apache.org/jira/browse/DISPATCH-1079
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 1.2.0
>Reporter: Ganesh Murthy
>Priority: Major
>
> socketAddressFamily/protocolFamily can be specified on a listener like this
> {noformat}
> listener {
>     idleTimeoutSeconds: 120
>     saslMechanisms: ANONYMOUS
>     host: ::1
>     role: normal
>     socketAddressFamily: IPv6
>     authenticatePeer: no
>     port: 29190
> }{noformat}
> In the above examole, socketAddressFamily to IPv6 makes sure that the 
> connection be made on the IPv6 interface.
>  
> The commit 6f56e289bec0db4a1de257883dc456a502c42fe7 removed all code to 
> relating protocol family so the code does not enforce this anymore.
>  
> Add back code to enforce  this restriction.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Updated] (DISPATCH-1079) Setting socketAddressFamily/protocolFamily does not take effect

2019-04-16 Thread Ganesh Murthy (JIRA)


 [ 
https://issues.apache.org/jira/browse/DISPATCH-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ganesh Murthy updated DISPATCH-1079:

Fix Version/s: (was: 1.7.0)
   1.8.0

> Setting socketAddressFamily/protocolFamily does not take effect
> ---
>
> Key: DISPATCH-1079
> URL: https://issues.apache.org/jira/browse/DISPATCH-1079
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 1.2.0
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.8.0
>
>
> socketAddressFamily/protocolFamily can be specified on a listener like this
> {noformat}
> listener {
>     idleTimeoutSeconds: 120
>     saslMechanisms: ANONYMOUS
>     host: ::1
>     role: normal
>     socketAddressFamily: IPv6
>     authenticatePeer: no
>     port: 29190
> }{noformat}
> In the above examole, socketAddressFamily to IPv6 makes sure that the 
> connection be made on the IPv6 interface.
>  
> The commit 6f56e289bec0db4a1de257883dc456a502c42fe7 removed all code to 
> relating protocol family so the code does not enforce this anymore.
>  
> Add back code to enforce  this restriction.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Updated] (DISPATCH-1079) Setting socketAddressFamily/protocolFamily does not take effect

2019-03-27 Thread Ted Ross (JIRA)


 [ 
https://issues.apache.org/jira/browse/DISPATCH-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Ross updated DISPATCH-1079:
---
Fix Version/s: (was: 1.6.0)
   1.7.0

> Setting socketAddressFamily/protocolFamily does not take effect
> ---
>
> Key: DISPATCH-1079
> URL: https://issues.apache.org/jira/browse/DISPATCH-1079
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 1.2.0
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.7.0
>
>
> socketAddressFamily/protocolFamily can be specified on a listener like this
> {noformat}
> listener {
>     idleTimeoutSeconds: 120
>     saslMechanisms: ANONYMOUS
>     host: ::1
>     role: normal
>     socketAddressFamily: IPv6
>     authenticatePeer: no
>     port: 29190
> }{noformat}
> In the above examole, socketAddressFamily to IPv6 makes sure that the 
> connection be made on the IPv6 interface.
>  
> The commit 6f56e289bec0db4a1de257883dc456a502c42fe7 removed all code to 
> relating protocol family so the code does not enforce this anymore.
>  
> Add back code to enforce  this restriction.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Updated] (DISPATCH-1079) Setting socketAddressFamily/protocolFamily does not take effect

2018-12-18 Thread Ganesh Murthy (JIRA)


 [ 
https://issues.apache.org/jira/browse/DISPATCH-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ganesh Murthy updated DISPATCH-1079:

Fix Version/s: (was: 1.5.0)
   1.6.0

> Setting socketAddressFamily/protocolFamily does not take effect
> ---
>
> Key: DISPATCH-1079
> URL: https://issues.apache.org/jira/browse/DISPATCH-1079
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 1.2.0
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.6.0
>
>
> socketAddressFamily/protocolFamily can be specified on a listener like this
> {noformat}
> listener {
>     idleTimeoutSeconds: 120
>     saslMechanisms: ANONYMOUS
>     host: ::1
>     role: normal
>     socketAddressFamily: IPv6
>     authenticatePeer: no
>     port: 29190
> }{noformat}
> In the above examole, socketAddressFamily to IPv6 makes sure that the 
> connection be made on the IPv6 interface.
>  
> The commit 6f56e289bec0db4a1de257883dc456a502c42fe7 removed all code to 
> relating protocol family so the code does not enforce this anymore.
>  
> Add back code to enforce  this restriction.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Updated] (DISPATCH-1079) Setting socketAddressFamily/protocolFamily does not take effect

2018-10-12 Thread Ganesh Murthy (JIRA)


 [ 
https://issues.apache.org/jira/browse/DISPATCH-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ganesh Murthy updated DISPATCH-1079:

Fix Version/s: (was: 1.4.0)
   1.5.0

> Setting socketAddressFamily/protocolFamily does not take effect
> ---
>
> Key: DISPATCH-1079
> URL: https://issues.apache.org/jira/browse/DISPATCH-1079
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 1.2.0
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.5.0
>
>
> socketAddressFamily/protocolFamily can be specified on a listener like this
> {noformat}
> listener {
>     idleTimeoutSeconds: 120
>     saslMechanisms: ANONYMOUS
>     host: ::1
>     role: normal
>     socketAddressFamily: IPv6
>     authenticatePeer: no
>     port: 29190
> }{noformat}
> In the above examole, socketAddressFamily to IPv6 makes sure that the 
> connection be made on the IPv6 interface.
>  
> The commit 6f56e289bec0db4a1de257883dc456a502c42fe7 removed all code to 
> relating protocol family so the code does not enforce this anymore.
>  
> Add back code to enforce  this restriction.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Updated] (DISPATCH-1079) Setting socketAddressFamily/protocolFamily does not take effect

2018-08-09 Thread Ganesh Murthy (JIRA)


 [ 
https://issues.apache.org/jira/browse/DISPATCH-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ganesh Murthy updated DISPATCH-1079:

Fix Version/s: (was: 1.3.0)
   1.4.0

> Setting socketAddressFamily/protocolFamily does not take effect
> ---
>
> Key: DISPATCH-1079
> URL: https://issues.apache.org/jira/browse/DISPATCH-1079
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 1.2.0
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.4.0
>
>
> socketAddressFamily/protocolFamily can be specified on a listener like this
> {noformat}
> listener {
>     idleTimeoutSeconds: 120
>     saslMechanisms: ANONYMOUS
>     host: ::1
>     role: normal
>     socketAddressFamily: IPv6
>     authenticatePeer: no
>     port: 29190
> }{noformat}
> In the above examole, socketAddressFamily to IPv6 makes sure that the 
> connection be made on the IPv6 interface.
>  
> The commit 6f56e289bec0db4a1de257883dc456a502c42fe7 removed all code to 
> relating protocol family so the code does not enforce this anymore.
>  
> Add back code to enforce  this restriction.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Updated] (DISPATCH-1079) Setting socketAddressFamily/protocolFamily does not take effect

2018-07-13 Thread Ganesh Murthy (JIRA)


 [ 
https://issues.apache.org/jira/browse/DISPATCH-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ganesh Murthy updated DISPATCH-1079:

Description: 
socketAddressFamily/protocolFamily can be specified on a listener like this
{noformat}
listener {
    idleTimeoutSeconds: 120
    saslMechanisms: ANONYMOUS
    host: ::1
    role: normal
    socketAddressFamily: IPv6
    authenticatePeer: no
    port: 29190
}{noformat}
In the above examole, socketAddressFamily to IPv6 makes sure that the 
connection be made on the IPv6 interface.

 

The commit 6f56e289bec0db4a1de257883dc456a502c42fe7 removed all code to 
relating protocol family so the code does not enforce this anymore.

 

Add back code to enforce  this restriction.

  was:
socketAddressFamily/protocolFamily can be specified on a listener like this
{noformat}
listener {
    idleTimeoutSeconds: 120
    saslMechanisms: ANONYMOUS
    host: ::1
    role: normal
    socketAddressFamily: IPv6
    authenticatePeer: no
    port: 29190
}{noformat}
In the above examole, socketAddressFamily to IPv6 makes sure that the 
connection be made on the IPv6 interface.

 

The commit 6f56e289bec0db4a1de257883dc456a502c42fe7 removed all code to 
protocol family so the code does not enforce this anymore.

 

Add back code to enforce  this restriction.


> Setting socketAddressFamily/protocolFamily does not take effect
> ---
>
> Key: DISPATCH-1079
> URL: https://issues.apache.org/jira/browse/DISPATCH-1079
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 1.2.0
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.3.0
>
>
> socketAddressFamily/protocolFamily can be specified on a listener like this
> {noformat}
> listener {
>     idleTimeoutSeconds: 120
>     saslMechanisms: ANONYMOUS
>     host: ::1
>     role: normal
>     socketAddressFamily: IPv6
>     authenticatePeer: no
>     port: 29190
> }{noformat}
> In the above examole, socketAddressFamily to IPv6 makes sure that the 
> connection be made on the IPv6 interface.
>  
> The commit 6f56e289bec0db4a1de257883dc456a502c42fe7 removed all code to 
> relating protocol family so the code does not enforce this anymore.
>  
> Add back code to enforce  this restriction.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Updated] (DISPATCH-1079) Setting socketAddressFamily/protocolFamily does not take effect

2018-07-13 Thread Ganesh Murthy (JIRA)


 [ 
https://issues.apache.org/jira/browse/DISPATCH-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ganesh Murthy updated DISPATCH-1079:

Description: 
socketAddressFamily/protocolFamily can be specified on a listener like this
{noformat}
listener {
    idleTimeoutSeconds: 120
    saslMechanisms: ANONYMOUS
    host: ::1
    role: normal
    socketAddressFamily: IPv6
    authenticatePeer: no
    port: 29190
}{noformat}
In the above examole, socketAddressFamily to IPv6 makes sure that the 
connection be made on the IPv6 interface.

 

The commit 6f56e289bec0db4a1de257883dc456a502c42fe7 removed all code to 
protocol family so the code does not enforce this anymore.

 

Add back code to enforces this restriction.

  was:
socketAddressFamily/protocolFamily can be specified on a listener like this 
{noformat}
listener {
    idleTimeoutSeconds: 120
    saslMechanisms: ANONYMOUS
    host: ::1
    role: normal
    socketAddressFamily: IPv6
    authenticatePeer: no
    port: 29190
}{noformat}
In the above examole, socketAddressFamily to IPv6 makes sure that the 
connection be made on the IPv6 interface.

 

The commit 6f56e289bec0db4a1de257883dc456a502c42fe7 removed all code to 
protocol family so the code does not enforce this anymore.

 

Add back code the enforces this restriction.


> Setting socketAddressFamily/protocolFamily does not take effect
> ---
>
> Key: DISPATCH-1079
> URL: https://issues.apache.org/jira/browse/DISPATCH-1079
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 1.2.0
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.3.0
>
>
> socketAddressFamily/protocolFamily can be specified on a listener like this
> {noformat}
> listener {
>     idleTimeoutSeconds: 120
>     saslMechanisms: ANONYMOUS
>     host: ::1
>     role: normal
>     socketAddressFamily: IPv6
>     authenticatePeer: no
>     port: 29190
> }{noformat}
> In the above examole, socketAddressFamily to IPv6 makes sure that the 
> connection be made on the IPv6 interface.
>  
> The commit 6f56e289bec0db4a1de257883dc456a502c42fe7 removed all code to 
> protocol family so the code does not enforce this anymore.
>  
> Add back code to enforces this restriction.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Updated] (DISPATCH-1079) Setting socketAddressFamily/protocolFamily does not take effect

2018-07-13 Thread Ganesh Murthy (JIRA)


 [ 
https://issues.apache.org/jira/browse/DISPATCH-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ganesh Murthy updated DISPATCH-1079:

Description: 
socketAddressFamily/protocolFamily can be specified on a listener like this
{noformat}
listener {
    idleTimeoutSeconds: 120
    saslMechanisms: ANONYMOUS
    host: ::1
    role: normal
    socketAddressFamily: IPv6
    authenticatePeer: no
    port: 29190
}{noformat}
In the above examole, socketAddressFamily to IPv6 makes sure that the 
connection be made on the IPv6 interface.

 

The commit 6f56e289bec0db4a1de257883dc456a502c42fe7 removed all code to 
protocol family so the code does not enforce this anymore.

 

Add back code to enforce  this restriction.

  was:
socketAddressFamily/protocolFamily can be specified on a listener like this
{noformat}
listener {
    idleTimeoutSeconds: 120
    saslMechanisms: ANONYMOUS
    host: ::1
    role: normal
    socketAddressFamily: IPv6
    authenticatePeer: no
    port: 29190
}{noformat}
In the above examole, socketAddressFamily to IPv6 makes sure that the 
connection be made on the IPv6 interface.

 

The commit 6f56e289bec0db4a1de257883dc456a502c42fe7 removed all code to 
protocol family so the code does not enforce this anymore.

 

Add back code to enforces this restriction.


> Setting socketAddressFamily/protocolFamily does not take effect
> ---
>
> Key: DISPATCH-1079
> URL: https://issues.apache.org/jira/browse/DISPATCH-1079
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 1.2.0
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.3.0
>
>
> socketAddressFamily/protocolFamily can be specified on a listener like this
> {noformat}
> listener {
>     idleTimeoutSeconds: 120
>     saslMechanisms: ANONYMOUS
>     host: ::1
>     role: normal
>     socketAddressFamily: IPv6
>     authenticatePeer: no
>     port: 29190
> }{noformat}
> In the above examole, socketAddressFamily to IPv6 makes sure that the 
> connection be made on the IPv6 interface.
>  
> The commit 6f56e289bec0db4a1de257883dc456a502c42fe7 removed all code to 
> protocol family so the code does not enforce this anymore.
>  
> Add back code to enforce  this restriction.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org