jconsole not found

[jdelgadot]

Hi,

Recently i have some problems with the wildly-maven-plugin

when i try to use mvn wildly:run i ve got the next error

Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.1.0.Final:run (default-cli) on project pra3: Execution default-cli of goal org.wildfly.plugins:wildfly-maven-plugin:1.1.0.Final:run failed: Plugin org.wildfly.plugins:wildfly-maven-plugin:1.1.0.Final or one of its dependencies could not be resolved: Could not find artifact sun.jdk:jconsole:jar:jdk at specified path /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home/../lib/jconsole.jar -

Where do i find console.jar?

This happens inside Eclipse when i use Maven build ... goals: wildly:run

But if i use a terminal and i write mvn wildly:run it works.

[jamezp]

Could you try 1.2.1.Final? That version should work with Java 9.

--

James R. Perkins

[jdelgadot]

Now with 1.2.1.Final another error

12:26:24,508 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service org.wildfly.undertow.listener.default: org.jboss.msc.service.StartException in service org.wildfly.undertow.listener.default: Address already in use /127.0.0.1:8080

  at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:179)

  at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)

  at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)

  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

  at java.lang.Thread.run(Thread.java:748)

[jamezp]

It looks like you have something else listening on port 8080. You'd have to figure what it is by using something like netstat.

--

James R. Perkins

[jdelgadot]

It is not that.

If i do mvn wildly:run the first time i hate not any error but the second i have address already in use.

If i shutdown the server and then i do mvn run:install i have again any error.

What does it happen?

It seems that wildly:run start always a server instance???

[jamezp]

Yes the run goal will always attempt to start a server. It's meant to be used as a quick way to run your application. Once you're done it's required to CTRL+C to kill the process. If you execute the run goal twice it will attempt to start two different servers and deploy your application.

--

James R. Perkins

[nickleus]

Thx James, I had the same problem, so i just changed the pom.xml

from:

<version.wildfly.maven.plugin>1.0.2.Final</version.wildfly.maven.plugin>

to:

<version.wildfly.maven.plugin>1.2.1.Final</version.wildfly.maven.plugin>

then reran the mvn call:

mvn clean install wildfly:deploy

and it worked--the error was gone