April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9112) Create an "operation-header" section in operation requests

by Brian Stansberry (JIRA)

Create an "operation-header" section in operation requests ---------------------------------------------------------- Key: JBAS-9112 URL: https://issues.jboss.org/browse/JBAS-9112 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.Beta2 For the oddball stuff that goes along with some ops: "operation-headers"=>{"rollout-plan"=>{..},"rollback-on-runtime-failure"=>false, "ignore-restart-required"=>true,...} "operation" and "address" would not move -- too disruptive -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-9195) Incomplete warning message when starting a started server

by Heiko Rupp (JIRA)

Incomplete warning message when starting a started server --------------------------------------------------------- Key: JBAS-9195 URL: https://issues.jboss.org/browse/JBAS-9195 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta1 Reporter: Heiko Rupp Priority: Minor When issuing a start request on an already started server, the following message shows up in the server log [Host Controller] 22:33:04,244 WARN [org.jboss.as.host.controller] (pool-1-thread-7) existing server [%s] with state: STARTED Note the %s, which is probably supposed to be replaced by the server name -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-9225) LOOPBACK_ADDRESS handling missing from CommonXml.writePropertyInterfaceCriteria

by Scott Stark (JIRA)

LOOPBACK_ADDRESS handling missing from CommonXml.writePropertyInterfaceCriteria ------------------------------------------------------------------------------- Key: JBAS-9225 URL: https://issues.jboss.org/browse/JBAS-9225 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta2 Reporter: Scott Stark Assignee: Scott Stark Fix For: 7.0.0.Beta3 Support for a loopback-address criterion was added to the CommonXml.parseSimpleInterfaceCriterion, but the writing of this was not added to the CommonXml.writePropertyInterfaceCriteria, so when the standard.xml configuration is persisted, the following error is seen: 10:58:21,807 WARN [org.jboss.as.controller] (pool-6-thread-2) Failed to persist configuration change: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to store configuration: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to store configuration at org.jboss.as.controller.persistence.XmlConfigurationPersister.store(XmlConfigurationPersister.java:97) at org.jboss.as.controller.BasicModelController.persistConfiguration(BasicModelController.java:308) at org.jboss.as.server.ServerControllerImpl.persistConfiguration(ServerControllerImpl.java:215) at org.jboss.as.controller.BasicModelController$MultiStepOperationController.updateModelAndPersist(BasicModelController.java:668) at org.jboss.as.controller.BasicModelController$MultiStepOperationController.recordModelComplete(BasicModelController.java:652) at org.jboss.as.server.ServerControllerImpl$ServerMultiStepOperationController.recordModelComplete(ServerControllerImpl.java:475) at org.jboss.as.controller.BasicModelController$MultiStepOperationController.execute(BasicModelController.java:707) at org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:248) at org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:216) at org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:77) at org.jboss.as.controller.SynchronousOperationSupport.execute(SynchronousOperationSupport.java:88) at org.jboss.as.controller.AbstractModelController.execute(AbstractModelController.java:40) at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$DeploymentTask.call(FileSystemDeploymentService.java:1052) at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$DeploymentTask.call(FileSystemDeploymentService.java:1043) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [:1.6.0_17] at java.util.concurrent.FutureTask.run(FutureTask.java:166) [:1.6.0_17] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165) [:1.6.0_17] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266) [:1.6.0_17] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_17] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_17] at java.lang.Thread.run(Thread.java:636) [:1.6.0_17] Caused by: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to write configuration at org.jboss.as.controller.persistence.AbstractConfigurationPersister.marshallAsXml(AbstractConfigurationPersister.java:108) at org.jboss.as.controller.persistence.XmlConfigurationPersister.store(XmlConfigurationPersister.java:90) ... 20 more Caused by: java.lang.RuntimeException: Unknown property in interface criteria list: org.jboss.dmr.Property@fbb8694 at org.jboss.as.controller.parsing.CommonXml.writePropertyInterfaceCriteria(CommonXml.java:1311) at org.jboss.as.controller.parsing.CommonXml.writeInterfaceCriteria(CommonXml.java:1277) at org.jboss.as.controller.parsing.CommonXml.writeInterfaces(CommonXml.java:1262) at org.jboss.as.controller.parsing.StandaloneXml.writeContent(StandaloneXml.java:435) at org.jboss.as.controller.parsing.StandaloneXml.writeContent(StandaloneXml.java:77) at org.jboss.staxmapper.XMLMapperImpl.doDeparse(XMLMapperImpl.java:78) at org.jboss.staxmapper.XMLMapperImpl.deparseDocument(XMLMapperImpl.java:73) at org.jboss.as.controller.persistence.AbstractConfigurationPersister.marshallAsXml(AbstractConfigurationPersister.java:102) ... 21 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-8411) Interface specified at host level but not at domain is accepted

