May 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-818) Slave host does not register to DC when starting with --cached-dc and DC is available

by Jaromir Hamala (JIRA)

[ https://issues.jboss.org/browse/WFLY-818?page=com.atlassian.jira.plugin.s... ] Jaromir Hamala commented on WFLY-818: ------------------------------------- I'm afraid that this issue effectively makes DC to be a Single Point of Failure. You have these options: 1. starting the HC with --cached-dc, but it effectively downgrades it to a standalone mode as is never attempts to contact DC 2. do not use the --cached-dc, but than you HC will fail to start if DC is not available Given there is no guide how to make DC highly available, it's a very unfortunate situation and possible a showstopper for deploying JBoss. > Slave host does not register to DC when starting with --cached-dc and DC is available > ------------------------------------------------------------------------------------- > > Key: WFLY-818 > URL: https://issues.jboss.org/browse/WFLY-818 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Manel Martinez Gonzalez > > NOTE: this is related to AS7-4281 (see https://issues.jboss.org/browse/AS7-4281?focusedCommentId=12682058&page=c... ) > When a slave host is started with --cached-dc option it won't register to Domain Controller although it's available. domain.sh help says "If this host is not the Domain Controller and cannot contact the Domain Controller at boot, boot using a locally cached copy of the domain configuration (see --backup)" and this is not really happening because slave host never contact to DC with --cached-dc -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3666) kbase holds multiple KnowledgeBaseEventListenerWrapper instances when adding the same KnowledgeBaseEventListener multiple times

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3666?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated JBRULES-3666: --------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=868913, https://bugzilla.redhat.com/show_bug.cgi?id=958394 (was: https://bugzilla.redhat.com/show_bug.cgi?id=868913) > kbase holds multiple KnowledgeBaseEventListenerWrapper instances when adding the same KnowledgeBaseEventListener multiple times > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBRULES-3666 > URL: https://issues.jboss.org/browse/JBRULES-3666 > Project: JBRULES > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-core > Affects Versions: 5.5.0.Beta1 > Reporter: Toshiya Kobayashi > Assignee: Mario Fusco > Fix For: 5.5.0.Final > > > When you add the same KnowledgeBaseEventListener to kbase twice, kbase holds both KnowledgeBaseEventListenerWrapper instances. I'm not 100% sure if this is a bug but I guess KnowledgeBaseEventListenerWrapper should implement equals() method like StatefulKnowledgeSessionImpl$AgendaEventListenerWrapper. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3666) kbase holds multiple KnowledgeBaseEventListenerWrapper instances when adding the same KnowledgeBaseEventListener multiple times

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3666?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on JBRULES-3666: -------------------------------------------------- Toshiya Kobayashi <tkobayas(a)redhat.com> made a comment on [bug 958394|https://bugzilla.redhat.com/show_bug.cgi?id=958394] +++ This bug was initially created as a clone of Bug #868913 +++ Description of problem: Platform BZ for JBRULES-3666 Steps to Reproduce: Actual results: Expected results: I think the unit test which is sent as the pull request would be fine. https://github.com/droolsjbpm/drools/pull/153 --- Additional comment from JBoss JIRA Server on 2012-11-01 08:16:54 EDT --- Mario Fusco <mario.fusco(a)gmail.com> updated the status of jira JBRULES-3666 to Resolved > kbase holds multiple KnowledgeBaseEventListenerWrapper instances when adding the same KnowledgeBaseEventListener multiple times > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBRULES-3666 > URL: https://issues.jboss.org/browse/JBRULES-3666 > Project: JBRULES > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-core > Affects Versions: 5.5.0.Beta1 > Reporter: Toshiya Kobayashi > Assignee: Mario Fusco > Fix For: 5.5.0.Final > > > When you add the same KnowledgeBaseEventListener to kbase twice, kbase holds both KnowledgeBaseEventListenerWrapper instances. I'm not 100% sure if this is a bug but I guess KnowledgeBaseEventListenerWrapper should implement equals() method like StatefulKnowledgeSessionImpl$AgendaEventListenerWrapper. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3699) Large memory allocation per request in drools-camel-server

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3699?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated JBRULES-3699: --------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=882155, https://bugzilla.redhat.com/show_bug.cgi?id=958387 (was: https://bugzilla.redhat.com/show_bug.cgi?id=882155) > Large memory allocation per request in drools-camel-server > ---------------------------------------------------------- > > Key: JBRULES-3699 > URL: https://issues.jboss.org/browse/JBRULES-3699 > Project: JBRULES > Issue Type: Quality Risk > Security Level: Public(Everyone can see) > Components: drools-camel > Affects Versions: 5.4.0.Final > Reporter: Toshiya Kobayashi > Assignee: Mark Proctor > Attachments: JBoss_Benchmark_Request.xml, numbers.drl > > > In drools-camel-server, memory allocation during request/response message handling is quite larger than actual request/response size. > For example, with attached numbers.drl and JBoss_Benchmark_Request.xml, one SOAP request results in 45MB+ object allocation while the actual request size is 200KB and the response size is 650KB. They are short-lived objects so wouldn't be a memory leak but affect performance especially under high load. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3723) 'IDEOGRAPHIC SPACE' (U+3000) in DSL fails

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3723?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated JBRULES-3723: --------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=904038, https://bugzilla.redhat.com/show_bug.cgi?id=958385 (was: https://bugzilla.redhat.com/show_bug.cgi?id=904038) > 'IDEOGRAPHIC SPACE' (U+3000) in DSL fails > ----------------------------------------- > > Key: JBRULES-3723 > URL: https://issues.jboss.org/browse/JBRULES-3723 > Project: JBRULES > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-compiler-DSL > Affects Versions: 5.5.0.Final > Reporter: Toshiya Kobayashi > Assignee: Mark Proctor > > When DSL contains '　' (='IDEOGRAPHIC SPACE' (U+3000)), DSLMapLexer fails with "DSL lexer error" (Internally, it's a NoViableAltException). IDEOGRAPHIC SPACE is commonly used in Japan so please allow it to use. It doesn't mean that I want to use IDEOGRAPHIC SPACE as an alternative to ASCII whitespace. Just to use it as same as usual unicode characters. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3723) 'IDEOGRAPHIC SPACE' (U+3000) in DSL fails

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3723?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on JBRULES-3723: -------------------------------------------------- Toshiya Kobayashi <tkobayas(a)redhat.com> made a comment on [bug 958385|https://bugzilla.redhat.com/show_bug.cgi?id=958385] +++ This bug was initially created as a clone of Bug #904038 +++ Description of problem: Platform BZ for https://issues.jboss.org/browse/JBRULES-3723 Steps to Reproduce: 1. include '　' (='IDEOGRAPHIC SPACE' (U+3000)) in DSL. See the following pull request for test case. https://github.com/droolsjbpm/drools/pull/173 Actual results: kbuilder.add() fails with "DSL lexer error" Expected results: Being able to use '　' as usual unicode characters > 'IDEOGRAPHIC SPACE' (U+3000) in DSL fails > ----------------------------------------- > > Key: JBRULES-3723 > URL: https://issues.jboss.org/browse/JBRULES-3723 > Project: JBRULES > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-compiler-DSL > Affects Versions: 5.5.0.Final > Reporter: Toshiya Kobayashi > Assignee: Mark Proctor > > When DSL contains '　' (='IDEOGRAPHIC SPACE' (U+3000)), DSLMapLexer fails with "DSL lexer error" (Internally, it's a NoViableAltException). IDEOGRAPHIC SPACE is commonly used in Japan so please allow it to use. It doesn't mean that I want to use IDEOGRAPHIC SPACE as an alternative to ASCII whitespace. Just to use it as same as usual unicode characters. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3676) drl cann't debuging in Eclipse IDE

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3676?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on JBRULES-3676: -------------------------------------------------- Toshiya Kobayashi <tkobayas(a)redhat.com> made a comment on [bug 958381|https://bugzilla.redhat.com/show_bug.cgi?id=958381] +++ This bug was initially created as a clone of Bug #947741 +++ Description of problem: Platform BZ for https://issues.jboss.org/browse/JBRULES-3676 - BRMS 5.3.1.GA - JBDS 5.0.0.GA - Build id: v20120615-1714-H213-GA - Build date: 20120615-1714 Steps to Reproduce: 1. Create HelloWorld Drools example project 2. Set a breakpoint to RHS of Sample.drl 3. DroolsTest -> Debug As -> Drools Application Actual results: DroolsTest finishes without stopping at the breakpoint. Expected results: The debugging stops at the breakpoint. --- Additional comment from Toshiya Kobayashi on 2013-04-03 03:12:33 EDT --- *** Bug 881044 has been marked as a duplicate of this bug. *** > drl cann't debuging in Eclipse IDE > ---------------------------------- > > Key: JBRULES-3676 > URL: https://issues.jboss.org/browse/JBRULES-3676 > Project: JBRULES > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-core (expert) > Affects Versions: 5.5.0.CR1 > Environment: Eclipse 4.2，JDK1.7，Drools5.5CR1 > Reporter: hongkun an > Assignee: Mark Proctor > > i follow url content > http://docs.jboss.org/drools/release/5.2.0.Final/drools-expert-docs/html/... > I want debug drl example（HelloWord）in eclipse ide，but，only debug java file，cann't debug drl，why？ -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3676) drl cann't debuging in Eclipse IDE

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3676?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated JBRULES-3676: --------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=947741, https://bugzilla.redhat.com/show_bug.cgi?id=958381 (was: https://bugzilla.redhat.com/show_bug.cgi?id=947741) > drl cann't debuging in Eclipse IDE > ---------------------------------- > > Key: JBRULES-3676 > URL: https://issues.jboss.org/browse/JBRULES-3676 > Project: JBRULES > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-core (expert) > Affects Versions: 5.5.0.CR1 > Environment: Eclipse 4.2，JDK1.7，Drools5.5CR1 > Reporter: hongkun an > Assignee: Mark Proctor > > i follow url content > http://docs.jboss.org/drools/release/5.2.0.Final/drools-expert-docs/html/... > I want debug drl example（HelloWord）in eclipse ide，but，only debug java file，cann't debug drl，why？ -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1241) Don't add javaee.api as an implicit dependency, as it breaks excludes

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-1241?page=com.atlassian.jira.plugin.... ] Stuart Douglas updated WFLY-1241: --------------------------------- Summary: Don't add javaee.api as an implicit dependency, as it breaks excludes (was: Remove javaee module) > Don't add javaee.api as an implicit dependency, as it breaks excludes > --------------------------------------------------------------------- > > Key: WFLY-1241 > URL: https://issues.jboss.org/browse/WFLY-1241 > Project: WildFly > Issue Type: Task > Components: EE > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > Rather than having one module that imports all the JavaEE API's they should be imported individually so excludes will work. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1241) Remove javaee module

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-1241?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-1241: ------------------------------------ Assignee: Stuart Douglas (was: David Lloyd) > Remove javaee module > -------------------- > > Key: WFLY-1241 > URL: https://issues.jboss.org/browse/WFLY-1241 > Project: WildFly > Issue Type: Task > Components: EE > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > Rather than having one module that imports all the JavaEE API's they should be imported individually so excludes will work. -- 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

13 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 May 2013