October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-287) Rule names with non-alphabetic characters may lead to name clashes

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-287?page=com.atlassian.jira.plugin... ] Geoffrey De Smet updated DROOLS-287: ------------------------------------ Description: A KB with the two following rules will not compile: {code} rule "Rule_>" when then end rule "Rule_<" when then end {code} Here's a more realistic example: {code} rule "dollar > euro" when then end rule "dollar < euro" when then end {code} was: A KB with the two following rules will not compile: rule "Rule_>" when then end rule "Rule_<" when then end > Rule names with non-alphabetic characters may lead to name clashes > ------------------------------------------------------------------ > > Key: DROOLS-287 > URL: https://issues.jboss.org/browse/DROOLS-287 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.CR4 > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Critical > Fix For: 5.5.1.Final, 6.0.0.CR5 > > > A KB with the two following rules will not compile: > {code} > rule "Rule_>" > when then end > rule "Rule_<" > when then end > {code} > Here's a more realistic example: > {code} > rule "dollar > euro" > when then end > rule "dollar < euro" > when then end > {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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-287) Rule names with non-alphabetic characters may lead to name clashes

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-287?page=com.atlassian.jira.plugin... ] Geoffrey De Smet edited comment on DROOLS-287 at 10/6/13 3:32 AM: ------------------------------------------------------------------ That's probably because Java classnames can't contain "<" or ">" and the rules becomes java class files. A solution to this is escaping, for example with the "$" character: "Rule_>" becomes "Rule_$gt$" "Rule_<" becomes "Rule_$lt$" "Rule_$" becomes "Rule_$dollar$" "Rule_£" becomes "Rule_$u1245$" (presuming that 1245 is the unicode for £) "Rule a" becomes "Rule$space$a" "Rule a" becomes "Rule$space$$space$a" was (Author: ge0ffrey): That's probably because Java classnames can't contain "<" or ">" and the rules becomes java class files. A solution to this is escaping, for example with the "$" character: "Rule_>" becomes "Rule_$gt$" "Rule_<" becomes "Rule_$lt$" "Rule_$" becomes "Rule_$dollar$" "Rule_£" becomes "Rule_$u1245$" (presuming that 1245 is the unicode for £. "Rule a" becomes "Rule$space$a" "Rule a" becomes "Rule$space$$space$a" > Rule names with non-alphabetic characters may lead to name clashes > ------------------------------------------------------------------ > > Key: DROOLS-287 > URL: https://issues.jboss.org/browse/DROOLS-287 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.CR4 > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Critical > Fix For: 5.5.1.Final, 6.0.0.CR5 > > > A KB with the two following rules will not compile: > rule "Rule_>" > when then end > rule "Rule_<" > when then end -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-287) Rule names with non-alphabetic characters may lead to name clashes

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-287?page=com.atlassian.jira.plugin... ] Geoffrey De Smet commented on DROOLS-287: ----------------------------------------- That's probably because Java classnames can't contain "<" or ">" and the rules becomes java class files. A solution to this is escaping for example with the "$" character: "Rule_>" becomes "Rule_$gt$" "Rule_<" becomes "Rule_$lt$" "Rule_$" becomes "Rule_$dollar$" "Rule_£" becomes "Rule_$u1245$" (presuming that 1245 is the unicode for £. "Rule a" becomes "Rule$space$a" "Rule a" becomes "Rule$space$$space$a" > Rule names with non-alphabetic characters may lead to name clashes > ------------------------------------------------------------------ > > Key: DROOLS-287 > URL: https://issues.jboss.org/browse/DROOLS-287 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.CR4 > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Critical > Fix For: 5.5.1.Final, 6.0.0.CR5 > > > A KB with the two following rules will not compile: > rule "Rule_>" > when then end > rule "Rule_<" > when then end -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-287) Rule names with non-alphabetic characters may lead to name clashes

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-287?page=com.atlassian.jira.plugin... ] Geoffrey De Smet edited comment on DROOLS-287 at 10/6/13 3:32 AM: ------------------------------------------------------------------ That's probably because Java classnames can't contain "<" or ">" and the rules becomes java class files. A solution to this is escaping, for example with the "$" character: "Rule_>" becomes "Rule_$gt$" "Rule_<" becomes "Rule_$lt$" "Rule_$" becomes "Rule_$dollar$" "Rule_£" becomes "Rule_$u1245$" (presuming that 1245 is the unicode for £. "Rule a" becomes "Rule$space$a" "Rule a" becomes "Rule$space$$space$a" was (Author: ge0ffrey): That's probably because Java classnames can't contain "<" or ">" and the rules becomes java class files. A solution to this is escaping for example with the "$" character: "Rule_>" becomes "Rule_$gt$" "Rule_<" becomes "Rule_$lt$" "Rule_$" becomes "Rule_$dollar$" "Rule_£" becomes "Rule_$u1245$" (presuming that 1245 is the unicode for £. "Rule a" becomes "Rule$space$a" "Rule a" becomes "Rule$space$$space$a" > Rule names with non-alphabetic characters may lead to name clashes > ------------------------------------------------------------------ > > Key: DROOLS-287 > URL: https://issues.jboss.org/browse/DROOLS-287 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.CR4 > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Critical > Fix For: 5.5.1.Final, 6.0.0.CR5 > > > A KB with the two following rules will not compile: > rule "Rule_>" > when then end > rule "Rule_<" > when then end -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2224) CLI doesn't exit batch mode when failures occur in run-batch

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFLY-2224?page=com.atlassian.jira.plugin.... ] Alexey Loubyansky commented on WFLY-2224: ----------------------------------------- Yes, it is intentional and is described in the help content for the command. > CLI doesn't exit batch mode when failures occur in run-batch > ------------------------------------------------------------ > > Key: WFLY-2224 > URL: https://issues.jboss.org/browse/WFLY-2224 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 8.0.0.Beta1 > Reporter: Brian Stansberry > Assignee: Alexey Loubyansky > Fix For: 8.0.0.CR1 > > > If you execute a batch that fails, the CLI remains in batch mode. > [domain@localhost:9990 /] batch > [domain@localhost:9990 / #] /profile=test:add > #1 /profile=test:add > [domain@localhost:9990 / #] :bogus > #2 /:bogus > [domain@localhost:9990 / #] run-batch > JBAS014884: No operation named 'bogus' exists at address [] > [domain@localhost:9990 / #] > This might be intentional (e.g. to let me fix a typo in my ":bogus" op), but if so, perhaps some output explaining that would be good? And for non-interactive mode staying in the batch seems wrong. > The same problem occurs in the EAP branch, which is where I first noticed it when investigating another issue. In that case the :bogus command wasn't bogus but was a proper op that failed for legitimate reasons. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2225) Mutated AtomicInteger/Long session attributes are not replicated

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-2225: ---------------------------------- Summary: Mutated AtomicInteger/Long session attributes are not replicated Key: WFLY-2225 URL: https://issues.jboss.org/browse/WFLY-2225 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 8.0.0.Beta1 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 8.0.0.CR1 The logic in CacheMutator treats all Number subclasses as immutable. However, AtomicInteger and AtomicLong both extend Number, but are mutable. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1858) Add RBAC sensitivity classification constraints to undertow subsystem

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1858?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-1858: ----------------------------------- Priority: Blocker (was: Major) > Add RBAC sensitivity classification constraints to undertow subsystem > --------------------------------------------------------------------- > > Key: WFLY-1858 > URL: https://issues.jboss.org/browse/WFLY-1858 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management, Web (Undertow) > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > Priority: Blocker > Labels: RBAC-WF-only > Fix For: 8.0.0.CR1 > > > The current RBAC work updated the web subsystem but not undertow. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2224) CLI doesn't exit batch mode when failures occur in run-batch

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-2224: -------------------------------------- Summary: CLI doesn't exit batch mode when failures occur in run-batch Key: WFLY-2224 URL: https://issues.jboss.org/browse/WFLY-2224 Project: WildFly Issue Type: Bug Components: CLI Affects Versions: 8.0.0.Beta1 Reporter: Brian Stansberry Assignee: Alexey Loubyansky Fix For: 8.0.0.CR1 If you execute a batch that fails, the CLI remains in batch mode. [domain@localhost:9990 /] batch [domain@localhost:9990 / #] /profile=test:add #1 /profile=test:add [domain@localhost:9990 / #] :bogus #2 /:bogus [domain@localhost:9990 / #] run-batch JBAS014884: No operation named 'bogus' exists at address [] [domain@localhost:9990 / #] This might be intentional (e.g. to let me fix a typo in my ":bogus" op), but if so, perhaps some output explaining that would be good? And for non-interactive mode staying in the batch seems wrong. The same problem occurs in the EAP branch, which is where I first noticed it when investigating another issue. In that case the :bogus command wasn't bogus but was a proper op that failed for legitimate reasons. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-349) FreeBSD isThreadCpuTimeSupported

