January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2683) DroolsSession's initWorkItemManagerFactory method can not work in a OSGi context

by Antoine Toulme (JIRA)

DroolsSession's initWorkItemManagerFactory method can not work in a OSGi context -------------------------------------------------------------------------------- Key: JBRULES-2683 URL: https://jira.jboss.org/browse/JBRULES-2683 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.2.0.M1 Reporter: Antoine Toulme Assignee: Mark Proctor Fix For: FUTURE This affects the current trunk. The code in the method does this: String className = this.chainedProperties.getProperty( "drools.workItemManagerFactory", "org.drools.process.instance.impl.DefaultWorkItemManagerFactory" ); [..] clazz = (Class<WorkItemManagerFactory>) Thread.currentThread().getContextClassLoader().loadClass( className ); [..] clazz = (Class<WorkItemManagerFactory>) SessionConfiguration.class.getClassLoader().loadClass( className ); None of this can work for the default factory since drools-core does not depend on drools-flow-core (and creating a dependency would create a cycle). Actually, this won't work for customer code as well, since drools-core won't depend on their bundle. I suggest to use a declarative service to work around this problem, while keeping this type of instantiation around when OSGi is not on. -- 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

14 years

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-677) Setup integration testing

by Geoffrey De Smet (JIRA)

Setup integration testing ------------------------- Key: JBRULES-677 URL: http://jira.jboss.com/jira/browse/JBRULES-677 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Minor based on solver configs -- 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

14 years

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2251) The Solver's score calculation should be reusable without using the Solver itself. The examples should not know the Solver that intimetly and should not use the working memory directly.

by Geoffrey De Smet (JIRA)

The Solver's score calculation should be reusable without using the Solver itself. The examples should not know the Solver that intimetly and should not use the working memory directly. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2251 URL: https://jira.jboss.org/jira/browse/JBRULES-2251 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Components: drools-solver Affects Versions: 5.0.1.FINAL Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet -- 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

14 years

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2313) Tomcat memery leak with drools 4.0.7 or 5.0.1

by GREFFET Emmanuel (JIRA)

Tomcat memery leak with drools 4.0.7 or 5.0.1 ---------------------------------------------- Key: JBRULES-2313 URL: https://jira.jboss.org/jira/browse/JBRULES-2313 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.0.1.FINAL, 4.0.7 Environment: XP tomcat 5.5.9 Reporter: GREFFET Emmanuel Assignee: Mark Proctor Priority: Critical The memory is never released !!! (never ever ) when à Stop and Start or restart Tomcat. A made this test with a simple Drools call with a simple webapp and i tried with 4.0.7 and 5.0.1 drools version. The problem is the same. We need to stop tomcat process to release memory. Until this stop each Tomcat "Restart" with a drools call, will never release the memory. I made graphic with VisualWM, and we can see this problem ! I made a zip of my simple Eclipse project (webapp + drools) and word file for more information and screen copy of VisualVM. Thanks for help. Emmanuel GREFFET ( FRANCE) -- 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

14 years

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2811) Javadocs should aggregate all javadocs of all modules, but should use groups to distinguish them in the overview

by Geoffrey De Smet (JIRA)

Javadocs should aggregate all javadocs of all modules, but should use groups to distinguish them in the overview ---------------------------------------------------------------------------------------------------------------- Key: JBRULES-2811 URL: https://jira.jboss.org/browse/JBRULES-2811 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Components: drools-api Affects Versions: 5.1.1.FINAL Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Optional Fix For: FUTURE Aggregate: http://maven.apache.org/plugins/maven-javadoc-plugin/aggregate-mojo.html Groups: http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#gr... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1103) Tabu asperation based on stepscore

by Geoffrey De Smet (JIRA)

Tabu asperation based on stepscore ---------------------------------- Key: JBRULES-1103 URL: http://jira.jboss.com/jira/browse/JBRULES-1103 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Fix For: FUTURE Move tabu and property tabu could use "aspiration" Basically even if it's tabu, a move is accepted if the stepscore improves. For solution tabu this is pointless. Aspiration should occur on stepScore and NOT on decisionScore -- 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

