January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBRULES-3351) Settings a termination config list will not create the Termination instance

by Patrik Dufresne (JIRA)

Patrik Dufresne created JBRULES-3351: ---------------------------------------- Summary: Settings a termination config list will not create the Termination instance Key: JBRULES-3351 URL: https://issues.jboss.org/browse/JBRULES-3351 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-planner Affects Versions: 5.3.1.Final Environment: N/A Reporter: Patrik Dufresne Assignee: Geoffrey De Smet Setting a sub termination config list using TerminationConfig.setTerminationConfigList(List<TerminationConfig>) will not create the termination when buildTermination is called. The problem is due to an error in TerminationConfig.java:179. if (terminationConfigList != null && terminationConfigList.isEmpty()) { for (TerminationConfig terminationConfig : terminationConfigList) { Termination termination = terminationConfig.buildTermination(scoreDefinition); if (termination != null) { terminationList.add(termination); } } } The boolean expression terminationConfigList.isEmpty() should become !terminationConfigList.isEmpty(). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] (JBRULES-3356) Accumulate function cannot be used directly from lhs

by Edson Tirelli (JIRA)

Edson Tirelli created JBRULES-3356: -------------------------------------- Summary: Accumulate function cannot be used directly from lhs Key: JBRULES-3356 URL: https://issues.jboss.org/browse/JBRULES-3356 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.4.0.Beta1, 5.3.1.Final Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.3.2.Final, 5.4.0.Beta2 Description of problem: Since support to multi-function accumulate has been added in 5.2, it would be nice to be able to use accumulate directly in lhs in Rule API like newRule().name("whatever").lhs().accumulate() which is impossible now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
2
0 / 0

[JBoss JIRA] (JBRULES-3354) Unable to construct expressions containing 'from' using Rules API

by Edson Tirelli (JIRA)

Edson Tirelli created JBRULES-3354: -------------------------------------- Summary: Unable to construct expressions containing 'from' using Rules API Key: JBRULES-3354 URL: https://issues.jboss.org/browse/JBRULES-3354 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.4.0.Beta1, 5.3.1.Final Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.3.2.Final, 5.4.0.Beta2 Description of problem: When trying to construct a new rule containing 'from' I can't continue constructing the rule due to error: "The method rhs(String) is undefined for the type capture#3-of ?" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
4
0 / 0

[JBoss JIRA] (JBRULES-3353) Drools Grid: Remote KnowledgeBuilderConfiguration throws NullPointerException

by Jens Rohloff (JIRA)

Jens Rohloff created JBRULES-3353: ------------------------------------- Summary: Drools Grid: Remote KnowledgeBuilderConfiguration throws NullPointerException Key: JBRULES-3353 URL: https://issues.jboss.org/browse/JBRULES-3353 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.4.0.Beta1 Reporter: Jens Rohloff Assignee: Mark Proctor Adding a AccumulateFunctionOption to a GridNode throws NullPointerException. java.lang.NullPointerException at org.drools.command.runtime.KBuilderSetPropertyCommand.execute(KBuilderSetPropertyCommand.java:42) at org.drools.command.runtime.KBuilderSetPropertyCommand.execute(KBuilderSetPropertyCommand.java:27) at org.drools.grid.impl.GridNodeServer$1$1.execute(GridNodeServer.java:74) at org.drools.grid.impl.GridNodeServer.messageReceived(GridNodeServer.java:48) at org.drools.grid.impl.MultiplexSocket.messageReceived(MultiplexSocket.java:25) at org.drools.grid.remote.mina.MinaIoHandler.messageReceived(MinaIoHandler.java:67) at org.apache.mina.core.filterchain.DefaultIoFilterChain$TailFilter.messageReceived(DefaultIoFilterChain.java:716) at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434) at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46) at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:796) at org.apache.mina.filter.codec.ProtocolCodecFilter$ProtocolDecoderOutputImpl.flush(ProtocolCodecFilter.java:427) at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:245) at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434) at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46) at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:796) at org.apache.mina.core.filterchain.IoFilterAdapter.messageReceived(IoFilterAdapter.java:119) at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434) at org.apache.mina.core.filterchain.DefaultIoFilterChain.fireMessageReceived(DefaultIoFilterChain.java:426) at org.apache.mina.core.polling.AbstractPollingIoProcessor.read(AbstractPollingIoProcessor.java:692) at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:645) at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:634) at org.apache.mina.core.polling.AbstractPollingIoProcessor.access$400(AbstractPollingIoProcessor.java:66) at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java:1078) at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1880) Can fire rules after disposing the Stateful session

by Sravanthi Tipirneni (JIRA)

Can fire rules after disposing the Stateful session --------------------------------------------------- Key: JBRULES-1880 URL: https://jira.jboss.org/jira/browse/JBRULES-1880 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.7 Reporter: Sravanthi Tipirneni Assignee: Mark Proctor Priority: Minor I can access the session and fire rules even after the session is disposed using the dispose method -- 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, 8 months

3
5
0 / 0

