October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-689) Validation exit code incorrect

by Jesper Pedersen (Created) (JIRA)

Validation exit code incorrect ------------------------------ Key: JBJCA-689 URL: https://issues.jboss.org/browse/JBJCA-689 Project: IronJacamar Issue Type: Bug Components: Validator Affects Versions: 1.1.0.Alpha2, 1.0.5.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.6.Final, 1.1.0.Alpha3 The validation exit code is incorrect in case of a failure leading to wrong output in the command line client -- 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

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] (JBJCA-688) Non spec compliant feedback

by Jesper Pedersen (Created) (JIRA)

Non spec compliant feedback --------------------------- Key: JBJCA-688 URL: https://issues.jboss.org/browse/JBJCA-688 Project: IronJacamar Issue Type: Task Components: Deployer Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.6.Final, 1.1.0.Alpha3 Provide additional feedback during deployment why an admin object or connection factory wasn't bound in JNDI -- 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

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] (AS7-1565) modcluster Subsystem Errors with AS7 Domain Profile

by Jean-Frederic Clere (Resolved) (JIRA)

[ https://issues.jboss.org/browse/AS7-1565?page=com.atlassian.jira.plugin.s... ] Jean-Frederic Clere resolved AS7-1565. -------------------------------------- Resolution: Rejected that is normal those commands only work on a server instance. > modcluster Subsystem Errors with AS7 Domain Profile > --------------------------------------------------- > > Key: AS7-1565 > URL: https://issues.jboss.org/browse/AS7-1565 > Project: Application Server 7 > Issue Type: Bug > Reporter: Stefan Negrea > Assignee: Jean-Frederic Clere > > All the operations invoked on the modcluster subsystem after the server is started in domain mode fail. The subsystem is in the list of loaded subsystems however nothing works (included reading and writing attributes). Also, the subsystem does not connect to the httpd server. -- 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

12 years, 11 months

1
0
0 / 0

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

by Heiko Braun (Created) (JIRA)

Provide the ability to modify XA Datasource properties through the console -------------------------------------------------------------------------- Key: AS7-2240 URL: https://issues.jboss.org/browse/AS7-2240 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. 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

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1962) jboss-admin.sh looses partial functionality after running :read-ressource command

by Dan Sirbu (JIRA)

jboss-admin.sh looses partial functionality after running :read-ressource command --------------------------------------------------------------------------------- Key: AS7-1962 URL: https://issues.jboss.org/browse/AS7-1962 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.Alpha1 Reporter: Dan Sirbu Assignee: Heiko Braun Fix For: Open To Community I have developped my own subsytem and I start using :read-resource for example on my module. That work ok. Then I used :read-children-names on my subsystem which failed with: 14:03:58,330 INFO [com.xxx.dns.DnsAlarm] (pool-7-thread-1) DnsAlarm: clear DnsUnreachableAlarm 14:13:53,166 ERROR [org.jboss.as.controller] (pool-2-thread-9) Operation ("read-children-names") failed - address: ([("subsystem" => "xxx")]) - failure description: "child-type may not be null." Then I went into the osgi subsytem and run the same command. Got the same type of error: 14:14:39,463 ERROR [org.jboss.as.controller] (pool-2-thread-16) Operation ("read-children-names") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." BUT, I also got : 14:14:49,623 WARN [org.jboss.as.protocol] (pool-2-thread-11) Got error closing channel JBREM00206: Channel is not open And from this point on the jboss-admin.sh is no longer able to do a :read-resource I do not see why the communication link would become broken since I did not disconnect the jboss-admin. Not only that, if I reconnect back to the AS 7 I can no longer run the :read-resource on my subsystem, but then I can use it on the osgi until I create the same error. Once I do that I can go back into my subsystem and run the :read-resource again. So, kind of lost due to this unpredictability ..... 14:14:39,463 ERROR [org.jboss.as.controller] (pool-2-thread-16) Operation ("read-children-names") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:14:49,623 WARN [org.jboss.as.protocol] (pool-2-thread-11) Got error closing channel JBREM00206: Channel is not open 14:23:28,037 ERROR [org.jboss.as.controller] (pool-2-thread-20) Operation ("read-children-names") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:23:30,515 ERROR [org.jboss.as.controller] (pool-2-thread-17) Operation ("read-children-names") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:23:32,349 ERROR [org.jboss.as.controller] (pool-2-thread-19) Operation ("read-children-names") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:23:47,093 ERROR [org.jboss.as.controller] (pool-2-thread-17) Operation ("read-children-resources") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:23:49,113 ERROR [org.jboss.as.controller] (pool-2-thread-17) Operation ("read-children-resources") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:23:50,123 ERROR [org.jboss.as.controller] (pool-2-thread-23) Operation ("read-children-resources") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:23:50,481 ERROR [org.jboss.as.controller] (pool-2-thread-24) Operation ("read-children-resources") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:23:50,721 ERROR [org.jboss.as.controller] (pool-2-thread-20) Operation ("read-children-resources") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:23:50,954 ERROR [org.jboss.as.controller] (pool-2-thread-17) Operation ("read-children-resources") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:23:51,166 ERROR [org.jboss.as.controller] (pool-2-thread-20) Operation ("read-children-resources") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:23:51,374 ERROR [org.jboss.as.controller] (pool-2-thread-19) Operation ("read-children-resources") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:23:51,605 ERROR [org.jboss.as.controller] (pool-2-thread-19) Operation ("read-children-resources") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:23:51,813 ERROR [org.jboss.as.controller] (pool-2-thread-23) Operation ("read-children-resources") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:23:52,034 ERROR [org.jboss.as.controller] (pool-2-thread-19) Operation ("read-children-resources") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:23:52,298 ERROR [org.jboss.as.controller] (pool-2-thread-19) Operation ("read-children-resources") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:23:52,300 WARN [org.jboss.as.protocol] (pool-2-thread-24) Got error closing channel JBREM00206: Channel is not open 14:23:52,489 ERROR [org.jboss.as.controller] (pool-2-thread-24) Operation ("read-children-resources") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:23:52,713 ERROR [org.jboss.as.controller] (pool-2-thread-20) Operation ("read-children-resources") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:23:54,465 ERROR [org.jboss.as.controller] (pool-2-thread-19) Operation ("read-children-resources") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:23:58,297 ERROR [org.jboss.as.controller] (pool-2-thread-20) Operation ("read-children-resources") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:23:59,124 ERROR [org.jboss.as.controller] (pool-2-thread-20) Operation ("read-children-resources") failed - address: ([("subsystem" => "osgi")]) - failure description: "child-type may not be null." 14:24:02,680 WARN [org.jboss.as.protocol] (pool-2-thread-25) Got error closing channel JBREM00206: Channel is not open while suddenly I can can do again : [standalone@192.168.105.1:9999 subsystem=xxx] :read-resource { "outcome" => "success", "result" => { "activation" => "LAZY", "module" => { "com.xxx" => undefined, "com.xxx" => undefined } } } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

5
5
0 / 0

[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

12 years, 11 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

12 years, 11 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

12 years, 11 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

12 years, 11 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

12 years, 11 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 October 2011