October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2135) :reload gives xml persistence exception

by Nicklas Karlsson (Created) (JIRA)

:reload gives xml persistence exception --------------------------------------- Key: AS7-2135 URL: https://issues.jboss.org/browse/AS7-2135 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.Alpha1 Environment: Win 7 Reporter: Nicklas Karlsson Assignee: Alexey Loubyansky start CLI on a fresh AS and do :reload and you'll get a 21:09:39,415 ERROR [org.jboss.as.controller] Failed to persist configuration change: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to marshal configuration at org.jboss.as.controller.persistence.FilePersistenceResource.<init>(FilePersistenceResource.java:62) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.persistence.ConfigurationFilePersistenceResource.<init>(ConfigurationFilePersistenceResource.java:39) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.persistence.BackupXmlConfigurationPersister.store(BackupXmlConfigurationPersister.java:80) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.ModelControllerImpl.writeModel(ModelControllerImpl.java:282) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.OperationContextImpl.doCompleteStep(OperationContextImpl.java:312) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.OperationContextImpl.completeStep(OperationContextImpl.java:219) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.OperationContextImpl.executeStep(OperationContextImpl.java:440) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.OperationContextImpl.doCompleteStep(OperationContextImpl.java:285) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.OperationContextImpl.completeStep(OperationContextImpl.java:219) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.operations.global.WriteAttributeHandlers$WriteAttributeOperationHandler.modelChanged(WriteAttributeHandlers.java:123) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.operations.global.WriteAttributeHandlers$WriteAttributeOperationHandler.execute(WriteAttributeHandlers.java:90) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.operations.global.GlobalOperationHandlers$WriteAttributeHandler.execute(GlobalOperationHandlers.java:487) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.OperationContextImpl.executeStep(OperationContextImpl.java:386) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.OperationContextImpl.doCompleteStep(OperationContextImpl.java:285) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.OperationContextImpl.completeStep(OperationContextImpl.java:219) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:167) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:173) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.server.ServerService.boot(ServerService.java:208) at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:168) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.server.ServerService.boot(ServerService.java:197) at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:133) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at java.lang.Thread.run(Thread.java:662) [:1.6.0_27] Caused by: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to write configuration at org.jboss.as.controller.persistence.AbstractConfigurationPersister.marshallAsXml(AbstractConfigurationPersister.java:109) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.persistence.FilePersistenceResource.<init>(FilePersistenceResource.java:55) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] ... 21 more Caused by: java.lang.IllegalArgumentException at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:124) [jboss-dmr-1.0.0.Final.jar:1.0.0.Final] at org.jboss.dmr.ModelNode.keys(ModelNode.java:1085) [jboss-dmr-1.0.0.Final.jar:1.0.0.Final] at org.jboss.as.controller.parsing.StandaloneXml.writeServerProfile(StandaloneXml.java:563) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.parsing.StandaloneXml.writeContent(StandaloneXml.java:499) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.parsing.StandaloneXml.writeContent(StandaloneXml.java:82) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.staxmapper.XMLMapperImpl.doDeparse(XMLMapperImpl.java:78) [staxmapper-1.0.0.Final.jar:1.0.0.Final] at org.jboss.staxmapper.XMLMapperImpl.deparseDocument(XMLMapperImpl.java:73) [staxmapper-1.0.0.Final.jar:1.0.0.Final] at org.jboss.as.controller.persistence.AbstractConfigurationPersister.marshallAsXml(AbstractConfigurationPersister.java:103) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] ... 22 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
2
0 / 0

[JBoss JIRA] (AS7-2225) possibility to adjust/correct attribute value before it's set

by Alexey Loubyansky (Created) (JIRA)

possibility to adjust/correct attribute value before it's set ------------------------------------------------------------- Key: AS7-2225 URL: https://issues.jboss.org/browse/AS7-2225 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky If an attribute expects values consisting of multiple properties than the user is expected to specify all those properties for every write-attribute. In some cases, when the majority of those properties are changed infrequently but the minority is changed much more often, it is not user friendly to require a user to specify the complete value every time. There could be a value adjusting mechanism that would fill-in the missing properties of the new values based on those present in the current attribute value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-874) Provide the ability to modify XA Datasource properties through the console

by Heiko Braun (JIRA)

Provide the ability to modify XA Datasource properties through the console -------------------------------------------------------------------------- Key: AS7-874 URL: https://issues.jboss.org/browse/AS7-874 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
3
0 / 0

[JBoss JIRA] Created: (AS7-1985) Ability to specify datasource connection properties from the console

by Heiko Braun (JIRA)

Ability to specify datasource connection properties from the console -------------------------------------------------------------------- Key: AS7-1985 URL: https://issues.jboss.org/browse/AS7-1985 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
3
0 / 0

