search

HCL-TECH-SOFTWARE / connections-automation

Deployment and upgrade automation scripts for HCL Connections 7.0 based on Ansible
Apache License 2.0
17 stars 31 forks source link

Comment out teams-tab/api, because it is already included #217

Closed stoeps13 closed 1 year ago

stoeps13 commented 1 year ago

Restarting or Starting HTTP Server generates warning/error on console:

/opt/IBM/HTTPServer/bin/apachectl -k stop [Tue Oct 18 09:02:07 2022] [warn] worker http://cnx7-ora-cp.stoeps.home:32080/teams-tab already used by another worker

Reason are duplicate proxypass definitions for /teams-tab and /teams-tab/api, the api rule is already included in the first rule, so no need to proxypass both urls.

I commented out the additional rule (/teams-tab was missing in the ssl section, but still in non-ssl / generic)

If the /teams-tab is no longer needed, then please remove from ssl and general part of the config. If it is still needed merge this PR please.

stoeps13 commented 1 year ago

I checked in my environment and the teams integration is accessing /teams-tab and the rule needs to be there, so just /teams-tab/api is too much.

sabrina-yee commented 1 year ago

Following up with our dev team re: /teams-tab/api.

david-bell-hcl commented 1 year ago

@stoeps13 It is a bit confusing because the /teams-tab context root is overloaded, with requests to /teams-tab and /teams-tab/api going to two different backend services via the teams ingress rules. It was built that way from the outset, not like the teams share service with two entirely separate context roots.

I also tried commenting out /teams-tab/api on one of our environments and the teams tab integration seems to still be working fine. I seem to recall some kind of issue in ingress when we first created this integration, such that it only worked when we separated the entries in IHS. The warning on IHS startup was not material to it functioning properly.

Anyway, seems like we can simplify now with your PR. Thanks for the input.