November 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2719) Count in accumulate behaves incorrect in combination with update

by Wouter Horré (JIRA)

Count in accumulate behaves incorrect in combination with update ---------------------------------------------------------------- Key: JBRULES-2719 URL: https://jira.jboss.org/browse/JBRULES-2719 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.1.1.FINAL Reporter: Wouter Horré Assignee: Mark Proctor Attachments: count.zip The following rule produces different results when update is used in contrast to when retract/insert is used (when a Container instance has changed): rule "Count With Accumulate" when $l : Leaf(); Number($nb: intValue) from accumulate($c : Container(leafs contains $l), count($c)); then System.out.println("Leaf " + $l.getName() + " with accumulate: " + $nb); end The following rule produces the correct result in both cases: rule "Count With Collect" when $l : Leaf(); HashSet($nb : size) from collect(Container(leafs contains $l)); then System.out.println("Leaf " + $l.getName() + " with collect: " + $nb); end I have attached a minimal example that triggers the behavior. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2723) Block fireUntilHalt when a fact is inserted/updated/retracted, until all activations in response are complete

by Norman Chan (JIRA)

Block fireUntilHalt when a fact is inserted/updated/retracted, until all activations in response are complete ------------------------------------------------------------------------------------------------------------- Key: JBRULES-2723 URL: https://jira.jboss.org/browse/JBRULES-2723 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.1.1.FINAL Reporter: Norman Chan Assignee: Mark Proctor fireUntilHalt starts executing rule consequences as soon as any rule has been activated. This can be a problem if an event insertion, etc causes many rules to be activated in response. The agenda should determine which activated rule is executed first based on rule properties (e.g. salience), but because not all activations are complete when fireUntilHalt starts executing, the rule that is fired first may not be the one that should fire first. By blocking fireUntilHalt until all activations in response to a change in working memory are complete, activated rules will be executed in the correct order. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2492) Classloader issue in OSGi environment

by Tamas Cserveny (JIRA)

Classloader issue in OSGi environment ------------------------------------- Key: JBRULES-2492 URL: https://jira.jboss.org/jira/browse/JBRULES-2492 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.0.1.FINAL Environment: Eclipse RCP (Equinox) Reporter: Tamas Cserveny Assignee: Mark Proctor Fix For: 5.0.2 Drools creates for each property used in a rule file a new class. This class extends a Drools base class called "org.drools.base.extractors.BaseObjectClassFieldReader". For the creation it will only use the classloader that defined the asserted object, this has an implication: In case the classloader loaded the asserted object does not see the drools-core.jar then it will fail. Steps to preproduce: Create two bundles: "drools" and "entities" Assert an entity with is defined in the "entities" package and use at least one property. eg. rule "E!" when Entity( name == "E!" ) then end Workaround: Make sure that all classes in drools are visible in the entities. You can do that by: Add a dependency, Import the packages or by using the buddy loading policy settings. Desired solution: Currently the generated class is loaded by the ByteArrayClassLoader. This classloader has one parent defined. The solution should be to set a composite classloader as parent. This classloader would first try to load the class in the classloader currently set and the would try two other alternatives: 1. the classloader which defined one of the classes in the drools-core.jar 2. the classloader set in the PackafgeBuilder config. This would ensure that the drools packages would be found correctly without effecting current behaviour. -- 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

15 years

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-7837) Replace JBossCache with Infinispan

by Brian Stansberry (JIRA)

Replace JBossCache with Infinispan ---------------------------------- Key: JBAS-7837 URL: https://jira.jboss.org/jira/browse/JBAS-7837 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Priority: Critical Fix For: JBossAS-6.0.0.M4 Use Infinispan 4.x (currently 4.0; expectation is to use 4.1) as the distributed caching provider for JBoss AS. This is meant as a parent issue for the overall task; the main work will be encapsulated in subtasks or dependent issues. -- 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

15 years

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-8421) Upgrade to WEld 1.1.0.CR1

by Pete Muir (JIRA)

Upgrade to WEld 1.1.0.CR1 ------------------------- Key: JBAS-8421 URL: https://jira.jboss.org/browse/JBAS-8421 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Weld/CDI Reporter: Pete Muir Assignee: Marius Bogoevici We aim to upgrade to Weld 1.1.0.CR1 in time for AS 6 CR1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8607) AS7 build causes PermGen error

by Thomas Diesler (JIRA)

