You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue description: We have observed an issue with the components deployed with maven as build output. For the applications deployed in the same AppNode and sharing the common dependencies, If we were manually stopping one of them, the other two were moving to impaired state in TEA.
On further analysing the issue, we found all the shared dependencies were not having the unique 4th level qualifier which made them dependent on each other. The shared dependencies which are not present in the same build server workspace are not adding the unique qualifier version. This leads to the need of unique 4th level qualifier in all the dependencies to resolve the conflicts between applications deployed on same appnode.
Steps to reproduce the issue:
Please refer to issue description. If needed, we can provide more granular steps.
Additional environment details if any:
Describe the results you received:
Post appnode/application restart applications going in impaired state.
Describe the results you expected:
Post appnode/application restart applications should be up and running state.
Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered:
Maven Plugin version: 2.8.1
Maven version: 3.225.0
Product : TIBCO ActiveMatrix Businessworks
Product version: BW 6.7.0 HF9
Component: Maven build plugin
Issue description: We have observed an issue with the components deployed with maven as build output. For the applications deployed in the same AppNode and sharing the common dependencies, If we were manually stopping one of them, the other two were moving to impaired state in TEA.
On further analysing the issue, we found all the shared dependencies were not having the unique 4th level qualifier which made them dependent on each other. The shared dependencies which are not present in the same build server workspace are not adding the unique qualifier version. This leads to the need of unique 4th level qualifier in all the dependencies to resolve the conflicts between applications deployed on same appnode.
Steps to reproduce the issue:
Please refer to issue description. If needed, we can provide more granular steps.
Additional environment details if any:
Describe the results you received:
Post appnode/application restart applications going in impaired state.
Describe the results you expected:
Post appnode/application restart applications should be up and running state.
Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered: