Skip to content

Conversation

jajik
Copy link
Member

@jajik jajik commented Jun 27, 2025

For some (historic?) reasons we've been using two ports in tests, so let's use just one instead.

@jajik jajik requested a review from jfclere June 30, 2025 07:24
Copy link
Member

@rhusar rhusar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What makes this the pick? Port 6666 is primarily associated with IRC communications but is also notorious for malware use. I am not convinced.

@jajik
Copy link
Member Author

jajik commented Jul 11, 2025

We're currently using two (and we've been since I remember) and I usually accessed through 6666. But frankly I don't care, we can change it to any other one, I'd just like to end using two ports. Any suggestions or wishes?

Drop port 6666 completely as two ports are not needed
@jajik jajik requested a review from rhusar July 16, 2025 07:58
@jajik
Copy link
Member Author

jajik commented Jul 16, 2025

@rhusar I changed the port to the other one we are using (8000).

@jajik jajik changed the title Use only port 6666 in tests Use only port 8000 in tests Jul 16, 2025
Copy link
Member

@rhusar rhusar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are not going to like this, but the 8000 is used by tomcat as the default JDPA port. It can be changed to any port, but this is default, which makes little sense to have conflicting ports in a default setup.

@rhusar
Copy link
Member

rhusar commented Jul 16, 2025

For some (historic?) reasons we've been using two ports in tests, so let's use just one instead.

These were chosen poorly, for debugging with no thought given to it, which has lead to numerous problems.

Lets pick one that won't cause any problems and conflicts that we know of.

@rhusar
Copy link
Member

rhusar commented Jul 16, 2025

Thinking out load, how about port 9000 (or variation of that like 9090)? It's typically used as alternative http port, perhaps that's reasonable for mod_cluster manager. That would make public proxy address 80, Tomcat and WildFly default HTTP port 8080, Tomcat debugging 8000.

@rhusar
Copy link
Member

rhusar commented Jul 16, 2025

Thinking out load, how about port 9000 (or variation of that like 9090)? It's typically used as alternative http port, perhaps that's reasonable for mod_cluster manager. That would make public proxy address 80, Tomcat and WildFly default HTTP port 8080, Tomcat debugging 8000.

Scratch that, just use the port 8090 that we use in WildFly/Undertow implementation and stop reinventing the wheel.

@jajik
Copy link
Member Author

jajik commented Jul 16, 2025

😄

@jfclere Any input on this?

@rhusar
Copy link
Member

rhusar commented Jul 16, 2025

BTW Here's the Jira for this https://issues.redhat.com/browse/MODCLUSTER-858

@rhusar
Copy link
Member

rhusar commented Jul 16, 2025

BTW Here's the Jira for this https://issues.redhat.com/browse/MODCLUSTER-858

Docs part for this: modcluster/docs.modcluster.io#244

@jajik jajik closed this Jul 25, 2025
@jajik jajik deleted the playground branch July 25, 2025 12:16
@jfclere
Copy link
Member

jfclere commented Jul 25, 2025

@jajik Please use 8090 as suggested in https://issues.redhat.com/browse/MODCLUSTER-858

@jajik jajik restored the playground branch July 25, 2025 12:21
@jajik
Copy link
Member Author

jajik commented Jul 25, 2025

@jajik Please use 8090 as suggested in https://issues.redhat.com/browse/MODCLUSTER-858

@jfclere Done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants