December 2012 - 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: 7.3.0.Alpha1 (was: 7.2.0.CR1) > 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: 7.3.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, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6123) Missing artifact: Could not resolve dependencies for project org.jboss.as:jboss-as-build:pom:7.2.0.Alpha1-SNAPSHOT: Could not find artifact org.jboss.as:jboss-as-core-model-test:jar:7.2.0.Alpha1-SNAPSHOT

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-6123?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar reassigned AS7-6123: -------------------------------- Assignee: Tomaz Cerar (was: Paul Gier) > Missing artifact: Could not resolve dependencies for project org.jboss.as:jboss-as-build:pom:7.2.0.Alpha1-SNAPSHOT: Could not find artifact org.jboss.as:jboss-as-core-model-test:jar:7.2.0.Alpha1-SNAPSHOT > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-6123 > URL: https://issues.jboss.org/browse/AS7-6123 > Project: Application Server 7 > Issue Type: Bug > Components: Build System > Affects Versions: 7.2.0.Alpha1 > Reporter: Tom Jenkinson > Assignee: Tomaz Cerar > Attachments: AS7-6123, AS7-6123.patch > > > Build failure on current master when building with skipTests: > [ERROR] Failed to execute goal on project jboss-as-build: Could not resolve dependencies for project org.jboss.as:jboss-as-build:pom:7.2.0.Alpha1-SNAPSHOT: Could not find artifact org.jboss.as:jboss-as-core-model-test:jar:7.2.0.Alpha1-SNAPSHOT in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) -> [Help 1] -- 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-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: 7.3.0.Alpha1 (was: 7.2.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: 7.3.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, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-5177) Add support for expressions in security domain module-option

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5177?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5177: ---------------------------------- Parent: AS7-6120 Issue Type: Sub-task (was: Enhancement) > Add support for expressions in security domain module-option > ------------------------------------------------------------ > > Key: AS7-5177 > URL: https://issues.jboss.org/browse/AS7-5177 > Project: Application Server 7 > Issue Type: Sub-task > Components: Domain Management, Security > Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP) > Reporter: John Mazzitelli > Assignee: Tomaz Cerar > Labels: rhq > Fix For: 7.2.0.Alpha1 > > > If I use the SecureIdentity security-domain with my datasource, and I directly hardcode the password in the security-domain definition (in standalone.xml), AS7.1.1.Final starts up fine with no errors: > <security-domain name="RHQDSSecurityDomain" cache-type="default"> > <authentication> > <login-module code="SecureIdentity" flag="required"> > <module-option name="username" value="${myser:rhqadmin}"/> > <module-option name="password" value="1eeb2f255e832171df8592078de921bc"/> > </login-module> > </authentication> > </security-domain> > Notice that I use the sys prop variable in the username (${var} notation) but not for password. But now, use it for the password too: > <security-domain name="RHQDSSecurityDomain" cache-type="default"> > <authentication> > <login-module code="SecureIdentity" flag="required"> > <module-option name="username" value="${myser:rhqadmin}"/> > <module-option name="password" value="${mypass:1eeb2f255e832171df8592078de921bc}"/> > </login-module> > </authentication> > </security-domain> > Notice ${mypass:1eeb...}. I do not want to hardcode the encrypted password - I want to set that system property (preferably via the -P option) so I don't hardcode it here. > But when I start up AS7, I get an exception. Here's the exception I see at startup: > 17:44:08,636 ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-2) Exception during createSubject()PB00024: Access Denied:Unauthenticated caller:null: java.lang.SecurityException: PB00024: Access Denied:Unauthenticated caller:null > at org.jboss.security.plugins.JBossSecuritySubjectFactory.createSubject(JBossSecuritySubjectFactory.java:89) > at org.jboss.jca.deployers.common.AbstractDsDeployer$1.run(AbstractDsDeployer.java:1019) > at org.jboss.jca.deployers.common.AbstractDsDeployer$1.run(AbstractDsDeployer.java:1014) > at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.6.0_29] > at org.jboss.jca.deployers.common.AbstractDsDeployer.createSubject(AbstractDsDeployer.java:1013) > at org.jboss.jca.deployers.common.AbstractDsDeployer.deployXADataSource(AbstractDsDeployer.java:824) > at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:338) > at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:271) > at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:111) > ... -- 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-5321) support expressions for remote-destination-outbound-socket-binding host attrib

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5321?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5321: ---------------------------------- Parent: AS7-6120 Issue Type: Sub-task (was: Feature Request) > support expressions for remote-destination-outbound-socket-binding host attrib > ------------------------------------------------------------------------------ > > Key: AS7-5321 > URL: https://issues.jboss.org/browse/AS7-5321 > Project: Application Server 7 > Issue Type: Sub-task > Components: Domain Management > Affects Versions: 7.1.1.Final > Reporter: John Mazzitelli > Assignee: Tomaz Cerar > Labels: rhq > Fix For: 7.2.0.CR1 > > > I appears that remote-destination-outbound-socket-binding resources cannot have attributes that are expressions - at least the host attrtibute. In JBossAS 4.2.3, we used to have a stock email service.xml that people could customize by simply passing in new system properties (rather than editing .xml or going through a CLI to change the values). However, in AS 7.1.1.Final, we can't do this for the mail service because at least the host attribute does not appear to allow for expressions: > /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=mail-smtp > My host attribute was set to the expression ${rhq.server.email.smtp-host:localhost} and when I tried to start the server, I got: > Caused by: java.net.UnknownHostException: ${rhq.server.email.smtp-host:localhost} > at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method) [rt.jar:1.6.0_29] > at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:849) [rt.jar:1.6.0_29] > at java.net.InetAddress.getAddressFromNameService(InetAddress.java:1202) [rt.jar:1.6.0_29] > at java.net.InetAddress.getAllByName0(InetAddress.java:1153) [rt.jar:1.6.0_29] > at java.net.InetAddress.getAllByName(InetAddress.java:1083) [rt.jar:1.6.0_29] > at java.net.InetAddress.getAllByName(InetAddress.java:1019) [rt.jar:1.6.0_29] > at java.net.InetAddress.getByName(InetAddress.java:969) [rt.jar:1.6.0_29] > at org.jboss.as.network.OutboundSocketBinding.getDestinationAddress(OutboundSocketBinding.java:146) > at org.jboss.as.mail.extension.MailSessionService.getServerSocketAddress(MailSessionService.java:106) > The weird thing is, the port attribute appears to allow for expressions. When my port is set to this expression: "${rhq.server.email.smtp-port:25}", the server starts up fine (that is, after I set to the host to a legitimate hostname like "localhost") > This JIRA is to request that expressions be supported for the host attribute as it appears to be supported for the port attribute. -- 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-5418) Resource description for platform mbean properties that throw UnsupportedOperationException should say nillable="true"

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5418?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5418: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.CR1) > Resource description for platform mbean properties that throw UnsupportedOperationException should say nillable="true" > ---------------------------------------------------------------------------------------------------------------------- > > Key: AS7-5418 > URL: https://issues.jboss.org/browse/AS7-5418 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.2.Final (EAP) > Environment: FreeBSD, OpenJDK 1.6 > Reporter: Brian Stansberry > Priority: Minor > Fix For: 7.3.0.Alpha1 > > > Some platform mbean getters are documented to throw a UOE on some VMs. The read-resource handler will catch the UOE and leave the attribute undefined, but the description says it's not nillable. > Specifically, PlatformMBeanDescriptions.getThreadingResource()'s THREAD_CPU_TIME_ENABLED attribute, although there may well be others. > This leads to this unit test failure on jvms where the UOE is thrown: > failure message="thread-cpu-time-enabled is undefined" > type="junit.framework.AssertionFailedError">junit.fra mework.AssertionFailedError: thread-cpu-time-enabled is undefined > at junit.framework.Assert.fail(Assert.java:50) > at junit.framework.Assert.assertTrue(Assert.java:20) > at > org.jboss.as.platform.mbean.PlatformMBeanResourceUnitTestCase.validateResource(PlatformMBeanResourceUn > itTestCase.java:595) > at org.jboss.as.platform.mbean.PlatformMBeanResourceUnitTestCase.basicResourceTest(PlatformMBeanResourceUnitTestCase.java:563) > at > org.jboss.as.platform.mbean.PlatformMBeanResourceUnitTestCase.testThreadingMXBean(PlatformMBeanResourceUnitTestCase.java:340) -- 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-5338) Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops should be visible to users

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5338?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5338: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.CR1) > Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops should be visible to users > --------------------------------------------------------------------------------------------- > > Key: AS7-5338 > URL: https://issues.jboss.org/browse/AS7-5338 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 7.3.0.Alpha1 > > > Ops registered on a domain server without the RUNTIME_ONLY flag are hidden from users (e.g. in read-operation-names results etc) in order to not delude users into thinking they can do something like :write-attribute directly on a server (instead of modifying host or domain config elements.) > But shouldn't a READ_ONLY flag be sufficient as well? An op that only reads config should be valid. -- 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-5522) Convert deployment's content to a child resource

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5522?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5522: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.CR1) > Convert deployment's content to a child resource > ------------------------------------------------ > > Key: AS7-5522 > URL: https://issues.jboss.org/browse/AS7-5522 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Brian Stansberry > Fix For: 7.3.0.Alpha1 > > > At the moment this is a complex attribute. > Not saying this MUST happen, just opening this to see what Brian & co think. I never really understood why it is a list either. -- 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-5503) Move DC operation stream cleaning from OperationCoordinatorStepHandler and into the OSHs that actual process the input streams

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5503?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5503: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.CR1) > Move DC operation stream cleaning from OperationCoordinatorStepHandler and into the OSHs that actual process the input streams > ------------------------------------------------------------------------------------------------------------------------------ > > Key: AS7-5503 > URL: https://issues.jboss.org/browse/AS7-5503 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 7.3.0.Alpha1 > > > Get rid of hackaliciousness at [1] and replace using OperationAttachments the way Stuart did for deployment overlays. > [1] https://github.com/jbossas/jboss-as/blob/master/host-controller/src/main/... -- 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-5573) Track "uncleanly unregistered" hosts on the master HC; expose via management API

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5573?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5573: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.CR1) > Track "uncleanly unregistered" hosts on the master HC; expose via management API > -------------------------------------------------------------------------------- > > Key: AS7-5573 > URL: https://issues.jboss.org/browse/AS7-5573 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 7.3.0.Alpha1 > > > When the master HC detects that a slave HC is no longer available but hasn't properly unregistered, the slave should still be visible in the management API but with some sort of status indicator. > The slave should probably not remaining in the regular management tree, since that will encourage clients to invoke operations that will just fail, but it's existence and "unknown" status should be reflected in some manner accessible to management clients who wish to obtain a more complete view of the domain topology. -- 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