Problema com debug Eclipse Neon

Isto ocorre quando o fonte não esta atualizado, provável que tiveram alterações mas o projeto não foi compilado, para resolver de um clean no projeto e inicie o debug novamente.

Aix, realizei o procedimento e continua o mesmo problema, inclusive já testei em diversos servidores, o problema é o mesmo, e sempre acaba na dando IvocationTargetException durante a execução

isso é um projeto maven?

É sim, inclusive ja tentei dar um update project … e nada

ja rodou um install ?

ainda não , como faço isso ?

Botão direito do mouse em cima do projeto.

Se for eclipse: run–> goals --> clean install

Se for Netbean: personalizar --> metas --> clean install

Se for por linha de comando: mvn clean install

Estou usando o eclipse, retornou esse erro na hora de dar install
[ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?

sim, não esta compilando, vai nas propriedades da JVM no eclipse e altera de JRE e aponta a JDK que vai funcionar.

Este processo do clean e install do maven deu certo alterando para JDK, porém o erro no debug continua… passa por linhas sem breakpoints e da Exceptions em classes que nem uso

esse fontes da classe em debug não são de outras dependencias internas ?

Não , na verdade identifiquei que o problema está ocorrendo em servidores wildfly, testei no tomcat e o debug funcionou normalmente, o que pode ser?

dentro da janela ali no servidor precisa fazer um full publishing, também pode experimentar dar um clean and clean work directory.

Realizei o procedimento, mas o wildfly 10.0 a aplicação nao está aparentemente nem subindo agora… aparece not found 404… e no tomcat normal

posta o log.

10:41:13,750 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final

10:41:14,006 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final

10:41:14,096 INFO  [<a href="http://org.jboss.as">org.jboss.as</a>] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) starting

10:41:15,565 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found produtos.war in deployment directory. To trigger deployment create a file called produtos.war.dodeploy

10:41:15,565 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found SvmProjetos.war in deployment directory. To trigger deployment create a file called SvmProjetos.war.dodeploy

10:41:15,566 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found SvmProjetos-0.0.1-SNAPSHOT.war in deployment directory. To trigger deployment create a file called SvmProjetos-0.0.1-SNAPSHOT.war.dodeploy

10:41:15,566 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found svm.war in deployment directory. To trigger deployment create a file called svm.war.dodeploy

10:41:15,566 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found praxis.war in deployment directory. To trigger deployment create a file called praxis.war.dodeploy

10:41:15,594 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)

10:41:15,615 INFO  [org.xnio] (MSC service thread 1-6) XNIO version 3.3.4.Final

10:41:15,623 INFO  [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.3.4.Final

10:41:15,677 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool – 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

10:41:15,703 INFO  [<a href="http://org.wildfly.extension.io">org.wildfly.extension.io</a>] (ServerService Thread Pool – 37) WFLYIO001: Worker ‘default’ has auto-configured to 8 core threads with 64 task threads based on your 4 available processors

10:41:15,733 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool – 38) WFLYCLINF0001: Activating Infinispan subsystem.

10:41:15,761 INFO  [org.jboss.as.connector] (MSC service thread 1-5) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.2.Final)

10:41:15,770 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = h2

10:41:15,928 INFO  [org.jboss.as.security] (ServerService Thread Pool – 53) WFLYSEC0002: Activating Security Subsystem

10:41:15,939 INFO  [org.jboss.as.webservices] (ServerService Thread Pool – 56) WFLYWS0002: Activating WebServices Extension

10:41:15,941 WARN  [org.jboss.as.txn] (ServerService Thread Pool – 54) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.

10:41:15,948 INFO  [org.jboss.as.security] (MSC service thread 1-5) WFLYSEC0001: Current PicketBox version=4.9.4.Final

10:41:15,966 INFO  [org.jboss.as.naming] (ServerService Thread Pool – 46) WFLYNAM0001: Activating Naming Subsystem

10:41:15,998 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool – 55) WFLYUT0003: Undertow 1.3.15.Final starting

10:41:16,000 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0003: Undertow 1.3.15.Final starting

10:41:16,012 INFO  [org.jboss.as.jsf] (ServerService Thread Pool – 44) WFLYJSF0007: Activated the following JSF Implementations: [main]

10:41:16,069 INFO  [org.jboss.as.naming] (MSC service thread 1-5) WFLYNAM0003: Starting Naming Service

10:41:16,071 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-5) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]

