August 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1611) Update logging to follow TAG-2 message format

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1611?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1611: --------------------------- Fix Version/s: 3.2.11 > Update logging to follow TAG-2 message format > --------------------------------------------- > > Key: JGRP-1611 > URL: https://issues.jboss.org/browse/JGRP-1611 > Project: JGroups > Issue Type: Task > Reporter: James Perkins > Assignee: Paul Ferraro > Priority: Minor > Fix For: 3.2.11, 3.4 > > > As per [ANDIAMO-7|https://issues.jboss.org/browse/ANDIAMO-7] all messages (logged and exceptions) need a unique id. This need to be done using JBoss Logging, [ANDIAMO-2|https://issues.jboss.org/browse/ANDIAMO-2]. See [https://community.jboss.org/docs/DOC-18453] for information on configuring the loggers and message bundles. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1177) Recursive expression resolution

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1177?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1177: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 960820|https://bugzilla.redhat.com/show_bug.cgi?id=960820] from POST to MODIFIED > Recursive expression resolution > ------------------------------- > > Key: WFLY-1177 > URL: https://issues.jboss.org/browse/WFLY-1177 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Jess Sightler > Labels: rhq > Fix For: 8.0.0.Alpha1 > > > When resolving an expression, keep resolving until the output of the resolution matches the input. > Use case: > ${sys.prop.with.host.specific.value} > resolves to > ${VAULT::xxxxx} > which resolves to > thesecret > Basically, the main mechanism for customizing domain-level configs on a per-host basis is to use expressions and use different values on each host. But this breaks down when a vault expression is added to the mix. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-247) Property reactivity does not work with positional/unification constraints

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-247: ------------------------------------- Summary: Property reactivity does not work with positional/unification constraints Key: DROOLS-247 URL: https://issues.jboss.org/browse/DROOLS-247 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 6.0.0.CR2, 5.5.0.Final Reporter: Davide Sottara Assignee: Mark Proctor Priority: Minor Fix For: 5.5.1.Final, 6.0.0.Final Positional and/or unification constraints are interpreted as either bindings or constraints, depending on the whether the variable is already bound or not. The user is expected not to have to care about the difference. ... Person( $name; $age := age ) ... If the pattern type is @propertyReactive, however, the actual decision between binding and constraint WILL make a difference, possibly forcing the user to use @watch() -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-245) Drools sees a type as a package

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-245?page=com.atlassian.jira.plugin... ] Davide Sottara commented on DROOLS-245: --------------------------------------- Could you post your DRL code - or at least the "Your First Rule" rule and the header (package, imports, declares and functions) ? Thanks! Davide > Drools sees a type as a package > -------------------------------- > > Key: DROOLS-245 > URL: https://issues.jboss.org/browse/DROOLS-245 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Reporter: georg tornqvist > Assignee: Mark Proctor > > Hi, > I want Drools to reason over an axis2 type, but the Drools compiler sees the type as a package, see error message below. > Strictly speaking, the Drools compiler may be right. The type "Client" encapsulates a "Factory" class, making hierarchically speaking the class "Client" a package. > Although I'm fairly new to Drools, I'm pretty sure that the behavior I'm experiencing is not right. The Drools version used in the WSO2BRS-2.0.0 is able to reason over the very same axis2 types. > Error importing : 'nl.domain.www.schema.Client' > Rule Compilation error : [Rule name='Your First Rule'] > io31/Rule_Your_First_Rule_16db2a632a4b4efd96dde4c6d6a55cdf.java (2:57) : Only a type can be imported. > nl.domain.www.schema.Client resolves to a package -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-246) Ensure traitable classes are declared as @Traitable

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-246: ------------------------------------- Summary: Ensure traitable classes are declared as @Traitable Key: DROOLS-246 URL: https://issues.jboss.org/browse/DROOLS-246 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.CR2, 5.5.0.Final Reporter: Davide Sottara Assignee: Mark Proctor Priority: Minor Fix For: 5.5.1.Final, 6.0.0.Final @Traitable classes - classes whose instances will don trait types - must be declared as such, otherwise the engine won't be able to allocate the appropriate data structures (namely the FactHandle) -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1385) Override default page-size-bytes in messaging subsystem configuration

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1385?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1385: ----------------------------------------------- Clebert Suconic <csuconic(a)redhat.com> made a comment on [bug 920980|https://bugzilla.redhat.com/show_bug.cgi?id=920980] This was rejected on 6.1.x (6.1.2 eventually)... I just submitted a new PR on 6.x: https://github.com/jbossas/jboss-eap/pull/333 @MIro: what version, what target and what status should this set to now? > Override default page-size-bytes in messaging subsystem configuration > --------------------------------------------------------------------- > > Key: WFLY-1385 > URL: https://issues.jboss.org/browse/WFLY-1385 > Project: WildFly > Issue Type: Enhancement > Components: JMS > Affects Versions: 8.0.0.Alpha1 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Minor > Fix For: 8.0.0.Alpha2 > > > When HornetQ address-full-policy is switched from BLOCK to PAGE, the following exception is thrown during shutdown. > {noformat} > Exception: > 09:48:05,247 WARN [org.hornetq.core.server] (MSC service thread 1-3) HQ222160: unable to send notification when broadcast group is stopped: java.lang.IllegalStateException: pageSize for address hornetq.notifications >= maxSize. Normally pageSize should be significantly smaller than maxSize, ms: 10485760 ps 10485760 > at org.hornetq.core.paging.impl.PagingStoreImpl.<init>(PagingStoreImpl.java:147) [hornetq-server-2.3.0.CR1-redhat-1.jar:2.3.0.CR1-redhat-1] > at org.hornetq.core.paging.impl.PagingStoreFactoryNIO.newStore(PagingStoreFactoryNIO.java:98) [hornetq-server-2.3.0.CR1-redhat-1.jar:2.3.0.CR1-redhat-1] > at org.hornetq.core.paging.impl.PagingManagerImpl.newStore(PagingManagerImpl.java:250) [hornetq-server-2.3.0.CR1-redhat-1.jar:2.3.0.CR1-redhat-1] > {noformat} > The standalone-full.xml configuration overrides the default address-setting's max-size-bytes (defaults to -1) to set it at 10 MiB. > However, if the admin changes the address-full-policy from BLOCK to PAGE, it will conflict with the default value for page-size-bytes which is also 10MiB. > To make the overridden standalone-full.xml more consistent, we can override page-size-bytes and set it to 2MiB (2097152 bytes). This change has no effect when the address-full-policy remains at BLOCK. When it is changed to PAGE, the resulting configuration will be coherent and there will be no exception thrown -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1977) Add configuration attribute for PERMISSIVE vs REJECTING role combinations

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-1977: -------------------------------------- Summary: Add configuration attribute for PERMISSIVE vs REJECTING role combinations Key: WFLY-1977 URL: https://issues.jboss.org/browse/WFLY-1977 Project: WildFly Issue Type: Sub-task Components: Domain Management Reporter: Brian Stansberry Fix For: 8.0.0.Beta1 The code implements PERMISSIVE, which is the default. Need a hook to turn on REJECTING, which should generate a role mapping exception if > 1 role is mapped. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1943) Add Run-As Capability to ConfigurableRoleMapper

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1943?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-1943: ----------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/4982 (was: https://github.com/bstansberry/wildfly/pull/26) > Add Run-As Capability to ConfigurableRoleMapper > ----------------------------------------------- > > Key: WFLY-1943 > URL: https://issues.jboss.org/browse/WFLY-1943 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Beta1 > > > For any user currently granted the 'SuperUser' role the existing header to request a lesser role should be honoured. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1866) More useful access control failure messages

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1866?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-1866: -------------------------------------- Assignee: Brian Stansberry > More useful access control failure messages > ------------------------------------------- > > Key: WFLY-1866 > URL: https://issues.jboss.org/browse/WFLY-1866 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.0.CR1 > > > The current RBAC implementation does not provide any information about the reason for an unauthorized decision, simply a "Permission denied" message. > This should be reworked such that constraints can provide more information thus helping the user to understand the reason an action is not authorized. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1920) Access control constraints for the audit logging resources

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1920?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-1920: ---------------------------------------- Can this be resolved? > Access control constraints for the audit logging resources > ---------------------------------------------------------- > > Key: WFLY-1920 > URL: https://issues.jboss.org/browse/WFLY-1920 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Kabir Khan > Fix For: 8.0.0.Beta1 > > > Currently the constraints related to audit logging don't do anything -- they are just stubs written pending the audit logging patch. So these need completion. > I believe this is just implementing the TODOs in AuditConstraint and NonAuditConstraint and then updating the tests to check the roles work properly. I envisioned the TODO as being a simple test of the target resource address, i.e. does it start with /host=*/core-service=management/access=audit. -- 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

10 years, 8 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 August 2013