[JBoss JIRA] (AS7-3128) Arquillian doesn't wait for the process to really end, causes problems like "port in use".

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/AS7-3128?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen reassigned AS7-3128: ---------------------------------- Assignee: Andrew Rubinger (was: Aslak Knutsen) > Arquillian doesn't wait for the process to really end, causes problems like "port in use". > ------------------------------------------------------------------------------------------ > > Key: AS7-3128 > URL: https://issues.jboss.org/browse/AS7-3128 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.1.0.CR1 > Reporter: Ondrej Zizka > Assignee: Andrew Rubinger > Priority: Blocker > Labels: arq_qe_blocker > > (05:54:09) dmlloyd: when running with JDWP enabled on the client or server, I occasionally get bind exceptions due to address in use > (05:54:25) dmlloyd: which means that tests are running into each other without waiting for termination of the previous one > (05:54:35) dmlloyd: which may also be causing other issues > (05:56:04) ozizka: dmlloyd: Yes, lbarrerio observed similar problem too, > (05:56:47) ozizka: And that's arq's issue too - there's no way to get around this currently AFAIK. Or is there? > (05:57:05) ozizka: Perhaps "manually" wait in @AfterClass or such > (05:57:07) dmlloyd: yeah, it can wait for the child process to terminate > (05:57:07) ozizka: which is ugly > (05:57:14) dmlloyd: I mean arq should > (05:59:17) ozizka: dmlloyd: Do you have it somewhere on hudson? > (05:59:24) ozizka: dmlloyd: It never happened to me actually > (05:59:49) ozizka: Send me a log if you have one handy > (06:01:35) dmlloyd: ozizka: no, try running with this command though: > {code} > mvn -DallTests install -Djpda -Dsurefire.jpda.args=-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n \ > -Dmaven.surefire.debug="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005" > {code} > (06:13:56) ozizka: dmlloyd: That's on linux? > (06:14:03) dmlloyd: yes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-2203) Add Arquillian Container support for AS 7 domain controller

by Rajesh Rajasekaran (JIRA)

[ https://issues.jboss.org/browse/AS7-2203?page=com.atlassian.jira.plugin.s... ] Rajesh Rajasekaran updated AS7-2203: ------------------------------------ Priority: Critical (was: Major) Increasing priority as we have been waiting on this for a while. > Add Arquillian Container support for AS 7 domain controller > ------------------------------------------------------------ > > Key: AS7-2203 > URL: https://issues.jboss.org/browse/AS7-2203 > Project: Application Server 7 > Issue Type: Feature Request > Components: Test Suite > Affects Versions: 7.1.0.CR1 > Reporter: Ondrej Zizka > Assignee: Aslak Knutsen > Priority: Critical > Labels: arq_qe_blocker > > A container for AS 7 domain controller would be very helpful for it's integration testsuite. > Such container should support: > * Attaching hosts to a domain > * Start, stop a domain with multiple hosts > * Configuration (creation) of the domain using domain config file > * Configuration (creation) of a profile using a CLI batch > * Configuration (creation) of a profile using a callback class which would handle communication with Java API > More requirements to come. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-8337) handling of deployment failed at batch resolve time

by Alexey Loubyansky (JIRA)

handling of deployment failed at batch resolve time --------------------------------------------------- Key: JBAS-8337 URL: https://jira.jboss.org/browse/JBAS-8337 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.M1 Types of failures here include: duplicate service definition (i.e. a service was defined that already exists in the container), missing required dependency (i.e. a service was defined that depends on something that isn't there), circular dependency (i.e. two or more service definitions represent circularity in terms of their dependency links). Right now this erases the entire batch, which means that the server cannot start if any of these errors occur. The correct behavior is, in my opinion, to log each error and continue, possibly yielding a report of problem services after the batch is resolved (it is likely, however, that one failure will lead to others). -- 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

12 years, 8 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-8336) handling of deployment failed the validation on the domain controller

by Alexey Loubyansky (JIRA)

handling of deployment failed the validation on the domain controller --------------------------------------------------------------------- Key: JBAS-8336 URL: https://jira.jboss.org/browse/JBAS-8336 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Fix For: 7.0.0.M1 A deployment can fail validation on the domain controller. In this event, the deployment is not added to the domain and an error is thrown from the deployer API, so this does not impact the server. -- 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

12 years, 8 months

4
6
0 / 0

[JBoss JIRA] Created: (AS7-1163) The license of JBoss AS itself is not evident in the distribution

by Dimitris Andreadis (JIRA)

The license of JBoss AS itself is not evident in the distribution ----------------------------------------------------------------- Key: AS7-1163 URL: https://issues.jboss.org/browse/AS7-1163 Project: Application Server 7 Issue Type: Task Components: Build System Affects Versions: 7.0.0.CR1 Reporter: Dimitris Andreadis Assignee: Paul Gier Priority: Critical Fix For: 7.0.0.Final When looking in the distribution, it's not evident what is the license of the application server itself. We have the licenses for the various subsystems in docs/licenses and the docs/licenses/licenses.xml containing entries like <dependency> <groupId>org.jboss.as</groupId> <artifactId>jboss-as-build-config</artifactId> <version>7.0.0.CR1</version> <licenses> <license> <name>lgpl</name> <url>http://repository.jboss.org/licenses/lgpl-2.1.txt</url> </license> </licenses> </dependency> But I think we need something more explicit like we had in previous releases. Maybe a txt file LICENSE.txt either in docs/licenses, or in the top level directory. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012