December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3019) Shutdown on startup error

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3019?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-3019: ----------------------------------- Component/s: Domain Management > Shutdown on startup error > ------------------------- > > Key: WFLY-3019 > URL: https://issues.jboss.org/browse/WFLY-3019 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Takayoshi Kimura > > Currently WildFly starts and up running although it got critical errors during boot. > For example, 8080 port is being used by the other process and undertow subsystem was not functioning, transaction manager and logging subsystems are failed to boot due to file permission error, or someone started the instance twice by mistake. > It would be nice if we can have an option to trigger shutdown the non-healthy instance in these boot error situations, for subsystem level errors and for deployment errors. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-436) Shutdown on startup error

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-436?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-3019 to WFCORE-436: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-436 (was: WFLY-3019) Affects Version/s: (was: 8.0.0.Final) Component/s: Domain Management (was: Domain Management) > Shutdown on startup error > ------------------------- > > Key: WFCORE-436 > URL: https://issues.jboss.org/browse/WFCORE-436 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Takayoshi Kimura > > Currently WildFly starts and up running although it got critical errors during boot. > For example, 8080 port is being used by the other process and undertow subsystem was not functioning, transaction manager and logging subsystems are failed to boot due to file permission error, or someone started the instance twice by mistake. > It would be nice if we can have an option to trigger shutdown the non-healthy instance in these boot error situations, for subsystem level errors and for deployment errors. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-435) Add MBean server support to Management console

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-435?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-3426 to WFCORE-435: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-435 (was: WFLY-3426) > Add MBean server support to Management console > ---------------------------------------------- > > Key: WFCORE-435 > URL: https://issues.jboss.org/browse/WFCORE-435 > Project: WildFly Core > Issue Type: Feature Request > Reporter: Sebastian Łaskawiec > Assignee: Jason Greene > Priority: Minor > > In JBoss 5.x server there was a web based tool for managing JMX Beans. Currently this functionality is supported via bundled JConsole. It would be convenient to have such functionality based on HTTP Web Management panel. > As discussed on email thread (subject: "JMX Console over Web Admin Console") it should be placed a part of standard management resource tree or in context of HTTP management interface. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3653) Managed Executors: unhandled exceptions should be logged

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3653?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-3653: ----------------------------------- Component/s: EE > Managed Executors: unhandled exceptions should be logged > -------------------------------------------------------- > > Key: WFLY-3653 > URL: https://issues.jboss.org/browse/WFLY-3653 > Project: WildFly > Issue Type: Enhancement > Components: EE > Affects Versions: 8.1.0.Final > Reporter: Rich DiCroce > Assignee: Jason Greene > > If you submit a task to a ManagedExecutorService, and the task throws an exception that propagates out of the task, the exception is not logged anywhere. Obviously, developers can simply wrap their task's code with a try-catch, but it would be nice if that were not needed. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[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)

9 years, 7 months

1
0
0 / 0

[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)

9 years, 7 months

1
0
0 / 0

[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)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3832) Upgrade JBMETA to 8.0.1.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3832?page=com.atlassian.jira.plugin.... ] Brian Stansberry edited comment on WFLY-3832 at 12/1/14 6:35 PM: ----------------------------------------------------------------- The WFLY-4117 patch brought jboss-metadata to 8.2.1.Final. was (Author: brian.stansberry): The WFLY-4117 brought jboss-metadata to 8.2.1.Final. > Upgrade JBMETA to 8.0.1.Final > ----------------------------- > > Key: WFLY-3832 > URL: https://issues.jboss.org/browse/WFLY-3832 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Bartosz Baranowski > Assignee: Jason Greene > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3832) Upgrade JBMETA to 8.0.1.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3832?page=com.atlassian.jira.plugin.... ] Brian Stansberry resolved WFLY-3832. ------------------------------------ Resolution: Out of Date The WFLY-4117 brought jboss-metadata to 8.2.1.Final. > Upgrade JBMETA to 8.0.1.Final > ----------------------------- > > Key: WFLY-3832 > URL: https://issues.jboss.org/browse/WFLY-3832 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Bartosz Baranowski > Assignee: Jason Greene > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[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)

9 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2014