[jbossts-issues] [JBoss JIRA] (JBTM-3364) Construction of LRA recovery url does not consider variants in path registration
by Ondrej Chaloupka (Jira)
[ https://issues.redhat.com/browse/JBTM-3364?page=com.atlassian.jira.plugin... ]
Ondrej Chaloupka updated JBTM-3364:
-----------------------------------
Description:
The LRA recovery URL creation on coordinator expects that the path to recovery coordinator is `"http://\{host}:\{port}/lra-recovery-coordinator"`.
But that's wrong. The recovery coordinator could be deployed at various context path. E.g. in WildFly this depends on the deployment name. If the `war` of the coordinator deployment is named "test" then it will be deployed at ``"http://\{host}:\{port}/test/lra-recovery-coordinator"`.
was:
The LRA recovery URL creation on coordinator expects that the path to recovery coordinator is `"http://{host}:{port}/lra-recovery-coordinator"`.
But that's wrong. The recovery coordinator could be deployed at various context path. E.g. in WildFly this depends on the deployment name. If the `war` of the coordinator deployment is named "test" then it will be deployed at ``"http://{host}:{port}/test/lra-recovery-coordinator"`.
> Construction of LRA recovery url does not consider variants in path registration
> --------------------------------------------------------------------------------
>
> Key: JBTM-3364
> URL: https://issues.redhat.com/browse/JBTM-3364
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: LRA
> Affects Versions: 5.10.6.Final
> Reporter: Ondrej Chaloupka
> Assignee: Ondrej Chaloupka
> Priority: Critical
>
> The LRA recovery URL creation on coordinator expects that the path to recovery coordinator is `"http://\{host}:\{port}/lra-recovery-coordinator"`.
>
> But that's wrong. The recovery coordinator could be deployed at various context path. E.g. in WildFly this depends on the deployment name. If the `war` of the coordinator deployment is named "test" then it will be deployed at ``"http://\{host}:\{port}/test/lra-recovery-coordinator"`.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)