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

Fix mismatch in axis service and proxy(synapse) service state #2104

Merged
merged 1 commit into from
Oct 3, 2023

Conversation

malakaganga
Copy link
Contributor

Purpose

For MI we have introduced this feature using a DeploymentInterceptor. But to enable that we have to add the following service parameter to the proxy

true

But there is an issue with MI where it does not properly propagate this state since be due to a mismatch in axis service and proxy(synapse) service state.

Fixes: wso2/product-micro-integrator#2981

For MI we have introduced this feature using a DeploymentInterceptor.
But to enable that we have to add the following service parameter to the proxy

<parameter name="keepServiceHistory">true</parameter>

But there is an issue with MI where it does not properly propagate this state
since be due to a mismatch in axis service and proxy(synapse) service state.

Fixes: wso2/product-micro-integrator#2981
@malakaganga malakaganga merged commit 63f9910 into wso2:master Oct 3, 2023
1 check failed
shilmyhasan pushed a commit to shilmyhasan/wso2-synapse-1 that referenced this pull request Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Maintain proxy state in MI Dashboard after restart
2 participants