10:41:16,203 INFO  [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.

10:41:16,205 INFO  [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.

10:41:16,242 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool – 55) WFLYUT0014: Creating file handler for path ‘C:\Users\mjunior\wildfly-10.0.0.Final/welcome-content’ with options [directory-listing: ‘false’, follow-symlink: ‘false’, case-sensitive: ‘true’, safe-symlink-paths: ‘[]’]

10:41:16,541 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: Started server default-server.

10:41:16,547 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0018: Host default-host starting

10:41:16,565 INFO  [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.18.Final

10:41:16,678 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080

10:41:16,832 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of “SvmProjetos-0.0.1-SNAPSHOT.war” (runtime-name: “SvmProjetos-0.0.1-SNAPSHOT.war”)

10:41:16,834 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of “produtos.war” (runtime-name: “produtos.war”)

10:41:16,842 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Users\mjunior\wildfly-10.0.0.Final\standalone\deployments

10:41:17,178 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-6) ISPN000128: Infinispan version: Infinispan ‘Mahou’ 8.1.0.Final

10:41:17,321 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]

10:41:17,331 INFO  [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)

10:41:20,927 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)

10:41:20,964 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = produtos.war_com.mysql.jdbc.Driver_5_1

10:41:21,193 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool – 62) Inicializando Mojarra 2.2.12-jbossorg-2 20150729-1131 para o contexto '/produtos’

10:41:23,435 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool – 62) WFLYUT0021: Registered web context: /produtos

10:41:25,184 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry slf4j-api-1.5.6.jar in /C:/Users/mjunior/wildfly-10.0.0.Final/standalone/deployments/SvmProjetos-0.0.1-SNAPSHOT.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar  does not point to a valid jar for a Class-Path reference.

10:41:25,184 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry slf4j-jdk14-1.5.6.jar in /C:/Users/mjunior/wildfly-10.0.0.Final/standalone/deployments/SvmProjetos-0.0.1-SNAPSHOT.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar  does not point to a valid jar for a Class-Path reference.

10:41:25,185 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry concurrent-1.3.2.jar in /C:/Users/mjunior/wildfly-10.0.0.Final/standalone/deployments/SvmProjetos-0.0.1-SNAPSHOT.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar  does not point to a valid jar for a Class-Path reference.

10:41:25,185 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry antlr-2.7.2.jar in /C:/Users/mjunior/wildfly-10.0.0.Final/standalone/deployments/SvmProjetos-0.0.1-SNAPSHOT.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar  does not point to a valid jar for a Class-Path reference.

10:41:25,276 INFO  [org.jboss.as.pojo] (MSC service thread 1-8) WFLYPOJO0001: Found legacy bean/pojo namespace: urn:jboss:bean-deployer:2.0 - might be missing some xml features (potential exceptions).

10:41:25,572 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment SvmProjetos-0.0.1-SNAPSHOT.war

10:41:25,631 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-7) HV000001: Hibernate Validator 5.2.3.Final

10:41:26,040 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0004: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 4.0)

10:41:26,040 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0006: Starting Services for CDI deployment: SvmProjetos-0.0.1-SNAPSHOT.war

10:41:26,077 INFO  [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900: 2.3.2 (Final)

10:41:26,087 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = SvmProjetos-0.0.1-SNAPSHOT.war_com.microsoft.sqlserver.jdbc.SQLServerDriver_4_0

10:41:26,091 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0009: Starting weld service for deployment SvmProjetos-0.0.1-SNAPSHOT.war

10:41:27,212 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool – 95) Inicializando Mojarra 2.2.12-jbossorg-2 20150729-1131 para o contexto '/SvmProjetos-0.0.1-SNAPSHOT’

10:41:29,661 WARNING [javax.enterprise.resource.webcontainer.jsf.managedbean] (ServerService Thread Pool – 95) JSF1074: O bean gerenciado denominado ‘tarefasBean’ já foi registrado.  Substituindo o tipo de classe do bean gerenciado br.com.schmersal.svm.bean.TarefasBean por br.com.schmersal.svm.bean.TarefasBean.

10:41:30,810 INFO  [org.primefaces.webapp.PostConstructApplicationEventListener] (ServerService Thread Pool – 95) Running on PrimeFaces 5.1

10:41:30,817 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool – 95) WFLYUT0021: Registered web context: /SvmProjetos-0.0.1-SNAPSHOT

10:41:30,905 INFO  [org.jboss.as.server] (ServerService Thread Pool – 34) WFLYSRV0010: Deployed “SvmProjetos-0.0.1-SNAPSHOT.war” (runtime-name : “SvmProjetos-0.0.1-SNAPSHOT.war”)

10:41:30,905 INFO  [org.jboss.as.server] (ServerService Thread Pool – 34) WFLYSRV0010: Deployed “produtos.war” (runtime-name : “produtos.war”)

10:41:31,045 INFO  [<a href="http://org.jboss.as">org.jboss.as</a>] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on <a href="http://127.0.0.1:9990/management">http://127.0.0.1:9990/management</a>

