December 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2695) Creating named formater patterns for offline servers fail

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2695?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-2695: -------------------------------- Steps to Reproduce: * extract wildfly-8.0.0.CR1 * run bin/domain * execute commands via CLI ** :stop-servers ** -/profile=full/subsystem=logging/console-handler=CONSOLE:remove- ** /profile=full/subsystem=logging/pattern-formatter=TESTPATTERN:add(pattern="%d%n") ** /profile=full/subsystem=logging/console-handler=CONSOLE:write-attribute(name=named-formatter, value=TESTPATTERN) ** /host=master/server-config=server-one:start was: * extract wildfly-8.0.0.CR1 * run bin/domain * execute commands via CLI ** :stop-servers ** /profile=full/subsystem=logging/console-handler=CONSOLE:remove ** /profile=full/subsystem=logging/pattern-formatter=TESTPATTERN:add(pattern="%d%n") ** /profile=full/subsystem=logging/console-handler=CONSOLE:write-attribute(name=named-formatter, value=TESTPATTERN) ** /host=master/server-config=server-one:start > Creating named formater patterns for offline servers fail > --------------------------------------------------------- > > Key: WFLY-2695 > URL: https://issues.jboss.org/browse/WFLY-2695 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Logging > Affects Versions: 8.0.0.CR1 > Environment: any domain configuration > Reporter: Matthias Berndt > Assignee: James Perkins > > After adding and attaching a named formatter to an offline server starting the server fails due to an invalid logging configuration. > server-one fails with: > {{ > [Server:server-one] 00:08:00,214 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("add") failed - address: ([ > [Server:server-one] ("subsystem" => "logging"), > [Server:server-one] ("console-handler" => "CONSOLE") > [Server:server-one] ]): java.lang.IllegalArgumentException: Formatter "TESTPATTERN" is not found > }} > I assume logging.properties is written too late in LoggingOperations.java -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-2695) Creating named formater patterns for offline servers fail

by Matthias Berndt (JIRA)

Matthias Berndt created WFLY-2695: ------------------------------------- Summary: Creating named formater patterns for offline servers fail Key: WFLY-2695 URL: https://issues.jboss.org/browse/WFLY-2695 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Logging Affects Versions: 8.0.0.CR1 Environment: any domain configuration Reporter: Matthias Berndt Assignee: James Perkins After adding and attaching a named formatter to an offline server starting the server fails due to an invalid logging configuration. server-one fails with: {{ [Server:server-one] 00:08:00,214 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("add") failed - address: ([ [Server:server-one] ("subsystem" => "logging"), [Server:server-one] ("console-handler" => "CONSOLE") [Server:server-one] ]): java.lang.IllegalArgumentException: Formatter "TESTPATTERN" is not found }} I assume logging.properties is written too late in LoggingOperations.java -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-2694) CLI example output for connecting to domain controller inaccurate

by Mark Little (JIRA)

Mark Little created WFLY-2694: --------------------------------- Summary: CLI example output for connecting to domain controller inaccurate Key: WFLY-2694 URL: https://issues.jboss.org/browse/WFLY-2694 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 8.0.0.CR1 Environment: Raspberry Pi Linux raspberrypi 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 armv6l GNU/Linux Reporter: Mark Little Assignee: Tom Wells Priority: Minor According to https://docs.jboss.org/author/display/WFLY8/Management+Clients --- ./bin/jboss-cli.sh You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. [disconnected /] [disconnected /] connect Connected to domain controller at localhost:9999 ---- But no "Connected to domain controller" is output. No indication of success is given other than the next line of the CLI has the hostname (localhost) referenced. -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-2693) list-active-jsf-impls is missing reply type

by Philippe Marschall (JIRA)