by Brian Stansberry (JIRA)

Interface specified at host level but not at domain is accepted --------------------------------------------------------------- Key: JBAS-8411 URL: https://jira.jboss.org/browse/JBAS-8411 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.M1 The current build/src/main/resources/domain/configuration/host.xml includes the declaration of an <interface name="public" at the host level and that interface is not declared in the domain. It's used in the <domain-controller><local> element but I think it should be required to be declared there. Interfaces directly under host should be used to clarify the host-specific IP address mapping for stuff declared in domain.xml. If the address name is only used in the DC config, then declare it there. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-9093) Support choosing a configuration from the command line

by Brian Stansberry (JIRA)

Support choosing a configuration from the command line ------------------------------------------------------ Key: JBAS-9093 URL: https://issues.jboss.org/browse/JBAS-9093 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta4 Use of "domain.xml", "host.xml" and "standalone.xml" should be defaults, changeable from the command line. This facilitates shipping different standard configurations, e.g. with our without clustering, "development" vs "production" in EAP etc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8550) Filesystem deployment service should use a different marker file for failed deployments

by Brian Stansberry (JIRA)

Filesystem deployment service should use a different marker file for failed deployments --------------------------------------------------------------------------------------- Key: JBAS-8550 URL: https://jira.jboss.org/browse/JBAS-8550 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.M2 >From Jesper Pedersen: Shouldn't a deployment which fails be called .failed instead of .deployed ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-8795) Allow the plan for executing an operation to specify a list of required hosts / servers

by Brian Stansberry (JIRA)

Allow the plan for executing an operation to specify a list of required hosts / servers --------------------------------------------------------------------------------------- Key: JBAS-8795 URL: https://issues.jboss.org/browse/JBAS-8795 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta1 This is to record an idea for future consideration. When a client submits an operation to the domain or host controller, it can include rules for how many servers the operation can fail on within a server group before the operation is reverted across the server group. Add the ability to specify a list of servers and or hosts where the operation must succeed. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-9226) FileSystemDeploymentService: applications cannot be undeployed by removing .deployed marker

by Shelly McGowan (JIRA)

FileSystemDeploymentService: applications cannot be undeployed by removing .deployed marker -------------------------------------------------------------------------------------------- Key: JBAS-9226 URL: https://issues.jboss.org/browse/JBAS-9226 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Shelly McGowan To undeploy an application using File System deployment, the application's associated .deployed marker needs to be removed. Once the .deployed marker is deleted, the application is stopped but then immediately readded/restarted without triggering it with a .dodeploy marker. I've attached a .war to reproduce. Copy servlet_js_servlet_web.war $JBOSS_HOME/standalone/deployments touch servlet_js_servlet_web.war.dodeploy rm servlet_js_servlet_web.war.deployed The .war can never be undeployed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8997) Use of single thread executor with implied default thread factory in jboss-as-naming

by David Lloyd (JIRA)

Use of single thread executor with implied default thread factory in jboss-as-naming ------------------------------------------------------------------------------------ Key: JBAS-8997 URL: https://issues.jboss.org/browse/JBAS-8997 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.Beta3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8998) Use of default thread factory in jboss-as-process-controller

by David Lloyd (JIRA)

Use of default thread factory in jboss-as-process-controller ------------------------------------------------------------ Key: JBAS-8998 URL: https://issues.jboss.org/browse/JBAS-8998 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.Beta3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2011