March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2908) The formatter attribute is changed every time it's processed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2908?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2908: ----------------------------------------------- James Perkins <jperkins(a)redhat.com> changed the Status of [bug 1066597|https://bugzilla.redhat.com/show_bug.cgi?id=1066597] from NEW to CLOSED > The formatter attribute is changed every time it's processed > ------------------------------------------------------------ > > Key: WFLY-2908 > URL: https://issues.jboss.org/browse/WFLY-2908 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 8.0.1.Final > > > The {{HandlerOperations.equalValue()}} method uses the incorrect property name when comparing values resulting in the method always returning {{false}}. > This does not harm anything, but just changes the format pattern each time a resource is processed. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-195) Rule Engine Crashes when used Slide Window constraints and kAgent is configured as incremental processing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-195?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-195: ------------------------------------------------ Rick Wagner <rwagner(a)redhat.com> changed the Status of [bug 1031099|https://bugzilla.redhat.com/show_bug.cgi?id=1031099] from NEW to ASSIGNED > Rule Engine Crashes when used Slide Window constraints and kAgent is configured as incremental processing > --------------------------------------------------------------------------------------------------------- > > Key: DROOLS-195 > URL: https://issues.jboss.org/browse/DROOLS-195 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Alessandro Lazarotti > Assignee: Mario Fusco > Attachments: LoopTest.java > > > When there is a Slide Window constraint and the kbase is configured to receive incremental changes from the kagent (drools.agent.newInstance as false) - the engine crashes > Attached unit test > Version: 5.3.0 -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-72) Potential memory leak in StatelessKnowledgeSessionImpl#execute when fireAllRules throwing RuntimeException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-72?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on DROOLS-72: ----------------------------------------------- Rick Wagner <rwagner(a)redhat.com> changed the Status of [bug 1036126|https://bugzilla.redhat.com/show_bug.cgi?id=1036126] from NEW to ASSIGNED > Potential memory leak in StatelessKnowledgeSessionImpl#execute when fireAllRules throwing RuntimeException > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-72 > URL: https://issues.jboss.org/browse/DROOLS-72 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Reporter: Trung Nguyen > Assignee: Mario Fusco > Fix For: 5.5.1.Final, 6.0.0.Alpha9 > > > when {{ksession.fireAllRules()}} throws RuntimeException, it cause {{ksession}} never gets released. > {code:lang=java} > public void execute(Object object) { > StatefulKnowledgeSession ksession = newWorkingMemory(); > ksession.insert( object ); > ksession.fireAllRules( ); > ksession.dispose(); > } > public void execute(Iterable objects) { > StatefulKnowledgeSession ksession = newWorkingMemory(); > for ( Object object : objects ) { > ksession.insert( object ); > } > ksession.fireAllRules( ); > ksession.dispose(); > } > {code} -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2959) Downgrade Jackson dependency

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2959?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-2959: ------------------------------------- The main issue was if you wanted to use Jackson 2 with RESTEasy, the application would fail to deploy. Is that the same issue with jackson-datatype-hibernate too? I know it's a lot to ask, but if anyone could attach simple example apps that show the behavior of 1 where it fails on RESTEasy with 2.3.x and 2 where it fails on 2.2.x with Hibernate. I will check to see if 2.3.2 fixes both issues. It wasn't released when I did the downgrade. > Downgrade Jackson dependency > ---------------------------- > > Key: WFLY-2959 > URL: https://issues.jboss.org/browse/WFLY-2959 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST > Affects Versions: 8.0.0.Final > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.0.1.Final > > > Jackson was upgraded to 2.3.0 which contains a [bug|https://github.com/FasterXML/jackson-jaxrs-providers/commit/bafb6fb64...] that breaks RESTEasy. RESTEasy currently uses 2.2.1. Downgrading to at least 2.2.3, which is what CR1 is at, seems to resolve this issue. > We should likely keep the version aligned with RESTEasy, but since CR1 was using 2.2.3 with no issues, I think reverting back to that should be fine. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1895) Provide a "default" role for management users with no other role specified

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1895?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-1895: ----------------------------------- Assignee: Emanuel Muckenhuber (was: Brian Stansberry) > Provide a "default" role for management users with no other role specified > -------------------------------------------------------------------------- > > Key: WFLY-1895 > URL: https://issues.jboss.org/browse/WFLY-1895 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Jakub Cechacek > Assignee: Emanuel Muckenhuber > Labels: rbac-filed-by-qa > Fix For: 8.0.1.Final > > > Currently it seems that when using RBAC provider users with no defined role are unable to read domain model at all. Consequently logging into Admin Console leads to 500 error page. Similar errors in CLI. > In relation to this, it should be considered what is the expected behavior of unsecured management interface. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2479) Security subsystem transformers for 1.1.0 do not reject expressions, or test for it

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-2479?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-2479: ----------------------------------- Assignee: Emanuel Muckenhuber (was: Brian Stansberry) > Security subsystem transformers for 1.1.0 do not reject expressions, or test for it > ----------------------------------------------------------------------------------- > > Key: WFLY-2479 > URL: https://issues.jboss.org/browse/WFLY-2479 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Kabir Khan > Assignee: Emanuel Muckenhuber > Fix For: 8.0.1.Final > > > Getting it to test for it is going to be a bit different than the usual RejectExpressionsConfig. The add handler transformers (correctly from what I can tell) use the existing child xxx-module resource to create the transformed add operation. > However, I think with the ModelTestUtils.checkFailedTransformedBootOperations() stuff set up the way it is the child resource/model used to populate the ops. A possible solution is to override the RejectExpressionsConfig to correct the main model as part of correcting the ops. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3000) Incorrect 'Content-Type' response set after executing an erroneous command

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3000?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-3000: ----------------------------------- Assignee: Emanuel Muckenhuber (was: Brian Stansberry) > Incorrect 'Content-Type' response set after executing an erroneous command > -------------------------------------------------------------------------- > > Key: WFLY-3000 > URL: https://issues.jboss.org/browse/WFLY-3000 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Christos Vasilakis > Assignee: Emanuel Muckenhuber > Fix For: 8.0.1.Final > > > The http management interface, upon error, returns an incorrect 'Content-Type' of > {noformat} > 'Content-Type: text/plain; charset=utf-8' > {noformat} > although JSON response is returned. > To reproduce, issue from the command line a simple 'read' operation > {noformat} > curl --digest -D - http://localhost:9990/management --header "Content-Type: application/json" -d '{"operation":"read-attribute", "name":"foo"}' -u <username>:<password> > .. > Content-Type: text/plain; charset=utf-8 > Content-Length: 119 > Date: Sun, 23 Feb 2014 17:27:10 GMT > { > "outcome" : "failed", > "failure-description" : "JBAS014792: Unknown attribute foo", > "rolled-back" : true > } > {noformat} > The 'Content-Type' should have been set to *'application/json'* instead of *'text/plain'* > Note: On JBoss AS 7.1.1.Final, the correct type of *'application/json'* is returned for the same operation. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3008) System property substitution does not work in subnet-match

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3008?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-3008: ----------------------------------- Assignee: Emanuel Muckenhuber (was: Brian Stansberry) > System property substitution does not work in subnet-match > ---------------------------------------------------------- > > Key: WFLY-3008 > URL: https://issues.jboss.org/browse/WFLY-3008 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Rich DiCroce > Assignee: Emanuel Muckenhuber > Priority: Minor > Fix For: 8.0.1.Final > > > Specifying a system property in subnet-match when defining an interface causes an exception on startup. Example: > {code:xml} > <property name="subnet" value="192.168.0.0/16"/> > ... > <interface name="public"> > <subnet-match value="${subnet}"/> > </interface> > {code} > Causes: > {code} > 12:36:13,457 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[311,46] > Message: JBAS014693: Invalid 'value' ${subnet} -- must be of the form address/mask > at org.jboss.as.server.parsing.CommonXml.validateAddressMask(CommonXml.java:605) [wildfly-server-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.server.parsing.CommonXml.parseSimpleInterfaceCriterion(CommonXml.java:587) [wildfly-server-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.server.parsing.CommonXml.parseInterfaceCriteria(CommonXml.java:467) [wildfly-server-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.server.parsing.CommonXml.parseInterfaces(CommonXml.java:644) [wildfly-server-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:465) [wildfly-server-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:145) [wildfly-server-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107) [wildfly-server-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:104) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final] > ... 3 more > {code} -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3069) slaves cannot reconnect to a restarted master if RBAC is enabled

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3069?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3069: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1072915|https://bugzilla.redhat.com/show_bug.cgi?id=1072915] from NEW to ASSIGNED > slaves cannot reconnect to a restarted master if RBAC is enabled > ---------------------------------------------------------------- > > Key: WFLY-3069 > URL: https://issues.jboss.org/browse/WFLY-3069 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Tom Fonteyne > Assignee: Emanuel Muckenhuber > Priority: Critical > > Enable RBAC in an Wilfly domain setup. "reload --host=master" and the slaves will no longer be connected to the master -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3069) slaves cannot reconnect to a restarted master if RBAC is enabled

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3069?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-3069: ----------------------------------- Assignee: Emanuel Muckenhuber (was: Brian Stansberry) > slaves cannot reconnect to a restarted master if RBAC is enabled > ---------------------------------------------------------------- > > Key: WFLY-3069 > URL: https://issues.jboss.org/browse/WFLY-3069 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Tom Fonteyne > Assignee: Emanuel Muckenhuber > Priority: Critical > > Enable RBAC in an Wilfly domain setup. "reload --host=master" and the slaves will no longer be connected to the master -- 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

12 years, 2 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 2014