[jira] [Commented] (CURATOR-665) ModeledFramework does not throw expected exception and instead hangs

2023-03-31 Thread Zili Chen (Jira)
[ https://issues.apache.org/jira/browse/CURATOR-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707298#comment-17707298 ] Zili Chen commented on CURATOR-665: --- Thanks for your reproduce [~Ryan0751]! I located the root cause

[jira] [Assigned] (CURATOR-665) ModeledFramework does not throw expected exception and instead hangs

2023-03-31 Thread Zili Chen (Jira)
[ https://issues.apache.org/jira/browse/CURATOR-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen reassigned CURATOR-665: - Assignee: Zili Chen > ModeledFramework does not throw expected exception and instead hangs >

[jira] [Commented] (CURATOR-665) ModeledFramework does not throw expected exception and instead hangs

2023-03-31 Thread Ryan Ruel (Jira)
[ https://issues.apache.org/jira/browse/CURATOR-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707255#comment-17707255 ] Ryan Ruel commented on CURATOR-665: --- Below is a test case which you can drop into TestModeledFramework

[jira] [Assigned] (CURATOR-664) EnsembleTracker use resolved server address in connection string if client address is wildcard

2023-03-31 Thread Enrico Olivelli (Jira)
[ https://issues.apache.org/jira/browse/CURATOR-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enrico Olivelli reassigned CURATOR-664: --- Assignee: Kezhu Wang > EnsembleTracker use resolved server address in connection

[jira] [Resolved] (CURATOR-664) EnsembleTracker use resolved server address in connection string if client address is wildcard

2023-03-31 Thread Enrico Olivelli (Jira)
[ https://issues.apache.org/jira/browse/CURATOR-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enrico Olivelli resolved CURATOR-664. - Resolution: Fixed > EnsembleTracker use resolved server address in connection string if