October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2143) CLONE - Command :reload breaks standalone server, IllegalArgumentException

by Rostislav Svoboda (Created) (JIRA)

CLONE - Command :reload breaks standalone server, IllegalArgumentException -------------------------------------------------------------------------- Key: AS7-2143 URL: https://issues.jboss.org/browse/AS7-2143 Project: Application Server 7 Issue Type: Bug Components: CLI, Server Affects Versions: 7.1.0.Alpha1 Reporter: Rostislav Svoboda Assignee: Brian Stansberry Fix For: 7.1.0.CR1 Invoking just :reload command in CLI breaks standalone server instance, no service is running and you must press Ctrl+C or kill java process. Tested with latest build from source codes pulled on 2011-10-18, I just started server and invoked reload command. Invoking '~/TESTING/jboss-as7/bin/jboss-admin.sh -c controller=10.34.3.154 --command=:reload' caused this on server side: {code} 14:34:00,620 INFO [jacorb.orb] ORB going down... 14:34:00,628 INFO [jacorb.orb.iiop] Listener exited 14:34:00,629 INFO [jacorb.orb] ORB shutdown complete 14:34:00,629 INFO [jacorb.orb] ORB run, exit 14:34:00,630 INFO [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server version 2.2.7.Final (HQ_2_2_7_FINAL_AS7, 121) [036ed48f-f980-11e0-8e7f-42a81bcb9cc4] stopped 14:34:00,636 INFO [org.jboss.as.mail.extension.MailSessionAdd] Unbound mail session [java:jboss/mail/Default] 14:34:00,637 INFO [org.jboss.as.connector.subsystems.datasources] JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS] 14:34:00,649 INFO [org.jboss.as] JBoss AS 7.1.0.Alpha2-SNAPSHOT "Ahoy!" stopped in 76ms 14:34:00,650 INFO [org.jboss.as] JBoss AS 7.1.0.Alpha2-SNAPSHOT "Ahoy!" starting 14:34:00,722 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_22] 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 14:34:00,724 INFO [org.jboss.as] JBoss AS 7.1.0.Alpha2-SNAPSHOT "Ahoy!" started in 74ms - Started 18 of 19 services (1 services are passive or on-demand) {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, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-2144) CLONE - Attribute socket-binding-port-offset for server-group cannot be set to 0

by Rostislav Svoboda (Created) (JIRA)

CLONE - Attribute socket-binding-port-offset for server-group cannot be set to 0 -------------------------------------------------------------------------------- Key: AS7-2144 URL: https://issues.jboss.org/browse/AS7-2144 Project: Application Server 7 Issue Type: Bug Components: CLI, Domain Management Affects Versions: 7.1.0.Alpha1 Reporter: Rostislav Svoboda Assignee: Brian Stansberry Fix For: 7.1.0.CR1 Issue met when invoking these operations in CLI: /server-group=main-server-group:write-attribute(name="socket-binding-port-offset", value=100) /host=master/server-config=server-one:restart /server-group=main-server-group:write-attribute(name="socket-binding-port-offset", value=0) { "outcome" => "failed", "failure-description" => {"domain-failure-description" => "0 is an invalid value for parameter socket-binding-port-offset. A minimum value of 1 is required"}, "rolled-back" => true } In standard distribution there is no port offset defined for /server-group=main-server-group. Tested with latest build from source codes pulled on 2011-10-18. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-2145) CLONE - CLI: missing :remove-attribute command

by Rostislav Svoboda (Created) (JIRA)

CLONE - CLI: missing :remove-attribute command ---------------------------------------------- Key: AS7-2145 URL: https://issues.jboss.org/browse/AS7-2145 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.Alpha1 Reporter: Rostislav Svoboda Assignee: Alexey Loubyansky Fix For: 7.1.0.CR1 We have _:read-attribute_ and _:write-attribute_ commands but we do not have *:remove-attribute* command. It would be invoked on attributes which have flag required set to false. For example when I define socket-binding-port-offset for server-group I can't remove it and I can't set it to 0 using CLI. {code} /server-group=main-server-group:read-resource-description() "socket-binding-port-offset" => { "description" => "The default offset to be added to the port values given by the socket binding group.", "type" => INT, "required" => false, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }, {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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-1100) ENCRYPT debug log prints "hex" output in ambiguous format

by Dennis Reed (JIRA)

ENCRYPT debug log prints "hex" output in ambiguous format --------------------------------------------------------- Key: JGRP-1100 URL: https://jira.jboss.org/jira/browse/JGRP-1100 Project: JGroups Issue Type: Bug Affects Versions: 2.4.7 Reporter: Dennis Reed Assignee: Dennis Reed ENCRYPT.formatArray doesn't convert a byte array straight to hex. It leaves off any leading 0 in a byte and appends ffffff in front of any negative byte. This prevents the original data from easily being reconstructed from the log for debugging purposes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
12
0 / 0

