September 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBRULES-3063) Drools should not allow set two rules with the same name for the same package

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3063?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated JBRULES-3063: --------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=724753 > Drools should not allow set two rules with the same name for the same package > ----------------------------------------------------------------------------- > > Key: JBRULES-3063 > URL: https://issues.jboss.org/browse/JBRULES-3063 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: drools-compiler > Affects Versions: 5.1.1.FINAL > Reporter: Alessandro Lazarotti > Assignee: Tihomir Surdilovic > Priority: Minor > Fix For: FUTURE > > > Drools should not allow set two rules with the same name for the same package > As expected, Drools does not allow us to define two rules with the same name in a same DRL file. > But if there are two rules with the same name, in the same package, but in separate files, no exception or warning is issued, just one rule overrides the other in silence. > From documentation: > "A rule must have a name, unique within its rule package. If a rule is defined twice in a single DRL, an error will appear when one loads it. If a DRL that includes a rule name already in the package is added, the previous rule is repalced."[1] > [1] http://docs.redhat.com/docs/en-US/JBoss_Enterprise_SOA_Platform/5/html/JB... > Different behavior for a similar action is not good. Both should alert user about a rule name repeated. > For large projects using a lot of DRL files can be hard to track mistakes occurred by rules override . It is really necessary provide an ERROR message for this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-552) Outline problems in DRL editor

by Dirk Bergstrom (JIRA)

Outline problems in DRL editor ------------------------------ Key: JBRULES-552 URL: http://jira.jboss.com/jira/browse/JBRULES-552 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.4 Reporter: Dirk Bergstrom Assigned To: Mark Proctor Priority: Minor Two (possibly related) problems with the outline view in the DRL editor: *) Rules that are commented out via a multi-line comment (/* ... */) still appear in the outline. *) Clicking on the name of a rule highlights some text near that rule. I assume it's supposed to highight the title of the rule, but it misses. Same thing affects the imports. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
5
0 / 0

[JBoss JIRA] Created: (AS7-1693) The jmx socket-binding should be configured to use the "management" interface

by Brian Stansberry (JIRA)

The jmx socket-binding should be configured to use the "management" interface ----------------------------------------------------------------------------- Key: AS7-1693 URL: https://issues.jboss.org/browse/AS7-1693 Project: Application Server 7 Issue Type: Task Components: Domain Management Affects Versions: 7.0.1.Final, 7.0.0.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.2.Final In the standard configs the jmx interface shouldn't be bound by default to the "public" interface, as users are likely to configure that interface to be open for insecure use. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (AS7-1704) Upgrade to Hibernate 4.0.0.CR2

by Scott Marlow (JIRA)

Upgrade to Hibernate 4.0.0.CR2 ------------------------------ Key: AS7-1704 URL: https://issues.jboss.org/browse/AS7-1704 Project: Application Server 7 Issue Type: Task Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.0.2.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
1
0 / 0

[JBoss JIRA] Moved: (AS7-1702) Accept <any-address/> in Jboss AS7 configuration

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/AS7-1702?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen moved ARQ-580 to AS7-1702: ---------------------------------------- Project: Application Server 7 (was: Arquillian) Key: AS7-1702 (was: ARQ-580) Affects Version/s: 7.0.1.Final (was: 1.0.0.CR4) Component/s: Test Suite (was: JBoss Containers) Security: (was: Public) > Accept <any-address/> in Jboss AS7 configuration > ------------------------------------------------ > > Key: AS7-1702 > URL: https://issues.jboss.org/browse/AS7-1702 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.0.1.Final > Environment: JBoss AS 7.0.1.Final > Reporter: Alexandre Gattiker > > ERROR ArquillianServiceDeployer - Cannot deploy arquillian service > java.lang.IllegalArgumentException > at org.jboss.dmr.ModelValue.asList(ModelValue.java:128) > at org.jboss.dmr.ModelNode.asList(ModelNode.java:1096) > at org.jboss.as.arquillian.container.ManagementClient.getInterface(ManagementClient.java:185) > at org.jboss.as.arquillian.container.ManagementClient.getBinding(ManagementClient.java:177) > at org.jboss.as.arquillian.container.ManagementClient.extractSubSystemURI(ManagementClient.java:148) > at org.jboss.as.arquillian.container.ManagementClient.getSubSystemURI(ManagementClient.java:90) > at org.jboss.as.arquillian.container.ManagementClient.getDeploymentMetaData(ManagementClient.java:96) > at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:98) > at org.jboss.as.arquillian.protocol.jmx.ArquillianServiceDeployer.doServiceDeploy(ArquillianServiceDeployer.java:58) > After changing the JBoss AS 7 configuration from: > <interface name="public"> > <inet-address value="127.0.0.1"/> > </interface> > to: > <interface name="public"> > <any-address/> > </interface> > Presumed cause: > in org.jboss.as.arquillian.container.ManagementClient in jboss-as-arquillian-common-7.0.1.Final.jar: > return rootNode.get("interface").get(name).get("criteria").asList().get(0).get("inet-address").asString(); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBBUILD-698) Could not maintain metadata on nexus repository

