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.

Sign up for GitHub

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

Jump to bottom

Caching service is enabling port 7500 for diagnostics by default #3807

Open
pablocarle opened this issue Sep 27, 2024 · 2 comments
Open

Caching service is enabling port 7500 for diagnostics by default #3807

pablocarle opened this issue Sep 27, 2024 · 2 comments
Labels
bug Verified defect in functionality Priority: High size/S

Comments

@pablocarle
Copy link
Contributor

Describe the bug
Caching service is trying to bind to port 7500 (default jgroups diagnostics port) even when the default should be to have it disabled.

Error / Warn messages are visible in v3 API ML with debug spring profile active.

Expected behavior
Port 7500 is not required in api ml
@pablocarle pablocarle added bug Verified defect in functionality new New issue that has not been worked on yet labels Sep 27, 2024
@EvaJavornicka EvaJavornicka added clarification Issue is being clarified in the discussion with the creator of the issue new New issue that has not been worked on yet and removed new New issue that has not been worked on yet labels Oct 2, 2024
@pablocarle
Copy link
Contributor Author

It seems 7600 (multicast) is also a default from jgroups that is not possible to configure in start.sh (mcast_port)
http://www.jgroups.org/manual/html/protlist.html

@pablocarle
Copy link
Contributor Author

This can also bring issues when starting more than one Zowe instance in the same LPAR

@balhar-jakub balhar-jakub removed the clarification Issue is being clarified in the discussion with the creator of the issue label Jan 21, 2025
@EvaJavornicka EvaJavornicka added Priority: High size/S and removed new New issue that has not been worked on yet labels Jan 22, 2025
@EvaJavornicka EvaJavornicka moved this from New to Unplanned Bugs in API Mediation Layer Backlog Management Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Verified defect in functionality Priority: High size/S
Projects
API Mediation Layer Backlog Management
Status: Unplanned Bugs
Milestone
No milestone
Development

No branches or pull requests
3 participants
@balhar-jakub @pablocarle @EvaJavornicka