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

If the connection parameters (url, ip, port, etc) of a queued connector changes the queued messages will not be sent #1400

Closed
rbeckman-nextgen opened this issue May 11, 2020 · 6 comments
Milestone

Comments

@rbeckman-nextgen
Copy link
Collaborator

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

In a queued connector, if the connection parameters changes (ip, port, etc.), the queued messages what are in the queue waiting for being sent, kept the old parameters, so are sent to the old destination

IMHO this is a bit confusing for the user. And it's not easy to solve with the current queue architecture.

Imported Issue. Original Details:
Jira Issue Key: MIRTH-1401
Reporter: albertosaez
Created: 2010-04-19T14:51:29.000-0700

@rbeckman-nextgen rbeckman-nextgen added this to the 3.0.0 Beta 1 milestone May 11, 2020
@rbeckman-nextgen
Copy link
Collaborator Author

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

This is my proposed patch. The endpoint url is not readed from the queued file, but from the mule configuration.

IN this way, old mirth queue messages can be converted to queued objects.

Imported Comment. Original Details:
Author: albertosaez
Created: 2010-04-21T17:42:23.000-0700

@rbeckman-nextgen
Copy link
Collaborator Author

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

This will be included in a system wide queuing rewrite.

Imported Comment. Original Details:
Author: jacobb
Created: 2010-05-11T15:52:57.000-0700

@rbeckman-nextgen
Copy link
Collaborator Author

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

Perhaps an option should be added to replace all connection information in current queued messages with the new information during deploy.

Imported Comment. Original Details:
Author: jacobb
Created: 2010-08-05T17:23:44.000-0700

@rbeckman-nextgen
Copy link
Collaborator Author

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

Updated patch for version 2.1.1

Imported Comment. Original Details:
Author: albertosaez
Created: 2011-10-09T14:45:37.000-0700

@rbeckman-nextgen
Copy link
Collaborator Author

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

This is resolved by MIRTH-2250 with the regenerate template option on the queue settings. This option can be enabled or disabled and the channel can be redeployed.

Imported Comment. Original Details:
Author: jacobb
Created: 2012-11-08T13:54:03.000-0800

@rbeckman-nextgen
Copy link
Collaborator Author

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

Confirmed that connector properties for queued messages get re-run through the Velocity replacer when Regenerate Template is checked.

Imported Comment. Original Details:
Author: narupley
Created: 2012-12-20T18:59:00.000-0800

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.