JBoss tools plugin not recognizing server on 8180

[mschwery]

I am having problems running an project on the local server in eclipse 4.3 with the port offset set to 100.

When I start the server it says that it has started in the console but when I right click on a project and say run on server eclipse thinks the server has not started.

If I access the application from a browser it runs fine but won't run inside eclipse.

[maxandersen]

Did you set the port offset in eclipse?

does the server editor show the right port in the port section or the default 8080 ?

Try setting the port specifically and see if it works.

we do try and detect port/port offsets but there are corner cases we can't guess/detect so thats what the explicit override is for.

[mschwery]

If I change the port offset in the standalone file it seems to be ok.

However that's not what I want to have people do.

What would be great is if I could have multiple jvms under the Jboss install with a different value for offset hard coded in each standalone.xml and start different ones by just changing the value in the offset box on the server tab.

That way if you have 100 in the offset box on the server tab eclipse would start the jvm that was hard coded with a offset value of 100 and in the console you would see the 8100 and 10090 port displayed at startup.

[maxandersen]

rob.stryker  might be able to explain, but I recall the ports are just based on what is detected in the configuration.

I agree that this could be smarter and add it to the command line arguments if not already there.

[rob.stryker]

Currently, the way to accomplish what you want would be to create several copies of your standalone.xml, modify the port-offset values in the standalone.xml, then in eclipse, make one runtime for each of your created .xml files, and then of course 5 servers, targeting each of the 5 runtimes.

I do like the idea of adding it cmd line arguments if the user is manually setting the value, but this provides a problem in that it would be conflicting for the users. All the other ports have a workflow where the command line args aren't changed at all and the ports are only using for interfacing with the running server.

It might be possible to change this, but if it turns out any specific port does not have hte ability to be overridden via command line args, it would make the UI inconsistant. If for example port-offset UI could change teh cmd line args, but web port or management port could not, then the user may be confused.

[maxandersen]

rob.stryker wouldn't it be sufficient just to manually add the override to the command line arguments ? (creating that many standalone.xml setups seems overkill for this).

[rob.stryker]

You're right that it would seem easier, but it'd be a workflow change, and also (possibly) an API change to many classes and models. So it's not "trivially easier". But a JIRA should definitely be opened to investigate it.

[rob.stryker]

JIRA reference:  https://issues.jboss.org/browse/JBIDE-15391

[maxandersen]

@Rob Stryker you wrote:

"Currently, the way to accomplish what you want would be to create several copies of your standalone.xml, modify the port-offset values in the standalone.xml, then in eclipse, make one runtime for each of your created .xml files, and then of course 5 servers, targeting each of the 5 runtimes."

I just pointed out that afaics the simplest approach for the user currently is to set the port offsets manually via the command line arguments and then set the portoffset manually in the UI. No need for "several copies of your standalone.xml" if the only thing you want is being able to run multiple servers from the same setup.

[rob.stryker]

> I just pointed out that afaics the simplest approach for the user currently (etc)

Yes, this is right.