[JBoss JIRA] Created: (AS7-1889) Failed to update messaging attribute "message-counter-enabled"

by Heiko Braun (JIRA)

Failed to update messaging attribute "message-counter-enabled" -------------------------------------------------------------- Key: AS7-1889 URL: https://issues.jboss.org/browse/AS7-1889 Project: Application Server 7 Issue Type: Bug Components: JMS Reporter: Heiko Braun Assignee: Clebert Suconic Fix For: 7.1.0.Alpha1 {noformat} { "outcome" => "failed", "result" => {"step-1" => { "outcome" => "failed", "failure-description" => "Operation handler failed: java.lang.IllegalStateException: Get service registry only supported in runtime operations", "rolled-back" => true }}, "failure-description" => {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "Operation handler failed: java.lang.IllegalStateException: Get service registry only supported in runtime operations"}}, "rolled-back" => true, "response-headers" => {"process-state" => "reload-required"} } 14:46:26,762 ERROR [org.jboss.as.controller] (HttpManagementService-threads - 38) Operation ("write-attribute") failed - address: ([ ("subsystem" => "messaging"), ("hornetq-server" => "default") ]): java.lang.IllegalStateException: Get service registry only supported in runtime operations at org.jboss.as.controller.OperationContextImpl.getServiceRegistry(OperationContextImpl.java:562) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
3
0 / 0

[JBoss JIRA] Created: (AS7-1301) Update OSGi to be compatible with JBoss Modules 1.1 series

by David Lloyd (JIRA)

Update OSGi to be compatible with JBoss Modules 1.1 series ---------------------------------------------------------- Key: AS7-1301 URL: https://issues.jboss.org/browse/AS7-1301 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: David Lloyd Assignee: Thomas Diesler Fix For: 7.1.0.Alpha1 JBoss Modules 1.1 has two significant changes. First, jaxpmodule is eliminated. Second, the system module is no more - instead there's a dependency type for the system class loader. I currently have an updated AS in my http://github.com/dmlloyd/jboss-as/tree/upgrades branch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

5
19
0 / 0

[JBoss JIRA] Created: (AS7-1376) Implement EE.10 Application Clients

by Carlo de Wolf (JIRA)

Implement EE.10 Application Clients ----------------------------------- Key: AS7-1376 URL: https://issues.jboss.org/browse/AS7-1376 Project: Application Server 7 Issue Type: Task Components: EE Reporter: Carlo de Wolf Assignee: David Lloyd Priority: Critical Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
3
0 / 0

[JBoss JIRA] Created: (AS7-1876) Field type resolution in @Resource doesn't occur (<env-entry-type> in ejb-jar.xml is required)

by Pedro Kowalski (JIRA)

Field type resolution in @Resource doesn't occur (<env-entry-type> in ejb-jar.xml is required) ---------------------------------------------------------------------------------------------- Key: AS7-1876 URL: https://issues.jboss.org/browse/AS7-1876 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.0.1.Final Environment: GNU/Linux Ubuntu 11.04 x86 Reporter: Pedro Kowalski Assignee: Carlo de Wolf While using @Resource on a field in EJB and defining it's value in ejb-jar.xml, the field type doesn't seem to be automatically resolved. It must be explicitly defined using <env-entry-type>. I attach exemplary application (+ sources) here: http://community.jboss.org/servlet/JiveServlet/download/627566-41282/ENVT... The deployment will fail if the following line is commented: <env-entry-type>java.lang.String</env-entry-type> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Could not determine type for <env-entry> java:comp/env/myEntry please specify the <env-entry-type>. After uncommenting it, the deployment runs fine. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
5
0 / 0

[JBoss JIRA] (AS7-2048) WAR uses filter of another WAR in the same EAR

by Sebastian Woeste (Created) (JIRA)

WAR uses filter of another WAR in the same EAR ---------------------------------------------- Key: AS7-2048 URL: https://issues.jboss.org/browse/AS7-2048 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.0.2.Final, 7.0.1.Final, 7.0.0.Final Reporter: Sebastian Woeste Assignee: Jason Greene I have an EAR with to WARs in it. Both WARs contain a JAR (in they're lib folder) which contain a Filter. If i deploy the EAR and log the loaded classes i see that the filter from both WARs are loaded but if i open the web context then only the first loaded filter will be used - for both WARs. This will lead to some classloading problems in the following process. For a more detailed description see the forum reference. -- 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, 8 months

3
2
0 / 0

[JBoss JIRA] (AS7-2087) May sure weld injects a remote proxy for remote interfaces

by Stuart Douglas (Created) (JIRA)

May sure weld injects a remote proxy for remote interfaces ---------------------------------------------------------- Key: AS7-2087 URL: https://issues.jboss.org/browse/AS7-2087 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld Affects Versions: 7.1.0.Alpha1 Reporter: Stuart Douglas Assignee: Stuart Douglas -- 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, 8 months

2
1
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