10:41:31,046 INFO  [<a href="http://org.jboss.as">org.jboss.as</a>] (Controller Boot Thread) WFLYSRV0051: Admin console listening on <a href="http://127.0.0.1:9990">http://127.0.0.1:9990</a>

10:41:31,047 INFO  [<a href="http://org.jboss.as">org.jboss.as</a>] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started in 17660ms - Started 1034 of 1329 services (394 services are lazy, passive or on-demand)

10:41:51,137 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0019: Stopped Driver service with driver-name = SvmProjetos-0.0.1-SNAPSHOT.war_com.microsoft.sqlserver.jdbc.SQLServerDriver_4_0

10:41:51,147 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool – 114) WFLYUT0022: Unregistered web context: /SvmProjetos-0.0.1-SNAPSHOT

10:41:51,175 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Stopping weld service for deployment SvmProjetos-0.0.1-SNAPSHOT.war

10:41:51,428 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment SvmProjetos-0.0.1-SNAPSHOT.war (runtime-name: SvmProjetos-0.0.1-SNAPSHOT.war) in 294ms

10:41:51,497 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed “SvmProjetos-0.0.1-SNAPSHOT.war” (runtime-name: “SvmProjetos-0.0.1-SNAPSHOT.war”)

10:41:56,516 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found SvmProjetos-0.0.1-SNAPSHOT.war in deployment directory. To trigger deployment create a file called SvmProjetos-0.0.1-SNAPSHOT.war.dodeploy

10:41:56,521 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of “SvmProjetos-0.0.1-SNAPSHOT.war” (runtime-name: “SvmProjetos-0.0.1-SNAPSHOT.war”)

10:42:00,221 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry slf4j-api-1.5.6.jar in /C:/Users/mjunior/wildfly-10.0.0.Final/standalone/deployments/SvmProjetos-0.0.1-SNAPSHOT.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar  does not point to a valid jar for a Class-Path reference.

10:42:00,221 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry slf4j-jdk14-1.5.6.jar in /C:/Users/mjunior/wildfly-10.0.0.Final/standalone/deployments/SvmProjetos-0.0.1-SNAPSHOT.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar  does not point to a valid jar for a Class-Path reference.

10:42:00,221 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry concurrent-1.3.2.jar in /C:/Users/mjunior/wildfly-10.0.0.Final/standalone/deployments/SvmProjetos-0.0.1-SNAPSHOT.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar  does not point to a valid jar for a Class-Path reference.

10:42:00,221 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry antlr-2.7.2.jar in /C:/Users/mjunior/wildfly-10.0.0.Final/standalone/deployments/SvmProjetos-0.0.1-SNAPSHOT.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar  does not point to a valid jar for a Class-Path reference.

10:42:00,327 INFO  [org.jboss.as.pojo] (MSC service thread 1-2) WFLYPOJO0001: Found legacy bean/pojo namespace: urn:jboss:bean-deployer:2.0 - might be missing some xml features (potential exceptions).

10:42:00,576 INFO  [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment SvmProjetos-0.0.1-SNAPSHOT.war

10:42:00,750 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0004: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 4.0)

10:42:00,751 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Starting Services for CDI deployment: SvmProjetos-0.0.1-SNAPSHOT.war

10:42:00,755 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Started Driver service with driver-name = SvmProjetos-0.0.1-SNAPSHOT.war_com.microsoft.sqlserver.jdbc.SQLServerDriver_4_0

10:42:00,757 INFO  [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0009: Starting weld service for deployment SvmProjetos-0.0.1-SNAPSHOT.war

10:42:01,002 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool – 166) Inicializando Mojarra 2.2.12-jbossorg-2 20150729-1131 para o contexto '/SvmProjetos-0.0.1-SNAPSHOT’

10:42:02,117 WARNING [javax.enterprise.resource.webcontainer.jsf.managedbean] (ServerService Thread Pool – 166) JSF1074: O bean gerenciado denominado ‘tarefasBean’ já foi registrado.  Substituindo o tipo de classe do bean gerenciado br.com.schmersal.svm.bean.TarefasBean por br.com.schmersal.svm.bean.TarefasBean.

10:42:02,805 INFO  [org.primefaces.webapp.PostConstructApplicationEventListener] (ServerService Thread Pool – 166) Running on PrimeFaces 5.1

10:42:02,806 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool – 166) WFLYUT0021: Registered web context: /SvmProjetos-0.0.1-SNAPSHOT

10:42:02,827 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed “SvmProjetos-0.0.1-SNAPSHOT.war” (runtime-name : “SvmProjetos-0.0.1-SNAPSHOT.war”)

Esta tudo certo, digita o contexto no browser la em cima que deve carregar o projeto.

utilizando esse contexto funcionou perfeitamente, não existe como eu voltar ao contexto original do projeto assim como está no tomcat? Usando svmProjetos?