by Alexander Yerenkow (JIRA)

[ https://issues.jboss.org/browse/WFLY-349?page=com.atlassian.jira.plugin.s... ] Alexander Yerenkow commented on WFLY-349: ----------------------------------------- Please, take a look at this pull request https://github.com/wildfly/wildfly/pull/5223 It should close this issue. > FreeBSD isThreadCpuTimeSupported > -------------------------------- > > Key: WFLY-349 > URL: https://issues.jboss.org/browse/WFLY-349 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Environment: FreeBSD 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > openjdk6/openjdk7 > Reporter: Alexander Yerenkow > Fix For: 8.0.0.CR1 > > > Platform Tests should be modified, since it's not respecting when isThreadCpuTimeSupported = false (It continues run some test with isThreadCpuTimeSupported, which produces Exceptions, and all test failed); > Simple test: > ThreadMXBean threadMXBean = ManagementFactory.getThreadMXBean(); > System.out.println("threadMXBean.isThreadCpuTimeSupported() = " + threadMXBean.isThreadCpuTimeSupported()); > System.out.println("threadMXBean.isThreadCpuTimeEnabled() = " + threadMXBean.isThreadCpuTimeEnabled()); > Result: > threadMXBean.isThreadCpuTimeSupported() = false > Exception in thread "main" java.lang.UnsupportedOperationException: Thread CPU time measurement is not supported > at sun.management.ThreadImpl.isThreadCpuTimeEnabled(ThreadImpl.java:98) > at Test.main(Test.java:19) -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBAS-9549) The UDP port opened for all IPs in the JBoss 7 standalone configuration

by Michael Furman (JIRA)

[ https://issues.jboss.org/browse/JBAS-9549?page=com.atlassian.jira.plugin.... ] Michael Furman updated JBAS-9549: --------------------------------- Attachment: standalone.xml The configuration > The UDP port opened for all IPs in the JBoss 7 standalone configuration > ----------------------------------------------------------------------- > > Key: JBAS-9549 > URL: https://issues.jboss.org/browse/JBAS-9549 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security > Reporter: Michael Furman > Assignee: Anil Saldhana > Attachments: standalone.xml > > > The bug is for Jboss 7.1.1.Final (I was not able to select it when I opened the issue) > I launched Jboss 7.1.1.Final on Centos6 using JDK7. > When I check what ports are opened I see the following UDP port opened for all IPs: > > netstat -ntulp > Active Internet connections (only servers) > Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name > udp 0 0 :::43676 :::* 2460/java > > The port is changing its value each time I restart JBoss. > Where and why the UDP port is configured? > > I use `standalone\configuration\standalone.xml` and I can not find any UDP configuration there. > > I still can see opened UDP port and I want to close it. -- 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

11 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2013