October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-622) DRLDumper does not output enum type declarations

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-622: ------------------------------------- Summary: DRLDumper does not output enum type declarations Key: DROOLS-622 URL: https://issues.jboss.org/browse/DROOLS-622 Project: Drools Issue Type: Bug Affects Versions: 6.1.0.Final, 6.0.1.Final, 6.0.0.Final Reporter: Davide Sottara Assignee: Mark Proctor -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-621) DRLDumper does not output trait type declarations correctly

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-621: ------------------------------------- Summary: DRLDumper does not output trait type declarations correctly Key: DROOLS-621 URL: https://issues.jboss.org/browse/DROOLS-621 Project: Drools Issue Type: Bug Affects Versions: 6.1.0.Final, 6.0.1.Final, 6.0.0.Final Reporter: Davide Sottara Assignee: Davide Sottara -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-136) Create a new error message for suffix attribute on size-rotating-file-handler

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-136?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-136: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1147806|https://bugzilla.redhat.com/show_bug.cgi?id=1147806] from POST to MODIFIED > Create a new error message for suffix attribute on size-rotating-file-handler > ------------------------------------------------------------------------------ > > Key: WFCORE-136 > URL: https://issues.jboss.org/browse/WFCORE-136 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 1.0.0.Alpha9 > > > As part of WFCORE-113, the suffix attribute on size-rotating-file-handler has a little bit different functionality than on other handlers (seconds or milliseconds are allowed). However the validation error message is the same as on other handlers ("seconds or milliseconds are not allowed"). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-132) BoundedQueueThreadPoolWriteAttributeHandler does not deal with undefined core-threads correctly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-132?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-132: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1147067|https://bugzilla.redhat.com/show_bug.cgi?id=1147067] from POST to MODIFIED > BoundedQueueThreadPoolWriteAttributeHandler does not deal with undefined core-threads correctly > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-132 > URL: https://issues.jboss.org/browse/WFCORE-132 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha8 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.Alpha9 > > > BoundedQueueThreadPoolWriteAttributeHandler doesn't deal with undefined values for core-threads correctly. It assumes the attribute will be defined, and that's not required. > The attribute doesn't have a fixed default value. Instead, the behavior in add is to set the runtime value to match max-threads of core-threads is undefined. BoundedQueueThreadPoolWriteAttributeHandler should do the same. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-620) Interval rule consequence actions not processed

by Roger Lefebvre (JIRA)