[JBoss JIRA] (AS7-2238) CLONE - Domain process is running in loop when invalid host or domain configuration is specified, process must be killed using -9

by Rostislav Svoboda (Created) (JIRA)

CLONE - Domain process is running in loop when invalid host or domain configuration is specified, process must be killed using -9 --------------------------------------------------------------------------------------------------------------------------------- Key: AS7-2238 URL: https://issues.jboss.org/browse/AS7-2238 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Rostislav Svoboda Assignee: Brian Stansberry Fix For: 7.1.0.Beta1 Domain process is running in loop when invalid host or domain configuration is specified. CPU is luckily not exhausted but process is still running. Command 'kill -9 PID' must be used to stop domain, Ctrl+C isn't working. {code} bin/domain.sh --host-config=foo.xml bin/domain.sh --domain-config=foo.xml {code} Process of standalone server ends correctly when invalid server configuration is specified. {code} bin/standalone.sh --server-config=foo.xml {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-2236) A resource-env-ref without injection targets must be bindable

by Carlo de Wolf (Created) (JIRA)

A resource-env-ref without injection targets must be bindable ------------------------------------------------------------- Key: AS7-2236 URL: https://issues.jboss.org/browse/AS7-2236 Project: Application Server 7 Issue Type: Bug Components: EE Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical {noformat} Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Could not determine type for resource-env-ref java:comp/env/dog at org.jboss.as.ee.component.deployers.ResourceReferenceProcessor.getResourceEnvRefEntries(ResourceReferenceProcessor.java:86) at org.jboss.as.ee.component.deployers.ResourceReferenceProcessor.processDescriptorEntries(ResourceReferenceProcessor.java:55) at org.jboss.as.ee.component.deployers.AbstractDeploymentDescriptorBindingsProcessor.deploy(AbstractDeploymentDescriptorBindingsProcessor.java:103) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] ... 5 more {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (AS7-1410) Expose runtime OSGi management configuration through console

by David Bosschaert (JIRA)

Expose runtime OSGi management configuration through console ------------------------------------------------------------ Key: AS7-1410 URL: https://issues.jboss.org/browse/AS7-1410 Project: Application Server 7 Issue Type: Sub-task Components: Console Reporter: David Bosschaert Assignee: David Bosschaert Fix For: 7.1.0.CR1 Bundle runtime management should be exposed through the console. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (AS7-769) Expose transaction manager though web management interface

by Heiko Braun (JIRA)

Expose transaction manager though web management interface ---------------------------------------------------------- Key: AS7-769 URL: https://issues.jboss.org/browse/AS7-769 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management, Transactions Reporter: Heiko Braun Assignee: Jason Greene -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

5
11
0 / 0

[JBoss JIRA] Created: (AS7-1782) Provide management use cases and operations for the transaction subsystem

by Heiko Braun (JIRA)

Provide management use cases and operations for the transaction subsystem ------------------------------------------------------------------------- Key: AS7-1782 URL: https://issues.jboss.org/browse/AS7-1782 Project: Application Server 7 Issue Type: Feature Request Components: Transactions Reporter: Heiko Braun Assignee: Jonathan Halliday Fix For: 7.1.0.Beta1 I cannot identify the use cases not the operation when looking at the current management exposure: {noformat} [standalone@localhost:9999 /] /subsystem=transactions:read-resource(recursive=true) { "outcome" => "success", "result" => { "coordinator-environment" => { "enable-statistics" => undefined, "enable-tsm-status" => undefined, "default-timeout" => 300 }, "core-environment" => { "process-id" => {"uuid" => "uuid"}, "node-identifier" => undefined, "relative-to" => undefined, "path" => undefined }, "object-store" => { "relative-to" => undefined, "path" => undefined }, "recovery-environment" => { "socket-binding" => "txn-recovery-environment", "status-socket-binding" => "txn-status-manager", "recovery-listener" => undefined } } } [standalone@localhost:9999 /] /subsystem=transactions:read-operation- read-operation-description read-operation-names [standalone@localhost:9999 /] /subsystem=transactions:read-operation-names { "outcome" => "success", "result" => [ "add", "read-attribute", "read-children-names", "read-children-resources", "read-children-types", "read-operation-description", "read-operation-names", "read-resource", "read-resource-description", "validate-address", "write-attribute" ] } {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

5
8
0 / 0

[JBoss JIRA] (AS7-2235) Framework properties not writable

by Thomas Diesler (Created) (JIRA)

Framework properties not writable --------------------------------- Key: AS7-2235 URL: https://issues.jboss.org/browse/AS7-2235 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.1.0.Beta1 [standalone@localhost:9999 /] /subsystem=osgi/property=org.osgi.framework.startlevel.beginning:write-attribute(name=value,value=2) { "outcome" => "failed", "failure-description" => "Attribute value is not writeable", "rolled-back" => true } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 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 October 2011