14 years

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2694) New drools example: Phone call billing

by Geoffrey De Smet (JIRA)

New drools example: Phone call billing -------------------------------------- Key: JBRULES-2694 URL: https://jira.jboss.org/browse/JBRULES-2694 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-docs Affects Versions: 5.1.1.FINAL Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Fix For: FUTURE Move the example of bejug 2010 into drools-examples http://www.slideshare.net/ge0ffrey/drools-bejug-2010 => skip to slide 10 -- 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

14 years

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-8778) Problem with deployment order of EAR and JMS queues

by Frank Langelage (JIRA)

Problem with deployment order of EAR and JMS queues --------------------------------------------------- Key: JBAS-8778 URL: https://issues.jboss.org/browse/JBAS-8778 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers, JMS (HornetQ) Affects Versions: 6.0.0.Final Reporter: Frank Langelage Assignee: Ales Justin Our application deployed as one EAR file contains two MDB. The queues are defined in $JBOSS_HOME/deploy/hornetq/mbi2e-lafr-sb2000-ipc-hornetq-jms.xml: <?xml version="1.0" encoding="UTF-8"?> <configuration xmlns="urn:hornetq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:hornetq /schema/hornetq-jms.xsd"> <queue name="mbi2e-lafr-sb2000-ipc/MessageDistributorQueue"> <entry name="queue/mbi2e-lafr-sb2000-ipc/MessageDistributorQueue"/> </queue> <queue name="mbi2e-lafr-sb2000-ipc/SalesOrderImportQueue"> <entry name="queue/mbi2e-lafr-sb2000-ipc/SalesOrderImportQueue"/> </queue> </configuration> If I first startup JBossAS, already including the queue definitions shown above, and then deploy my ear file everything is fine. No Errors. But if I bounce and restart the engine after that, with everything deployed, I get Warnings and Errors. Right after the start of the MDB listening on the 'MessageDistributorQueue' I get this: 11:48:58,754 WARN [HornetQActivation] Failure in HornetQ activation org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@1fe97f9 destination=queue/mbi2e-lafr-sb2000-ipc/MessageDistributorQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15): HornetQException[errorCode=105 message=Unable to validate user: null for check type CONSUME for address jms.queue.mbi2e-lafr-sb2000-ipc/MessageDistributorQueue] at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:287) [:] at org.hornetq.core.client.impl.ClientSessionImpl.internalCreateConsumer(ClientSessionImpl.java:1556) [:] at org.hornetq.core.client.impl.ClientSessionImpl.createConsumer(ClientSessionImpl.java:447) [:] at org.hornetq.core.client.impl.ClientSessionImpl.createConsumer(ClientSessionImpl.java:392) [:] at org.hornetq.core.client.impl.DelegatingSession.createConsumer(DelegatingSession.java:201) [:] at org.hornetq.ra.inflow.HornetQMessageHandler.setup(HornetQMessageHandler.java:165) [:] at org.hornetq.ra.inflow.HornetQActivation.setup(HornetQActivation.java:291) [:] at org.hornetq.ra.inflow.HornetQActivation$SetupActivation.run(HornetQActivation.java:573) [:] at org.jboss.resource.work.WorkWrapper.run(WorkWrapper.java:172) [:6.0.1-SNAPSHOT] at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) [:2.0.0.CR7] at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:801) [:2.0.0.CR7] at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45) [:2.0.0.CR7] at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:821) [:2.0.0.CR7] at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [:2.0.0.CR7] And then a few more times during the further startup process I see this: 11:49:00,759 INFO [HornetQActivation] Attempting to reconnect org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@1fe97f9 destination=queue/mbi2e-lafr-sb2000-ipc/MessageDistributorQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15) 11:49:00,998 ERROR [HornetQActivation] Unable to reconnect org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@1fe97f9 destination=queue/mbi2e-lafr-sb2000-ipc/MessageDistributorQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15): HornetQException[errorCode=105 message=Unable to validate user: null for check type CONSUME for address jms.queue.mbi2e-lafr-sb2000-ipc/MessageDistributorQueue] at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:287) [:] at org.hornetq.core.client.impl.ClientSessionImpl.internalCreateConsumer(ClientSessionImpl.java:1556) [:] at org.hornetq.core.client.impl.ClientSessionImpl.createConsumer(ClientSessionImpl.java:447) [:] at org.hornetq.core.client.impl.ClientSessionImpl.createConsumer(ClientSessionImpl.java:392) [:] at org.hornetq.core.client.impl.DelegatingSession.createConsumer(DelegatingSession.java:201) [:] at org.hornetq.ra.inflow.HornetQMessageHandler.setup(HornetQMessageHandler.java:165) [:] at org.hornetq.ra.inflow.HornetQActivation.setup(HornetQActivation.java:291) [:] at org.hornetq.ra.inflow.HornetQActivation.handleFailure(HornetQActivation.java:539) [:] at org.hornetq.ra.inflow.HornetQActivation$SetupActivation.run(HornetQActivation.java:577) [:] at org.jboss.resource.work.WorkWrapper.run(WorkWrapper.java:172) [:6.0.1-SNAPSHOT] at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) [:2.0.0.CR7] at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:801) [:2.0.0.CR7] at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45) [:2.0.0.CR7] at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:821) [:2.0.0.CR7] at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [:2.0.0.CR7] At the very end of the startup process connect succeeds: 2010-12-28 11:49:09,133 INFO [org.hornetq.ra.inflow.HornetQActivation.info] (pool-1-thread-2) Attempting to reconnect org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@1fe97f9 destination=queue/mbi2e-lafr-sb2000-ipc/SalesOrderImportQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15) 2010-12-28 11:49:09,156 INFO [org.hornetq.ra.inflow.HornetQActivation.info] (pool-1-thread-1) Attempting to reconnect org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@1fe97f9 destination=queue/mbi2e-lafr-sb2000-ipc/MessageDistributorQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15) 2010-12-28 11:49:09,236 INFO [org.apache.coyote.http11.Http11Protocol.start] (Thread-2) Starting Coyote HTTP/1.1 on http-0.0.0.0-8080 2010-12-28 11:49:09,241 INFO [org.apache.coyote.http11.Http11Protocol.start] (Thread-2) Starting Coyote HTTP/1.1 on http-0.0.0.0-8443 2010-12-28 11:49:09,243 INFO [org.jboss.bootstrap.impl.base.server.AbstractServer.run] (Thread-2) JBossAS [6.0.1.SNAPSHOT "Neo"] Started in 3m:57s:688ms 2010-12-28 11:49:09,259 INFO [org.hornetq.ra.inflow.HornetQActivation.info] (pool-1-thread-1) Reconnected with HornetQ 2010-12-28 11:49:09,292 INFO [org.hornetq.ra.inflow.HornetQActivation.info] (pool-1-thread-2) Reconnected with HornetQ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