Philippe Marschall created WFLY-2693: ---------------------------------------- Summary: list-active-jsf-impls is missing reply type Key: WFLY-2693 URL: https://issues.jboss.org/browse/WFLY-2693 Project: WildFly Issue Type: Enhancement Security Level: Public (Everyone can see) Components: JSF Reporter: Philippe Marschall Assignee: Stan Silvert The DMR operation "list-active-jsf-impls" of the JSF subsystem is missing a reply type. Therefore the operation will show up as "Void" in VisualVM and no result will be displayed. -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-279) Add deployment-scanner for singleton deployments

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-279?page=com.atlassian.jira.plugin.s... ] Paul Ferraro updated WFLY-279: ------------------------------ Fix Version/s: 9.0.0.CR1 (was: 8.0.0.CR1) (was: 8.0.0.Final) > Add deployment-scanner for singleton deployments > ------------------------------------------------ > > Key: WFLY-279 > URL: https://issues.jboss.org/browse/WFLY-279 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 9.0.0.CR1 > > > To simplify the use of singleton deployments in standalone mode, it would be nice to have a mechanism analogous to the hasingleton-deploy directory in AS6 and earlier. To do this, we can enhance the existing deployment-scanner to accept an additional policy attribute. Something like: > <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1"> > <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" policy="standard"/> > <deployment-scanner path="singleton-deployments" relative-to="jboss.server.base.dir" scan-interval="5000" policy="singleton"/> > </subsystem> -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-334) HA Singleton deployer for applications

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-334?page=com.atlassian.jira.plugin.s... ] Paul Ferraro updated WFLY-334: ------------------------------ Fix Version/s: 9.0.0.CR1 (was: 8.0.0.Final) > HA Singleton deployer for applications > -------------------------------------- > > Key: WFLY-334 > URL: https://issues.jboss.org/browse/WFLY-334 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering, Domain Management > Reporter: Wolf-Dieter Fink > Assignee: Paul Ferraro > Labels: deployers, hasingleton > Fix For: 9.0.0.CR1 > > > A HASingleton deployer should be provided in standalone and domain mode. > To be able to migrate such singleton applications from former AS versions. -- 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

1
0
0 / 0

[JBoss JIRA] (DROOLS-387) NoSuchElementException on addKnowledgePackages when a "not" follows an "eval"

by Jason Saint (JIRA)