[ https://issues.jboss.org/browse/DROOLS-620?page=com.atlassian.jira.plugin... ] Roger Lefebvre updated DROOLS-620: ---------------------------------- Steps to Reproduce: Execute the added test cases defined in the commit description. (was: GIT Pull request to come) > Interval rule consequence actions not processed > ----------------------------------------------- > > Key: DROOLS-620 > URL: https://issues.jboss.org/browse/DROOLS-620 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.Beta1 > Environment: MacBook Pro, OS X 10.9.5 > Reporter: Roger Lefebvre > Assignee: Mark Proctor > > Actions defined in the consequence of a rule with an defined interval (e.g. cron) are not processed by the system. Inserted facts, modified fields and pushed agenda groups are not consumed resulting in other rules not being fired. If you execute fireAllRules from code, it will then process the consequence actions. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-620) Interval rule consequence actions not processed

by Roger Lefebvre (JIRA)

[ https://issues.jboss.org/browse/DROOLS-620?page=com.atlassian.jira.plugin... ] Roger Lefebvre updated DROOLS-620: ---------------------------------- Git Pull Request: https://github.com/droolsjbpm/drools/pull/387 > Interval rule consequence actions not processed > ----------------------------------------------- > > Key: DROOLS-620 > URL: https://issues.jboss.org/browse/DROOLS-620 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.Beta1 > Environment: MacBook Pro, OS X 10.9.5 > Reporter: Roger Lefebvre > Assignee: Mark Proctor > > Actions defined in the consequence of a rule with an defined interval (e.g. cron) are not processed by the system. Inserted facts, modified fields and pushed agenda groups are not consumed resulting in other rules not being fired. If you execute fireAllRules from code, it will then process the consequence actions. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-58) Setting some locales causes missing buttons on console and throws errors.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-58?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFCORE-58: ----------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1141668|https://bugzilla.redhat.com/show_bug.cgi?id=1141668] from POST to MODIFIED > Setting some locales causes missing buttons on console and throws errors. > ------------------------------------------------------------------------- > > Key: WFCORE-58 > URL: https://issues.jboss.org/browse/WFCORE-58 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha4 > Reporter: Jay Kumar SenSharma > Assignee: Tomaz Cerar > Fix For: 1.0.0.Alpha5 > > Attachments: mssing_add_remove_disable_Buttons.png > > > - When WildFly 9 Alpha1 is started with the following system properties in the "standalone.conf" then the admin console behaves abnormally and shows some missing buttons in the console. See attached screenshot "mssing_add_remove_disable_Buttons.png". > {code} > JAVA_OPTS="$JAVA_OPTS -Duser.country=TR -Duser.language=tr" > {code} > - Also it throws following Error while accessing the console URL like [1] > [1] http://localhost:9990/console/App.html#datasources > {code} > 10:39:39,223 ERROR [org.jboss.as.controller.management-operation] (XNIO-1 task-8) WFLYCTL0013: Operation ("check-resource-access") failed - address: ([ > ("subsystem" => "datasources"), > ("data-source" => "*"), > ("connection-properties" => "*") > ]): java.lang.IllegalArgumentException: No enum constant org.jboss.as.controller.registry.AttributeAccess.Storage.CONFİGURATİON > at java.lang.Enum.valueOf(Enum.java:236) [rt.jar:1.7.0_51] > at org.jboss.as.controller.registry.AttributeAccess$Storage.valueOf(AttributeAccess.java:91) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3] > at org.jboss.as.controller.operations.global.ReadResourceDescriptionHandler$CheckResourceAccessHandler.execute(ReadResourceDescriptionHandler.java:431) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3] > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:603) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:481) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3] > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:282) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3] > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:277) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3] > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1060) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3] > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:296) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3] > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:165) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3] > at org.jboss.as.domain.http.server.DomainApiHandler.handleRequest(DomainApiHandler.java:179) [wildfly-domain-http-interface-1.0.0.Alpha3.jar:1.0.0.Alpha3] > at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$1.run(SubjectDoAsHandler.java:72) [wildfly-domain-http-interface-1.0.0.Alpha3.jar:1.0.0.Alpha3] > at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$1.run(SubjectDoAsHandler.java:68) [wildfly-domain-http-interface-1.0.0.Alpha3.jar:1.0.0.Alpha3] > at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_51] > at javax.security.auth.Subject.doAs(Subject.java:415) [rt.jar:1.7.0_51] > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3] > at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:68) [wildfly-domain-http-interface-1.0.0.Alpha3.jar:1.0.0.Alpha3] > at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:63) [wildfly-domain-http-interface-1.0.0.Alpha3.jar:1.0.0.Alpha3] > at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:50) [undertow-core-1.1.0.Beta5.jar:1.1.0.Beta5] > at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:83) [wildfly-domain-http-interface-1.0.0.Alpha3.jar:1.0.0.Alpha3] > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.1.0.Beta5.jar:1.1.0.Beta5] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:197) [undertow-core-1.1.0.Beta5.jar:1.1.0.Beta5] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:737) [undertow-core-1.1.0.Beta5.jar:1.1.0.Beta5] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-140) The Resource for a deployment whose 'persistent' attribute is 'false' does not return 'true' from isRuntime()

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-140?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-140: ------------------------------------ Description: Scanner managed deployments have the deployment resource's 'persistent' attribute set to 'false'. This results in the StandaloneXml not persisting the resource to XML, but that depends on custom logic in StandaloneXml that reads the attribute. The Resource for these deployments should return 'true' from isRuntime() so callers can decided about this without needing internal knowledge of the resource attributes. was: Scanner managed deployments have the deployment resource's 'persistent' attribute set to 'false'. This results in the StandardXml not persisting the resource to XML, but that depends on custom logic in StandardXml that reads the attribute. The Resource for these deployments should return 'true' from isRuntime() so callers can decided about this without needing internal knowledge of the resource attributes. > The Resource for a deployment whose 'persistent' attribute is 'false' does not return 'true' from isRuntime() > ------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-140 > URL: https://issues.jboss.org/browse/WFCORE-140 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha8 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.Alpha9 > > > Scanner managed deployments have the deployment resource's 'persistent' attribute set to 'false'. This results in the StandaloneXml not persisting the resource to XML, but that depends on custom logic in StandaloneXml that reads the attribute. > The Resource for these deployments should return 'true' from isRuntime() so callers can decided about this without needing internal knowledge of the resource attributes. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-140) The Resource for a deployment whose 'persistent' attribute is 'false' does not return 'true' from isRuntime()

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-140: --------------------------------------- Summary: The Resource for a deployment whose 'persistent' attribute is 'false' does not return 'true' from isRuntime() Key: WFCORE-140 URL: https://issues.jboss.org/browse/WFCORE-140 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 1.0.0.Alpha8 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 1.0.0.Alpha9 Scanner managed deployments have the deployment resource's 'persistent' attribute set to 'false'. This results in the StandardXml not persisting the resource to XML, but that depends on custom logic in StandardXml that reads the attribute. The Resource for these deployments should return 'true' from isRuntime() so callers can decided about this without needing internal knowledge of the resource attributes. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-139) OperationContext should create runtime-only resources for addresses whose registration is runtime only

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-139: --------------------------------------- Summary: OperationContext should create runtime-only resources for addresses whose registration is runtime only Key: WFCORE-139 URL: https://issues.jboss.org/browse/WFCORE-139 Project: WildFly Core Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 1.0.0.Alpha9 The OperationContext.createResource method creates and adds a default Resource. The created Resource should return the same value from isRuntime() that the ManagementResourceRegistration associated with the target address returns from MRR.isRuntimeOnly() -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

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 October 2014