May 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCLUSTER-184) Explore use of ClusteredCacheLoader to avoid state transfer

by Brian Stansberry (JIRA)

Explore use of ClusteredCacheLoader to avoid state transfer ----------------------------------------------------------- Key: JBCLUSTER-184 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-184 Project: JBoss Clustering Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry With CCL a cache miss results in a get call around the cluster. Can eliminate the need for in-memory state transfer. Won't work with buddy replication, but could be very interesting with total replication. Need to think through issues with things like passivation. -- 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

12 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-140) Examine need for a distributed service registry outside the AS

by Brian Stansberry (JIRA)

Examine need for a distributed service registry outside the AS -------------------------------------------------------------- Key: JBCLUSTER-140 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-140 Project: JBoss Clustering Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q3Y6 Is something like DRM needed outside the AS? If it is, do we want to use the JBoss Cache based version (creates JBC dependency.) DRM is used in two ways: 1) To maintain a distributed registry of remote invocation targets. 2) To maintain a distributed registry of services, which is done by having the service register a meaningless token under its key rather than a target. This is used by HASingleton. Need to examine whether this kind of thing is needed by Messaging, or whether simple listening for view changes is sufficient. Listening for view changes could be sufficient if each group member knew how to create a Remoting InvokerLocator for the other members based on the JGroups Address. But, this presupposes use of consistent ports across the cluster, and that the IP address used by JGroups is the one that Messaging traffic should use. -- 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

12 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-144) Consider other clustering code that can be removed from the AS

by Brian Stansberry (JIRA)

Consider other clustering code that can be removed from the AS -------------------------------------------------------------- Key: JBCLUSTER-144 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-144 Project: JBoss Clustering Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q4Y6 Things like the http session replication code that we've considered integrating into Tomcat. -- 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

12 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-141) Create a generic HA Singleton API

by Brian Stansberry (JIRA)

Create a generic HA Singleton API --------------------------------- Key: JBCLUSTER-141 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-141 Project: JBoss Clustering Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q3Y6 Also want to extract the HASingletonElectionPolicy code from the AS codebase. -- 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

12 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBJCA-77) Verify OSGi information in all manifests

by Jesper Pedersen (JIRA)

Verify OSGi information in all manifests ---------------------------------------- Key: JBJCA-77 URL: https://jira.jboss.org/jira/browse/JBJCA-77 Project: JBoss JCA Issue Type: Task Components: Common, Core, Deployer Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Blocker Fix For: 1.0.0.Beta1 Verify that the OSGi information in all the MANIFEST.MF files are correct. This information needs to be kept in sync from this point on. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-6185) JBoss MBeans in JConsole no longer works

by jaikiran pai (JIRA)

JBoss MBeans in JConsole no longer works ----------------------------------------- Key: JBAS-6185 URL: https://jira.jboss.org/jira/browse/JBAS-6185 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-5.0.0.CR2 Environment: JBossAS-5 CR2, Sun Java 1.5, Windows 2003 Reporter: jaikiran pai Assignee: Dimitris Andreadis Displaying of JBoss MBeans in JConsole as explained here http://www.jboss.org/community/docs/DOC-10521 , no longer works because of the classpath issue. Maybe related to the refactoring of org\jboss\system\server\jmx\* classes into jboss-system-jmx.jar in JBoss-5. More details about this issue can be found in the linked forum thread. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

11
23
0 / 0

[JBoss JIRA] Created: (JBRULES-1699) BRMS: Cannot easily remove data when creating a test scenario

by Jaroslaw Kijanowski (JIRA)

BRMS: Cannot easily remove data when creating a test scenario ------------------------------------------------------------- Key: JBRULES-1699 URL: https://jira.jboss.org/jira/browse/JBRULES-1699 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.M1 Reporter: Jaroslaw Kijanowski Assignee: Michael Neale Fix For: 5.0.0.M2 I create a test scenario and add a fact in the Given section. If I want to remove it, I have to add a field. Then two "minus" signs appear, on for the field and one for the whole fact. Same for the Expect section and globals. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

5
12
0 / 0

[JBoss JIRA] Created: (JBRULES-1908) updated Drools docs content from SOA 4.2.CP03 Rules Guide

by Darrin Mison (JIRA)

