December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4088) Add system properties for commonly parameterized mod_cluster configuration.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4088?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4088: ---------------------------------- Parent: AS7-6120 Issue Type: Sub-task (was: Feature Request) > Add system properties for commonly parameterized mod_cluster configuration. > --------------------------------------------------------------------------- > > Key: AS7-4088 > URL: https://issues.jboss.org/browse/AS7-4088 > Project: Application Server 7 > Issue Type: Sub-task > Components: Clustering, Domain Management > Affects Versions: 7.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 7.2.0.Alpha1 > > > Add properties for: > jboss.mod_cluster.advertise.address > jboss.mod_cluster.advertise.port > jboss.mod_cluster.balancer > jboss.mod_cluster.load-balancing-group > jboss.mod_cluster.proxy-list -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-2705) .deployed sticks around

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-2705?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-2705: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.Alpha1) > .deployed sticks around > ----------------------- > > Key: AS7-2705 > URL: https://issues.jboss.org/browse/AS7-2705 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.0.Alpha1 > Reporter: Jesper Pedersen > Fix For: 7.3.0.Alpha1 > > > Steps: > 1) cp successful.rar /path/to/jbossas7/standalone/deployments > 2) touch /path/to/jbossas7/standalone/deployments/successful.rar.dodeploy > .rar deploys with issues => .deployed > 3) Ctrl+C > The .deployed file is still there -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-2967) Remove workaround for shutting down the ModelControllerClientOperationHandlers

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-2967?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-2967: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.Alpha1) > Remove workaround for shutting down the ModelControllerClientOperationHandlers > ------------------------------------------------------------------------------ > > Key: AS7-2967 > URL: https://issues.jboss.org/browse/AS7-2967 > Project: Application Server 7 > Issue Type: Sub-task > Components: Domain Management > Affects Versions: 7.1.0.CR1 > Reporter: Emanuel Muckenhuber > Fix For: 7.3.0.Alpha1 > > > Once the graceful shutdown API is in place we need to cleanup the way the ModelControllerClientOperationHandler channels are closed. Currently we are waiting for all current operations to complete, in order that the response for :reload / :shutdown operations are sent. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-1221) HTTP management API section in the Admin Guide

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-1221?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-1221: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.Alpha1) > HTTP management API section in the Admin Guide > ---------------------------------------------- > > Key: AS7-1221 > URL: https://issues.jboss.org/browse/AS7-1221 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 7.3.0.Alpha1 > > > We need a technical guide to the HTTP management API. > The "Management clients" section gives a basic overview. But it should reference a separate section that documents the usage of GET and POST, the URL patterns, the JSON representation of DMR etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-1219) Add jboss-dmr documentation to the Admin Guide

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-1219?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-1219: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.Alpha1) > Add jboss-dmr documentation to the Admin Guide > ---------------------------------------------- > > Key: AS7-1219 > URL: https://issues.jboss.org/browse/AS7-1219 > Project: Application Server 7 > Issue Type: Task > Components: Documentation, Domain Management > Reporter: Brian Stansberry > Fix For: 7.3.0.Alpha1 > > > Basic documentation on DMR: > 1) Purpose > 2) Source location and maven coordinates > 3) Description of the 2 public classes, ModelNode and ModelType, link to 1.0.0.Final code for each on github > 4) Some simple examples > 5) Fully document the string format, so people know how to read DMR output and how to write DMR input > 6) Links to 5) above in the CLI docs, both in a place that describes how to read output and in a place that describes the format for parameter values in low-level operation requests -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-1535) More management operations for timers

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-1535?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-1535: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.CR1) > More management operations for timers > ------------------------------------- > > Key: AS7-1535 > URL: https://issues.jboss.org/browse/AS7-1535 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management, EJB > Reporter: Stuart Douglas > Assignee: Bartosz Baranowski > Fix For: 7.3.0.Alpha1 > > > Using the management api it should be possible to perform additional operations on timers such as: > suspending > cancelling > invoking a timeout method -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-444) Audit logging

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-444?page=com.atlassian.jira.plugin.sy... ] Brian Stansberry updated AS7-444: --------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.CR1) > Audit logging > ------------- > > Key: AS7-444 > URL: https://issues.jboss.org/browse/AS7-444 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Critical > Fix For: 7.3.0.Alpha1 > > > All modifications through the administrative infrastructure will be audited. The administrative audit log will be tamper proof. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-947) Managed domain server :reload() operation

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-947?page=com.atlassian.jira.plugin.sy... ] Brian Stansberry updated AS7-947: --------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.Alpha1) > Managed domain server :reload() operation > ----------------------------------------- > > Key: AS7-947 > URL: https://issues.jboss.org/browse/AS7-947 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Emanuel Muckenhuber > Fix For: 7.3.0.Alpha1 > > > Reloading yields an exception: > /host=local/server=server-one:reload > {noformat} > [Host Controller] 12:32:50,188 ERROR [org.jboss.as.host.controller] (pool-1-thread-24) Could not start server Server:server-one: java.lang.IllegalArgumentException: A node is already registered at '(server => server-one)' > [Host Controller] at org.jboss.as.controller.registry.NodeSubregistry.registerProxyController(NodeSubregistry.java:89) [jboss-as-controller-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT] > {noformat} > A second operation request results in "broken pipe": > {noformat} > [Host Controller] 12:33:03,025 ERROR [org.jboss.as.protocol] (ModelControllerClient-thread - 1) Failed to close resource org.jboss.as.protocol.SimpleByteDataOutput@37c398e: java.net.SocketException: Broken pipe > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-2322) Stack trace improvements, summarize the things that broke to make them not so intimidating

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-2322?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-2322: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.Alpha1) > Stack trace improvements, summarize the things that broke to make them not so intimidating > ------------------------------------------------------------------------------------------ > > Key: AS7-2322 > URL: https://issues.jboss.org/browse/AS7-2322 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Jim Tyrrell > Assignee: Brian Stansberry > Priority: Critical > Labels: eap6-ux > Fix For: 7.3.0.Alpha1 > > Attachments: log.txt > > > See the typical attached stack dump: > It would be nice if the stack dump could include all of the information above as a summary as shown below, basically just the first lines of the errors w/o the whole stack dump: > 11:51:45,391 INFO [org.jboss.as.server.controller] (HttpManagementService-threads - 5) Deployment of "SpringWAR.war" was rolled back with failure message {"Failed services" => {"jboss.web.deployment.default-host./SpringWAR" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./SpringWAR: failed to start context"}} > 11:51:45,392 INFO [org.jboss.as.controller] (HttpManagementService-threads - 5) Service status report > Services which failed to start: > service jboss.web.deployment.default-host./SpringWAR: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./SpringWAR: failed to start context > 11:51:45,417 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment SpringWAR.war in 26ms > 11:51:45,417 Error Summary of Exceptions in deployment: > - [org.springframework.web.context.ContextLoader] (MSC service thread 1-5) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B > - [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B > - [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Error listenerStart > - ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Context [/SpringWAR] startup failed due to previous errors > - [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Closing Spring root WebApplicationContext > - [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.web.deployment.default-host./SpringWAR: > ERROR Scroll up to see more info... > Or > 11:51:45,417 Error Summary of Exceptions in deployment: > [1] [org.springframework.web.context.ContextLoader] (MSC service thread 1-5) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B > [2] [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B > [3] [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Error listenerStart > [4] ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Context [/SpringWAR] startup failed due to previous errors > [5] [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Closing Spring root WebApplicationContext > [6] [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.web.deployment.default-host./SpringWAR: > ERROR Scroll up to see more info... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-4978) System properties are not expanded in jvm-options

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4978?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-4978: --------------------------------------- Work on this task should cover all aspects expression support in jvm resource elements. See spreadsheet attached to parent task. > System properties are not expanded in jvm-options > ------------------------------------------------- > > Key: AS7-4978 > URL: https://issues.jboss.org/browse/AS7-4978 > Project: Application Server 7 > Issue Type: Sub-task > Components: Domain Management > Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP), 7.2.0.Alpha1 > Reporter: Enguerrand Dibanda > Priority: Minor > Fix For: 7.2.0.Alpha1 > > > - System properties are not expanded when passed to the <jvm-options> tag of a domain mode jvm configuration. > - Problem is still present in jboss-as-7.2.0.Alpha1-SNAPSHOT -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
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 December 2012