[jboss-jira] [JBoss JIRA] (WFLY-3935) cluster-ha-singleton fails to deploy when the server is started with the debug flag

[Anderson Parra de Paula (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021949#comment-13021949 ] 

Anderson Parra de Paula commented on WFLY-3935:
-----------------------------------------------

I didn't have problems to run this application on current development version using debug mode.

Please, take a look at log:
14:27:54,664 INFO  [org.jboss.as.server] (XNIO-1 task-7) WFLYSRV0010: Deployed "wildfly-cluster-ha-singleton-service.jar" (runtime-name : "wildfly-cluster-ha-singleton-service.jar")
14:28:00,010 INFO  [org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.SchedulerBean] (EJB default - 1) HASingletonTimer: Info=HASingleton timer @jb.node1 Fri Nov 21 14:27:54 GMT 2014
14:28:10,002 INFO  [org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.SchedulerBean] (EJB default - 2) HASingletonTimer: Info=HASingleton timer @jb.node1 Fri Nov 21 14:27:54 GMT 2014
14:28:20,002 INFO  [org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.SchedulerBean] (EJB default - 3) HASingletonTimer: Info=HASingleton timer @jb.node1 Fri Nov 21 14:27:54 GMT 2014
14:28:30,001 INFO  [org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.SchedulerBean] (EJB default - 4) HASingletonTimer: Info=HASingleton timer @jb.node1 Fri Nov 21 14:27:54 GMT 2014
14:28:40,024 INFO  [org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.SchedulerBean] (EJB default - 5) HASingletonTimer: Info=HASingleton timer @jb.node1 Fri Nov 21 14:27:54 GMT 2014
14:28:50,015 INFO  [org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.SchedulerBean] (EJB default - 6) HASingletonTimer: Info=HASingleton timer @jb.node1 Fri Nov 21 14:27:54 GMT 2014


> cluster-ha-singleton fails to deploy when the server is started with the debug flag
> -----------------------------------------------------------------------------------
>
>                 Key: WFLY-3935
>                 URL: https://issues.jboss.org/browse/WFLY-3935
>             Project: WildFly
>          Issue Type: Bug
>    Affects Versions: 8.1.0.Final
>            Reporter: Euan Mapham
>            Assignee: Jason Greene
>
> When a clustered-ha-singleton is deployed to a wildfly server that was started using the --debug option, a org.jboss.msc.service.ServiceNotFoundException occurrs.
> I am using the quickstart/cluster-ha-singleton found on github:
> https://github.com/wildfly/quickstart/tree/master/cluster-ha-singleton
> Wildfly version 8.1.0.Final
> I start the server with this command:
> ./bin/standalone.sh --debug -server-config=standalone-ha.xml -Djboss.node.name=jb.node1
> I then deploy the wildfly-cluster-ha-singleton-service.jar.
> The exception that occurrs is:
> 15:03:31,803 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."wildfly-cluster-ha-singleton-service.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."wildfly-cluster-ha-singleton-service.jar".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "wildfly-cluster-ha-singleton-service.jar"
>   at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.1.0.Final.jar:8.1.0.Final]
>   at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>   at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_20]
>   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_20]
>   at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_20]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.clustering.singleton.builder.server.default not found
>   at org.jboss.as.server.deployment.service.ServiceActivatorProcessor.deploy(ServiceActivatorProcessor.java:72) [wildfly-server-8.1.0.Final.jar:8.1.0.Final]
>   at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.1.0.Final.jar:8.1.0.Final]
>   ... 5 more
> Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.clustering.singleton.builder.server.default not found
>   at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:668) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>   at org.jboss.msc.service.DelegatingServiceRegistry.getRequiredService(DelegatingServiceRegistry.java:46) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>   at org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.HATimerServiceActivator.install(HATimerServiceActivator.java:51)
>   at org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.HATimerServiceActivator.activate(HATimerServiceActivator.java:44)
>   at org.jboss.as.server.deployment.service.ServiceActivatorProcessor.deploy(ServiceActivatorProcessor.java:70) [wildfly-server-8.1.0.Final.jar:8.1.0.Final]
>   ... 6 more
> When I remove the "--debug" option from the command to start the server, everything works fine.
> This means we cannot debug our applications if we use this feature.
> Regards,
> Euan



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)