updated Drools docs content from SOA 4.2.CP03 Rules Guide --------------------------------------------------------- Key: JBRULES-1908 URL: https://jira.jboss.org/jira/browse/JBRULES-1908 Project: JBoss Drools Issue Type: Task Security Level: Public (Everyone can see) Components: drools-docs-expert Reporter: Darrin Mison Assignee: Mark Proctor I revised the language of the "Insertion" section while fixing a couple of reported grammatical errors for the 4.2.CP03 SOA Rules Guide. The original language is the same in: http://anonsvn.jboss.org/repos/labs/labs/jbossrules/soa_tags/4.3.0.FP01_B... , so these changes would also apply to the most recent docs. Updated content below, the section ids are different but you get the idea ;-) <section id="sect-JBoss_Rules_Reference_Manual-WorkingMemory_and_StatefulStateless_Sessions-Insertion"> <title>Insertion</title> <para> <firstterm>Insertion</firstterm> is the act of telling the WorkingMemory about the facts. </para> <important> <para> In many Expert Systems the term used for this concept is <firstterm>assert</firstterm> or <firstterm>assertion</firstterm>. However as the keyword <methodname>assert</methodname> is already used in many languages, Drools uses the keyword & term <methodname>insert</methodname>. You will often encounter these terms used interchangably in discussion of Rules Engines. </para> </important> <para> When inserted, the rule is examined for matches against the rules. The work of determining what rules to fire is done during insertion, but no rules are executed at this time. The rules are executed when <methodname>fireAllRules()</methodname> is called, and it should only be called after you have inserted all your facts. </para> <para> It is a common misconception that rule matching occurs when <methodname>fireAllRules()</methodname> is called. </para> <para> When an Object is inserted it returns a FactHandle. This FactHandle is the token used to represent your inserted Object inside the WorkingMemory, it is also how you will interact with the Working Memory when you wish to retract or modify an object. </para> <programlisting language="java">Cheese stilton = new Cheese("stilton"); FactHandle stiltonHandle = session.insert( stilton );</programlisting> <para> As mentioned in <xref linkend="sect-JBoss_Rules_Reference_Manual-The_Drools_Rule_Engine-RuleBase" /> a Working Memory can operate in two assertions modes: <firstterm>equality</firstterm> and <firstterm>identity</firstterm>. Identity is the default mode. The assertion mode determines how the Working Memory stores the facts and how it compares the newly inserted fact to previously inserted ones. If the Working Memory determines the fact to "be the same" as an already inserted one it will ignore the new fact and return the FactHandle for the previously inserted one. </para> <variablelist> <varlistentry> <term>Identity</term> <listitem> <para> Identity Mode uses an <classname>IdentityHashMap</classname>to store all asserted Objects. New facts being inserted are compared to existing facts "by reference". A new FactHandle will be returned if the object being inserted is not a reference to an object that has been inserted previously. </para> </listitem> </varlistentry> <varlistentry> <term>Equality</term> <listitem> <para> Equality Mode uses a <classname>HashMap</classname> to store all asserted Objects. New facts being inserted are compared to existing facts "by value". A new FactHandle will be returned if the content of the object is not identical to that of a previously inserted object. </para> </listitem> </varlistentry> </variablelist> </section> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

5
7
0 / 0

[JBoss JIRA] Created: (JBCL-84) Extend the ClassLoadingMetaData filtered package semantics

by Adrian Brock (JIRA)

Extend the ClassLoadingMetaData filtered package semantics ---------------------------------------------------------- Key: JBCL-84 URL: https://jira.jboss.org/jira/browse/JBCL-84 Project: JBoss ClassLoader Issue Type: Feature Request Components: MetaData Reporter: Adrian Brock Currently the ClassLoadingMetaData has some includedPackages and excludedPackages metadata. This is just a comma seperated list of explicit package names. This metadata should be extended to make it more flexible. e.g. using globing <classloader> <excluded type="glob">com.foo.*</included> or explicitly naming the filter <classloader> <excluded class="com.foo.MyClassFilter>...</excluded> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1135) Move generation should be described in a drl

by Geoffrey De Smet (JIRA)

Move generation should be described in a drl -------------------------------------------- Key: JBRULES-1135 URL: http://jira.jboss.com/jira/browse/JBRULES-1135 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Solver Affects Versions: 4.0.0.GA Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Fix For: FUTURE instead of MoveFactory POJO -- 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

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2009