March 2013 - jboss-jira - Jboss List Archives

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-462?page=com.atlassian.jira.plugin.sy... ] Brian Stansberry updated AS7-462: --------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Patching system > --------------- > > Key: AS7-462 > URL: https://issues.jboss.org/browse/AS7-462 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > Labels: rhq > Fix For: 8.0.0.Alpha1 > > > "Server" side of the patching system. Server not in the sense of the domain model Server, but rather client-server where the client is whatever tool (JON) determines there are patches available and asks the server to apply them. > This does not need to implemented until M2 but thinking about it during the design of the InstalledImage is good. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-5659) pre/post cli-scripts for AS patching feature

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5659?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5659: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > pre/post cli-scripts for AS patching feature > -------------------------------------------- > > Key: AS7-5659 > URL: https://issues.jboss.org/browse/AS7-5659 > Project: Application Server 7 > Issue Type: Feature Request > Components: Scripts > Reporter: Nicklas Karlsson > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.Alpha1 > > > It would be handy to be able to attach pre/post CLI scripts to be applied for an AS patch. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-5181) inconsistent usage of min/max-occurs in model description

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5181?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5181: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > inconsistent usage of min/max-occurs in model description > --------------------------------------------------------- > > Key: AS7-5181 > URL: https://issues.jboss.org/browse/AS7-5181 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.0.Final > Reporter: Emanuel Muckenhuber > Fix For: 8.0.0.Alpha1 > > Attachments: patch.txt > > > The usages of min/max-occurs in the model description are not consistent - e.g. missing in ResourceDescription, mostly wrong when used in the descriptionProvider or outdated examples in the documentation. > I'll attach a simple patch which should actually fix that issue in line with the documentation [1] (incl. recursive usage) and the usage of the CLI (ls -l). However there might be more to it. > [1] https://docs.jboss.org/author/display/AS71/Description+of+the+Management+... -- 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, 4 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: (was: 7.3.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 > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-1370) Domain Management - Add support for database authentication.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-1370?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-1370: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Domain Management - Add support for database authentication. > ------------------------------------------------------------ > > Key: AS7-1370 > URL: https://issues.jboss.org/browse/AS7-1370 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Flemming Harms > Fix For: 8.0.0.Alpha1 > > > It should be possible to define a database authentication element for authentication of incoming connections against a database. > Ideally the password should be obtainable from the database to allow us to use DIGEST authentication but if not a fallback to verify the password should be supported. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-637) Ability to rollback AS version updates

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-637?page=com.atlassian.jira.plugin.sy... ] Brian Stansberry updated AS7-637: --------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Ability to rollback AS version updates > -------------------------------------- > > Key: AS7-637 > URL: https://issues.jboss.org/browse/AS7-637 > Project: Application Server 7 > Issue Type: Sub-task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: > >> A fixpack installer that handles version rollbacks would be fantastic. > >> Of course it needs to remain flexible to work with JBoss installs that > >> have been manually modified. > Note that this may be out of scope for community AS 7; e.g. it may be a JON function. However, the AS 7 design of things like how we lay down content on the filesystem should take this use case into account. -- 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, 4 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: No Release (was: 7.3.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: No Release > > > 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, 4 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: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > 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: 8.0.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, 4 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: Open To Community (was: 7.3.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: Open To Community > > > 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, 4 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: No Release (was: 7.3.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: No Release > > > 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, 4 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 March 2013