[JBoss JIRA] (WFLY-3935) cluster-ha-singleton fails to deploy when the server is started with the debug flag
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-3935?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-3935:
-----------------------------------
Assignee: Paul Ferraro (was: Jason Greene)
> 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
> Components: Clustering
> Affects Versions: 8.1.0.Final
> Reporter: Euan Mapham
> Assignee: Paul Ferraro
>
> 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)
11 years, 7 months
[JBoss JIRA] (WFLY-4086) If a ManagedExecutorService's Runnable throws an exception, it should not be eaten (but it's stacktrace should be shown in the console) by default
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-4086?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-4086:
-----------------------------------
Component/s: EE
> If a ManagedExecutorService's Runnable throws an exception, it should not be eaten (but it's stacktrace should be shown in the console) by default
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4086
> URL: https://issues.jboss.org/browse/WFLY-4086
> Project: WildFly
> Issue Type: Enhancement
> Components: EE
> Affects Versions: 8.1.0.Final
> Reporter: Geoffrey De Smet
> Assignee: Jason Greene
>
> To reproduce:
> {code}
> @Resource(name = "DefaultManagedExecutorService")
> ManagedExecutorService executor;
> public String myRestMethod() {
> executor.submit(new SolverCallable());
> return "Submitted.";
> }
> private class SolverCallable implements Runnable {
> public void run() {
> throw new IllegalStateException("Tweety bird: Please Sylvester, don't eat me!");
> }
> }
> {code}
> Poor tweety bird's plea (nor the stacktrace) doesn't show up in the WildFly console of a vanilla installation.
> This led me to believe I had no error.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFLY-3935) cluster-ha-singleton fails to deploy when the server is started with the debug flag
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-3935?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-3935:
-----------------------------------
Component/s: Clustering
> 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
> Components: Clustering
> 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)
11 years, 7 months
[JBoss JIRA] (WFCORE-434) Fix AuditLogFieldsOfLogTestCase
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-434?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-434:
------------------------------------
Component/s: Domain Management
Test Suite
> Fix AuditLogFieldsOfLogTestCase
> -------------------------------
>
> Key: WFCORE-434
> URL: https://issues.jboss.org/browse/WFCORE-434
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Test Suite
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
>
> Test started to fail with:
> {noformat}
> java.lang.IllegalArgumentException: Invalid character: -
> at org.jboss.dmr.JSONParserImpl.invalid(JSONParserImpl.java:136)
> at org.jboss.dmr.JSONParser.yyLex(JSONParser.java:596)
> at org.jboss.dmr.JSONParser.yyParse(JSONParser.java:662)
> at org.jboss.dmr.ModelNode.fromJSONString(ModelNode.java:1390)
> at org.jboss.as.test.manualmode.auditlog.AuditLogFieldsOfLogTestCase.testAuditLoggingFields(AuditLogFieldsOfLogTestCase.java:106)
> {noformat}
> message was (notice the extra "-" in front)
> {noformat}
> - {
> "type" : "core",
> "r/o" : false,
> "booting" : false,
> "version" : "9.0.0.Alpha1",
> "user" : "IAmAdmin",
> "domainUUID" : null,
> "access" : "NATIVE",
> "remote-address" : "127.0.0.1/127.0.0.1",
> "success" : true,
> "ops" : [{
> "operation" : "write-attribute",
> "address" : [
> {
> "core-service" : "management"
> },
> {
> "access" : "audit"
> },
> {
> "logger" : "audit-log"
> }
> ],
> "name" : "log-boot",
> "value" : true,
> "operation-headers" : {
> "caller-type" : "user",
> "access-mechanism" : "NATIVE"
> }
> }]
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFCORE-434) Fix AuditLogFieldsOfLogTestCase
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-434?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-3855 to WFCORE-434:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-434 (was: WFLY-3855)
Affects Version/s: (was: 9.0.0.Alpha1)
> Fix AuditLogFieldsOfLogTestCase
> -------------------------------
>
> Key: WFCORE-434
> URL: https://issues.jboss.org/browse/WFCORE-434
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
>
> Test started to fail with:
> {noformat}
> java.lang.IllegalArgumentException: Invalid character: -
> at org.jboss.dmr.JSONParserImpl.invalid(JSONParserImpl.java:136)
> at org.jboss.dmr.JSONParser.yyLex(JSONParser.java:596)
> at org.jboss.dmr.JSONParser.yyParse(JSONParser.java:662)
> at org.jboss.dmr.ModelNode.fromJSONString(ModelNode.java:1390)
> at org.jboss.as.test.manualmode.auditlog.AuditLogFieldsOfLogTestCase.testAuditLoggingFields(AuditLogFieldsOfLogTestCase.java:106)
> {noformat}
> message was (notice the extra "-" in front)
> {noformat}
> - {
> "type" : "core",
> "r/o" : false,
> "booting" : false,
> "version" : "9.0.0.Alpha1",
> "user" : "IAmAdmin",
> "domainUUID" : null,
> "access" : "NATIVE",
> "remote-address" : "127.0.0.1/127.0.0.1",
> "success" : true,
> "ops" : [{
> "operation" : "write-attribute",
> "address" : [
> {
> "core-service" : "management"
> },
> {
> "access" : "audit"
> },
> {
> "logger" : "audit-log"
> }
> ],
> "name" : "log-boot",
> "value" : true,
> "operation-headers" : {
> "caller-type" : "user",
> "access-mechanism" : "NATIVE"
> }
> }]
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFLY-3983) Unknown deployment type: resource-adapters when user click on resource adapter in admin console
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-3983?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-3983:
----------------------------------------
Heiko, this may very well be a resource-adapter subsystem problem, in which case please change the component to JCA and assign to Stefano Maestri.
> Unknown deployment type: resource-adapters when user click on resource adapter in admin console
> -----------------------------------------------------------------------------------------------
>
> Key: WFLY-3983
> URL: https://issues.jboss.org/browse/WFLY-3983
> Project: WildFly
> Issue Type: Bug
> Components: Web Console
> Affects Versions: JBoss AS7 7.2.0.Final
> Environment: JBOSS EAP 6.2 , Windows
> Reporter: Sri chilukuri
> Assignee: Heiko Braun
>
> We have myproduct.ear which is deployed in JBoss EAP 6.2. myproduct.ear contains following modules. All the modules are deployed and everything works as expected. We are having 'Unknown deployment type: resource-adapters' error message when we click on myproduct.ear.myadapter.rar in Runtime.Deployments.Available Deployments in Admin console. This is working fine in JBoss EAP 6.1 and issue is showing up from JBoss EAP 6.2 to wildfly-8.1.0.Final. myproduct.ear.myweb.war and myweb.war.mybeans.jar works as expected when user click on them.
> EAR modules:
> myproduct.ear
> ------ myweb.war
> ------ mybeans.jar
> -------myadapter.rar
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFLY-3983) Unknown deployment type: resource-adapters when user click on resource adapter in admin console
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-3983?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-3983:
-----------------------------------
Component/s: Web Console
> Unknown deployment type: resource-adapters when user click on resource adapter in admin console
> -----------------------------------------------------------------------------------------------
>
> Key: WFLY-3983
> URL: https://issues.jboss.org/browse/WFLY-3983
> Project: WildFly
> Issue Type: Bug
> Components: Web Console
> Affects Versions: JBoss AS7 7.2.0.Final
> Environment: JBOSS EAP 6.2 , Windows
> Reporter: Sri chilukuri
> Assignee: Jason Greene
>
> We have myproduct.ear which is deployed in JBoss EAP 6.2. myproduct.ear contains following modules. All the modules are deployed and everything works as expected. We are having 'Unknown deployment type: resource-adapters' error message when we click on myproduct.ear.myadapter.rar in Runtime.Deployments.Available Deployments in Admin console. This is working fine in JBoss EAP 6.1 and issue is showing up from JBoss EAP 6.2 to wildfly-8.1.0.Final. myproduct.ear.myweb.war and myweb.war.mybeans.jar works as expected when user click on them.
> EAR modules:
> myproduct.ear
> ------ myweb.war
> ------ mybeans.jar
> -------myadapter.rar
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFLY-3983) Unknown deployment type: resource-adapters when user click on resource adapter in admin console
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-3983?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-3983:
-----------------------------------
Assignee: Heiko Braun (was: Jason Greene)
> Unknown deployment type: resource-adapters when user click on resource adapter in admin console
> -----------------------------------------------------------------------------------------------
>
> Key: WFLY-3983
> URL: https://issues.jboss.org/browse/WFLY-3983
> Project: WildFly
> Issue Type: Bug
> Components: Web Console
> Affects Versions: JBoss AS7 7.2.0.Final
> Environment: JBOSS EAP 6.2 , Windows
> Reporter: Sri chilukuri
> Assignee: Heiko Braun
>
> We have myproduct.ear which is deployed in JBoss EAP 6.2. myproduct.ear contains following modules. All the modules are deployed and everything works as expected. We are having 'Unknown deployment type: resource-adapters' error message when we click on myproduct.ear.myadapter.rar in Runtime.Deployments.Available Deployments in Admin console. This is working fine in JBoss EAP 6.1 and issue is showing up from JBoss EAP 6.2 to wildfly-8.1.0.Final. myproduct.ear.myweb.war and myweb.war.mybeans.jar works as expected when user click on them.
> EAR modules:
> myproduct.ear
> ------ myweb.war
> ------ mybeans.jar
> -------myadapter.rar
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months