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

Expose connection properties from open performative #32

Open
Sharad-Regoti-Unotech opened this issue May 31, 2021 · 3 comments
Open

Expose connection properties from open performative #32

Sharad-Regoti-Unotech opened this issue May 31, 2021 · 3 comments
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved.

Comments

@Sharad-Regoti-Unotech
Copy link

How can we connect to active mq cluster using this library

@jhendrixMSFT
Copy link
Member

Closing as there's too little information here to be actionable. Please ping back with more details if this is still an issue.

@Thitiphong
Copy link

Thitiphong commented Nov 24, 2021

How can we get connection property "failover-server-list" from ActionMQ server with this library
https://www.oasis-open.org/committees/download.php/60379/amqp-failover-v1.0-wd01.pdf

@jhendrixMSFT
Copy link
Member

Thanks this is helpful. Per the doc, this should come back as part of the open performative. We don't expose the properties at present though.

@jhendrixMSFT jhendrixMSFT reopened this Nov 24, 2021
@jhendrixMSFT jhendrixMSFT changed the title Connect to active failover cluster Expose connection properties from open performative Nov 24, 2021
@RickWinter RickWinter added customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved. labels May 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved.
Projects
None yet
Development

No branches or pull requests

4 participants