by Tomáš Remeš (JIRA)

Could not maintain metadata on nexus repository ----------------------------------------------- Key: JBBUILD-698 URL: https://issues.jboss.org/browse/JBBUILD-698 Project: JBoss Build System Issue Type: Bug Components: Artifact Repositories Reporter: Tomáš Remeš clicking on istack-commons-runtime 1.1.SNAPSHOT.jar gets "Could not maintain metadata. Nexus returned an error: ERROR 500: Internal Server Error" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-1356) Error starting shared transport causes future channels using it to fail

by Dennis Reed (JIRA)

Error starting shared transport causes future channels using it to fail ----------------------------------------------------------------------- Key: JGRP-1356 URL: https://issues.jboss.org/browse/JGRP-1356 Project: JGroups Issue Type: Bug Affects Versions: 2.6.20 Reporter: Dennis Reed Assignee: Bela Ban When a shared singleton transport started in Configurator#startProtocolStack throws an exception during TP#start, it is not rolled back. Future channels created with the same singleton transport try to use the failed instance. If there is an exception in start, either: - The transport should be removed or stopped, and future channels should try to start it again - The exception should be saved, and future channels using the same transport should get the same exception when started -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-1331) Digest: remove low seqno

by Bela Ban (JIRA)

Digest: remove low seqno ------------------------ Key: JGRP-1331 URL: https://issues.jboss.org/browse/JGRP-1331 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.1 We don't need Digest.Entry.low_seqno for NakReceiverWindow anymore. We only need it for the Retransmitter implementations. If we can remove that last dependency, e.g. by storing the last seqno removed from a retransmitter, we can remove low_seqno from a digest. This is significant, for example if we have 100 nodes, a digest includes 300 longs:(low+highest_received+highest_delivered) * 100. If we remove low_seqno, we only have 200 longs. (These will still be further compressed in a different JIRA). This is important for large clusters, to reduce the size of STABLE messages and views. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
11
0 / 0

[JBoss JIRA] Created: (JGRP-1358) Documentation problem with port_range

by Jean-Philippe Gariepy (JIRA)

Documentation problem with port_range ------------------------------------- Key: JGRP-1358 URL: https://issues.jboss.org/browse/JGRP-1358 Project: JGroups Issue Type: Bug Affects Versions: 2.12 Environment: Linux Reporter: Jean-Philippe Gariepy Assignee: Bela Ban Priority: Minor port_range for TCP is document as infinite if 0. This does not seem to be the case. If I start a second node, I got: Caused by: java.net.BindException: No available port to bind to in range [7800 .. 7800] at org.jgroups.util.Util.createServerSocket(Util.java:3051) at org.jgroups.blocks.TCPConnectionMap.<init>(TCPConnectionMap.java:88) at org.jgroups.blocks.TCPConnectionMap.<init>(TCPConnectionMap.java:55) at org.jgroups.protocols.TCP.createConnectionMap(TCP.java:130) at org.jgroups.protocols.TCP.start(TCP.java:64) at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:990) at org.jgroups.JChannel.startStack(JChannel.java:1784 0 is useful to indicate that only one port should be used (bind_port+0). Magic value for infinite should rather be -1. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1659) TestNG arquillian test in as-client mode not working

by Martin Kouba (JIRA)

TestNG arquillian test in as-client mode not working ---------------------------------------------------- Key: AS7-1659 URL: https://issues.jboss.org/browse/AS7-1659 Project: Application Server 7 Issue Type: Bug Components: Test Suite Reporter: Martin Kouba Assignee: Andrew Rubinger Priority: Blocker {code} {code} 15:07:52,888 WARN [org.jboss.modules] (MSC service thread 1-1) Failed to define class org.jboss.cditck.arquillian.client.ClientTest in Module "deployment.test.jar:main" from Service Module Loader: java.lang.LinkageError: Failed to link org/jboss/cditck/arquillian/client/ClientTest (Module "deployment.test.jar:main" from Service Module Loader) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:401) at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261) at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76) at org.jboss.modules.Module.loadModuleClass(Module.java:588) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:183) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:358) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:307) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:101) at org.jboss.as.weld.WeldModuleResourceLoader.classForName(WeldModuleResourceLoader.java:68) [jboss-as-weld-7.0.1.Final.jar:7.0.1.Final] at org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:82) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] at org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:134) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] at org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:191) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:368) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:81) [jboss-as-weld-7.0.1.Final.jar:7.0.1.Final] at org.jboss.as.weld.services.WeldService.start(WeldService.java:89) [jboss-as-weld-7.0.1.Final.jar:7.0.1.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22] Caused by: java.lang.NoClassDefFoundError: org/jboss/arquillian/testng/Arquillian at java.lang.ClassLoader.defineClass1(Native Method) [:1.6.0_22] at java.lang.ClassLoader.defineClass(ClassLoader.java:634) [:1.6.0_22] at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) [:1.6.0_22] at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:397) ... 19 more {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2011