[ https://issues.jboss.org/browse/DROOLS-387?page=com.atlassian.jira.plugin... ] Jason Saint commented on DROOLS-387: ------------------------------------ I tried with 5.6.0.CR1 and the packages were added to the knowledge base with no exceptions. It also works with 6.0.0.CR5. It looks like the underlying issue is fixed in the latest versions. > NoSuchElementException on addKnowledgePackages when a "not" follows an "eval" > ----------------------------------------------------------------------------- > > Key: DROOLS-387 > URL: https://issues.jboss.org/browse/DROOLS-387 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Environment: java version "1.7.0_21" > Reporter: Jason Saint > Assignee: Mark Proctor > > I apologize if this has already been reported, but I did not see anything in search results for which this looked like a duplicate. > With the following 2 rules, compiling the first and adding it to a knowledge base causes subsequent package additions to fail with a NoSuchElementException. > rule "Problem" > when > eval(true == true) > not String() from "Problem" > then > end > rule "Test1" > when > $test : String() from "Test" > then > end > The following java code will produce the exception on the second call to addKnowledgePackages (tried with Drools 5.4 and 5.5) > {code} > package com.chiprewards.droolsbug; > import org.drools.KnowledgeBase; > import org.drools.KnowledgeBaseFactory; > import org.drools.builder.KnowledgeBuilder; > import org.drools.builder.KnowledgeBuilderErrors; > import org.drools.builder.KnowledgeBuilderFactory; > import org.drools.io.Resource; > import org.drools.builder.ResourceType; > import org.drools.io.ResourceFactory; > /** > * Hello world! > * > */ > public class App > { > public static void main( String[] args ) > { > KnowledgeBase kBase = KnowledgeBaseFactory.newKnowledgeBase(); > KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder(); > > String problem_rule = "rule \"Problem\"\n when\n eval(true == true)\n not String() from \"Problem\"\n then\nend"; > > Resource resource = ResourceFactory.newByteArrayResource(problem_rule.getBytes()); > kbuilder.add(resource, ResourceType.DRL); > if(kbuilder.hasErrors()) { > System.out.println("First rule had error parsing"); > System.exit(1); > } > > kBase.addKnowledgePackages(kbuilder.getKnowledgePackages()); > > //Add second rule > > String next_rule = "rule \"Test\"\n when\n String() from \"Test\"\n then\nend"; > > resource = ResourceFactory.newByteArrayResource(next_rule.getBytes()); > kbuilder.add(resource, ResourceType.DRL); > if(kbuilder.hasErrors()) { > System.out.println("Second rule had error parsing"); > System.exit(1); > } > > kBase.addKnowledgePackages(kbuilder.getKnowledgePackages()); > } > } > {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

1
0
0 / 0

[JBoss JIRA] (DROOLS-389) Improve support for @Traitable POJOs and @Trait interfaces

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-389: ------------------------------------- Summary: Improve support for @Traitable POJOs and @Trait interfaces Key: DROOLS-389 URL: https://issues.jboss.org/browse/DROOLS-389 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Final, 5.5.0.Final Reporter: Davide Sottara Assignee: Davide Sottara Priority: Minor -- 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

1
0
0 / 0

[JBoss JIRA] (DROOLS-388) Inconsistent behavior of "contains" operator

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-388?page=com.atlassian.jira.plugin... ] Davide Sottara updated DROOLS-388: ---------------------------------- Description: The compiler accepts constraints such as {code} Person( fullName contains 'Jr' ) // should be fullName.contains('Jr') {code} Interestingly, MVEL evaluates it as the string operation "contains", but once the constraint is jitted it is again evaluated as a collection operator. That is, a rule such as: {code} when $s : String( this contains "foo" ) then {code} with inputs "foo1" .. "fooN" effectively fires an unpredictable number of times before starting to fail silently was: The compiler accepts constraints such as {code} Person( fullName contains 'Jr' ) // should be fullName.contains('Jr') {code} Interestingly, MVEL evaluates it as the string "contains", but once the constraint is jitted it is again evaluated as a collection operator. That is, a rule such as: {code} when $s : String( this contains "foo" ) then {code} with inputs "foo1" .. "fooN" effectively fires an unpredictable number of times before starting to fail silently > Inconsistent behavior of "contains" operator > -------------------------------------------- > > Key: DROOLS-388 > URL: https://issues.jboss.org/browse/DROOLS-388 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.1.Final, 6.0.0.Final > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Minor > > The compiler accepts constraints such as > {code} > Person( fullName contains 'Jr' ) // should be fullName.contains('Jr') > {code} > Interestingly, MVEL evaluates it as the string operation "contains", but > once the constraint is jitted it is again evaluated as a collection operator. > That is, a rule such as: > {code} > when > $s : String( this contains "foo" ) > then > {code} > with inputs "foo1" .. "fooN" effectively fires an unpredictable number of times before starting to fail silently -- 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

1
0
0 / 0

[JBoss JIRA] (DROOLS-388) Inconsistent behavior of "contains" operator

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-388: ------------------------------------- Summary: Inconsistent behavior of "contains" operator Key: DROOLS-388 URL: https://issues.jboss.org/browse/DROOLS-388 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Final, 5.5.1.Final Reporter: Davide Sottara Assignee: Mario Fusco Priority: Minor The compiler accepts constraints such as {code} Person( fullName contains 'Jr' ) // should be fullName.contains('Jr') {code} Interestingly, MVEL evaluates it as the string "contains", but once the constraint is jitted it is again evaluated as a collection operator. That is, a rule such as: {code} when $s : String( this contains "foo" ) then {code} with inputs "foo1" .. "fooN" effectively fires an unpredictable number of times before starting to fail silently -- 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

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 2013