7
16
0 / 0

[JBoss JIRA] Created: (JGRP-1025) Harden FLUSH

by Bela Ban (JIRA)

Harden FLUSH ------------ Key: JGRP-1025 URL: https://jira.jboss.org/jira/browse/JGRP-1025 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Vladimir Blagojevic Fix For: 2.9 Make sure no FLUSH is left hanging, e.g. due to the crash of the flush leader after the START-FLUSH round. In other words, make analyze the code and make sure STOP-FLUSH is eventually called. -- 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

14 years, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JASSIST-127) interface proxy creation fails if there are methods with covariant return types

by Paul Pogonyshev (JIRA)

interface proxy creation fails if there are methods with covariant return types ------------------------------------------------------------------------------- Key: JASSIST-127 URL: https://jira.jboss.org/browse/JASSIST-127 Project: Javassist Issue Type: Bug Affects Versions: 3.12.0.GA Environment: Java 1.6. Reporter: Paul Pogonyshev Assignee: Shigeru Chiba Creation of proxy class for interface Bar fails: public interface Foo { Foo getSelf (); } public interface Bar extends Foo { Bar getSelf (); } This is because of covariant return types of method getSelf(). However, as this is permitted by the language (i.e. subtype can restrict the return type further), I consider this a bug. -- 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

14 years, 1 month

4
11
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 January 2011