AS7 build causes PermGen error ------------------------------ Key: JBAS-8607 URL: https://jira.jboss.org/browse/JBAS-8607 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.0.0.Alpha2 On my EC2 Hudson instance I frequently see errors like this [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.2:single (assemble) on project jboss-as-build: Execution assemble of goal org.apache.maven.plugins:maven-assembly-plugin:2.2:single failed: Unable to load the mojo 'single' (or one of its required components) from the plugin 'org.apache.maven.plugins:maven-assembly-plugin:2.2': com.google.inject.ProvisionException: Guice provision errors: [ERROR] ... [ERROR] [ERROR] 1 error: com.google.inject.internal.util.ComputationException: java.lang.OutOfMemoryError: PermGen space This is running on a 'small' instance with 1.7G Ram. Setting the global MAVEN_OPTS to something like: -Xmx512m -XX:MaxPermSize=512m does not help I propose to put the distro assembly in a mvn profile -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
3
0 / 0

[JBoss JIRA] Updated: (JBAS-8093) Weld should visibly log when /WEB-INF/beans.xml is not found.

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8093?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici updated JBAS-8093: ----------------------------------- Priority: Optional (was: Major) > Weld should visibly log when /WEB-INF/beans.xml is not found. > ------------------------------------------------------------- > > Key: JBAS-8093 > URL: https://jira.jboss.org/browse/JBAS-8093 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Weld/CDI > Reporter: Lincoln Baxter III > Assignee: Pete Muir > Priority: Optional > Fix For: TBD > > > An INFO or WARNING level log message must be displayed when loading a web-application where /WEB-INF/beans.xml is missing. > "/WEB-INF/beans.xml is not present - Beans in WAR " +warName+ " will not be loaded." > The user needs to know this because weld is making an important decision. Also, a common pitfall, defining EJBs with @Injected dependencies will break because the EJB's are discovered, @Injection is attempted, but fails because no other beans were loaded. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-8483) errors injecting the Weld BeanManager.

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8483?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici closed JBAS-8483. ---------------------------------- Resolution: Out of Date Closing this, as other similar JNDI-related issues are fixed as well. > errors injecting the Weld BeanManager. > -------------------------------------- > > Key: JBAS-8483 > URL: https://jira.jboss.org/browse/JBAS-8483 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld/CDI > Affects Versions: 6.0.0.M5 > Environment: jboss as 6 milestone 5 > Reporter: nimo stephan > Assignee: Marius Bogoevici > > The same weld-war does work in jboss as 6 milestone 4. Deploying it in jboss as 6 milestone 5 does work, only when invoking a bean, then weld throws exception: > (The full stacktrace can be seen here: http://community.jboss.org/thread/157055) > 10:57:33,719 SEVERITY [javax.enterprise.resource.webcontainer.jsf.application] javax.ejb.EJBException: java.lang.RuntimeException: Unable to inject jndi dependency: env/org.jboss.weld.integration.ejb.SessionBeanInterceptor/beanManager into property org.jboss.weld.integration.ejb.SessionBeanInterceptor.beanManager: MyWAR not bound: javax.faces.el.EvaluationException: javax.ejb.EJBException: java.lang.RuntimeException: Unable to inject jndi dependency: env/org.jboss.weld.integration.ejb.SessionBeanInterceptor/beanManager into property org.jboss.weld.integration.ejb.SessionBeanInterceptor.beanManager: MyWAR not bound > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) [:2.0.2-FCS] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-8288) Interceptors and decorators defined on stateful EJBs must be passivated/activated

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8288?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici updated JBAS-8288: ----------------------------------- Issue Type: Feature Request (was: Bug) Affects Version/s: TBD Priority: Optional (was: Major) > Interceptors and decorators defined on stateful EJBs must be passivated/activated > --------------------------------------------------------------------------------- > > Key: JBAS-8288 > URL: https://jira.jboss.org/browse/JBAS-8288 > Project: JBoss Application Server > Issue Type: Feature Request > Components: Weld/CDI > Affects Versions: TBD > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > Priority: Optional > Fix For: 6.0.0.CR1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-8284) SFSB proxies not serializable in JBoss AS

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8284?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici closed JBAS-8284. ---------------------------------- Resolution: Duplicate Issue Duplicates JBAS-8293 > SFSB proxies not serializable in JBoss AS > ----------------------------------------- > > Key: JBAS-8284 > URL: https://jira.jboss.org/browse/JBAS-8284 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld/CDI > Reporter: David Allen > Fix For: 6.0.0.CR1 > > > The deserialization of a client proxy for a stateful session bean fails in JBoss AS. It appears to be serializing Microkernel classes in the object graph which are naturally not available to the classloader of the test application during deserialization. > This is demonstrated by test org.jboss.jsr299.tck.tests.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest.testSerializeSFSB(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

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 November 2010