July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-3146) timer rule cannot work fine, if the method 'ksession.fireAllRules()' is called before we reload KnowlegeSession.

by winton xu (JIRA)

timer rule cannot work fine, if the method 'ksession.fireAllRules()' is called before we reload KnowlegeSession. ---------------------------------------------------------------------------------------------------------------- Key: JBRULES-3146 URL: https://issues.jboss.org/browse/JBRULES-3146 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.2.0.Final Reporter: winton xu Assignee: Mark Proctor Priority: Critical we can reproduce it by following steps. 1. create a knowledge session. and call the method 'fireAllRules()' 2. reload knowledge session. 3. crate and build a timer rule. 4. fire the timer rule. [Actual Result] the timer rule cannot work fine. [Expected Result] the timer rule can work fine. (please check the attachement 'TimerAndCalendarTest.java.txt') -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-8938) Separate $JAVA_OPTS for ProcessController and HostController

by Brian Stansberry (JIRA)

Separate $JAVA_OPTS for ProcessController and HostController ------------------------------------------------------------ Key: JBAS-8938 URL: https://issues.jboss.org/browse/JBAS-8938 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry The way domain.sh and domain.conf work now, whatever value gets assigned to $JAVA_OPTS gets passed to java, so affects the vm used for the ProcessController, and then gets passed through as a param to the PC which uses it for creating the HostController process. We should have a separate variable for the PC, or perhaps use $JAVA_OPTS for neither and have 2 new variables. Settings for the PC are unlikely to be optimum for the HC, and using the same var makes it harder to set of debugging (e.g. both the PC and HC process will try and use the same port for remote socket debugging.) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1778) Drools builder raises errors for non-decision tables XLS files

by Edson Tirelli (JIRA)

Drools builder raises errors for non-decision tables XLS files -------------------------------------------------------------- Key: JBRULES-1778 URL: https://jira.jboss.org/jira/browse/JBRULES-1778 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.M1 Reporter: Edson Tirelli Assignee: Kris Verlaenen Fix For: FUTURE As it is now, the eclipse "drools builder" is raising errors for any XLS file that is not a decision table. For instance, in drools-examples there is the ExampleCheese.xls file used for a drools-template example that acuses the following error: No RuleTable's were found in spreadsheet. ExampleCheese.xls drools-examples/src/main/rules/org/drools/examples Unknown Drools Error -- 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, 7 months

4
3
0 / 0

[JBoss JIRA] Created: (AS7-1428) Throw an error when a driver is not loaded due to wrong driver-classname

by Stefano Maestri (JIRA)

Throw an error when a driver is not loaded due to wrong driver-classname ------------------------------------------------------------------------- Key: AS7-1428 URL: https://issues.jboss.org/browse/AS7-1428 Project: Application Server 7 Issue Type: Task Components: JCA Reporter: Stefano Maestri Assignee: Jeff Zhang Fix For: 7.1.0.Alpha1 See forum post -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2256) ExtendedEntityManager injected into Stateless Session Bean

by gunter zeilinger (JIRA)

ExtendedEntityManager injected into Stateless Session Bean ---------------------------------------------------------- Key: EJBTHREE-2256 URL: https://issues.jboss.org/browse/EJBTHREE-2256 Project: EJB 3.0 Issue Type: Bug Components: injection Environment: Running Arquillian 1.0.0.Alpha5 JUnit testcase with jbossas-remote-6 in jboss-6.0.0.Final Reporter: gunter zeilinger Injecting a Stateless and a Stateful Session Bean - the later with an Extended Presentation Context - into a managed object: {code} @RunWith(Arquillian.class) public class MyTest { @EJB private MySFSB sfsb; @EJB private MySLSB slsb; : {code} may cause that the {{ExtendedEntityManager}} from the SFSB get also injected into the SLSB, which results in: {noformat} java.lang.NullPointerException at org.jboss.ejb3.entity.ExtendedEntityManager.getPersistenceContext(ExtendedEntityManager.java:76) at org.jboss.ejb3.entity.ExtendedEntityManager.getEntityManager(ExtendedEntityManager.java:61) at org.jboss.ejb3.jpa.integration.JPA2EntityManagerDelegator.createNamedQuery(JPA2EntityManagerDelegator.java:44) at MySLSB.foo(MySLSB.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) at org.jboss.ejb3.interceptors.container.ContainerMethodInvocationWrapper.invokeNext(ContainerMethodInvocationWrapper.java:72) at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:76) at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:62) ... {noformat} The failure does not occur on each run - sometimes the SLSB get its own {{org.jboss.jpa.tx.TransactionScopedEntityManager}} injected as expected, and the test passes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (LOGTOOL-6) Remove file sorting before processing translation file

by Kevin Pollet (JIRA)

Remove file sorting before processing translation file ------------------------------------------------------ Key: LOGTOOL-6 URL: https://issues.jboss.org/browse/LOGTOOL-6 Project: Log Tool Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta1 Reporter: Kevin Pollet Assignee: David Lloyd Fix For: 1.0.0.Beta2 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JGRP-1271) MuxMessageDispatcher mutates RequestOptions leading ultimately to potential StackOverflowError

by Eric Sirianni (JIRA)

MuxMessageDispatcher mutates RequestOptions leading ultimately to potential StackOverflowError ---------------------------------------------------------------------------------------------- Key: JGRP-1271 URL: https://issues.jboss.org/browse/JGRP-1271 Project: JGroups Issue Type: Bug Affects Versions: 2.11 Environment: All Reporter: Eric Sirianni Assignee: Bela Ban The presence of 'public static final' RequestOptions SYNC and ASYNC implies strongly that RequestOptions are immutable. Otherwise, clients could be changing the meaning of these shared constants. However, MuxMessageDispatcher.cast() mutates the passed-in RequestOptions to set the RspFilter. It chains the existing RspFilter in the RequestOptions to a new one: options.setRspFilter((filter != null) ? new NoMuxHandlerRspFilter(filter) : new NoMuxHandlerRspFilter()) The result of this is that the following innocent looking code code will quickly lead to a stack overflow as the RspFilter chain in the RequestOptions.ASYNC object grows without bound: while (true) { muxMessageDispatcher.cast(dests, msg, RequestOptions.ASYNC, false); } The workaround is to create a new RequestOptions object per call to cast() : while (true) { muxMessageDispatcher.cast(dests, msg, new RequestOptions(...), false); } I recommend either: A. Deprecating the public static final RequestOptions ASYNC and SYNC fields and heavily JavaDoc'ing that clients must use a fresh RequestOptions for each send() or cast() invocation. -or- B. JavaDoc'ing the RequestOptions class as *immutable* and fixing MuxMessageDispatcher and other such JGroups blocks that mutate RequestOptions. You may wish to add a "copy constructor" to RequestOptions to facilitate this. The fix for MuxMessageDispatcher is fairly easy - just "clone" the passed-in RequestOptions and set the NoMuxHandlerRspFilter on the new RequestOptions object: < return super.cast(dests, msg, options.setRspFilter((filter != null) ? new NoMuxHandlerRspFilter(filter) : new NoMuxHandlerRspFilter()), blockForResults); --- > RequestOptions newOptions = new RequestOptions(options.getMode(), options.getTimeout(), options.getAnycasting(), options, (filter != null) ? new NoMuxHandlerRspFilter(filter) : new NoMuxHandlerRspFilter(), options.getFlags()); > return super.cast(dests, msg, newOptions), blockForResults); -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBRULES-2284) OutOfMemoryException at DT loading

by Sergey Vanskov (JIRA)

OutOfMemoryException at DT loading ---------------------------------- Key: JBRULES-2284 URL: https://jira.jboss.org/jira/browse/JBRULES-2284 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-decisiontables Affects Versions: 5.0.1.FINAL Environment: Core2Quad Windows XP Pro 64 Reporter: Sergey Vanskov Assignee: Mark Proctor I have created DT having 20.000 rows with 4 conditions and 1 action in CSV format and set the following parameters for JVM -Xmx3072M -XX:MaxPermSize=256M. I haveOutOfMemoryException with the following stack trace java.lang.OutOfMemoryError: Java heap space at java.lang.String.format(String.java:2558) at org.drools.lang.DroolsParserExceptionFactory.formatParserLocation(DroolsParserExceptionFactory.java:203) at org.drools.lang.DroolsParserExceptionFactory.createErrorMessage(DroolsParserExceptionFactory.java:104) at org.drools.lang.DroolsParserExceptionFactory.createDroolsException(DroolsParserExceptionFactory.java:89) at org.drools.lang.DRLParser.reportError(DRLParser.java:350) at org.antlr.runtime.BaseRecognizer.recoverFromMismatchedToken(BaseRecognizer.java:624) at org.antlr.runtime.BaseRecognizer.match(BaseRecognizer.java:115) at org.drools.lang.DRLParser.fact(DRLParser.java:9841) at org.drools.lang.DRLParser.lhs_pattern(DRLParser.java:9388) at org.drools.lang.DRLParser.pattern_source(DRLParser.java:7432) at org.drools.lang.DRLParser.lhs_unary(DRLParser.java:6582) at org.drools.lang.DRLParser.lhs_and(DRLParser.java:6229) at org.drools.lang.DRLParser.lhs_or(DRLParser.java:5877) at org.drools.lang.DRLParser.lhs(DRLParser.java:5673) at org.drools.lang.DRLParser.normal_lhs_block(DRLParser.java:5580) at org.drools.lang.DRLParser.when_part(DRLParser.java:3975) at org.drools.lang.DRLParser.rule(DRLParser.java:3769) at org.drools.lang.DRLParser.statement(DRLParser.java:993) at org.drools.lang.DRLParser.compilation_unit(DRLParser.java:484) at org.drools.compiler.DrlParser.compile(DrlParser.java:238) at org.drools.compiler.DrlParser.parse(DrlParser.java:78) at org.drools.compiler.DrlParser.parse(DrlParser.java:83) at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:275) at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:510) at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:31) .... Is 3Gb not enough for such a problem?! How may memory requirements be estimated? -- 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, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-9205) Clicking on a subsytem in web console shows a "Could not reveal xxx" message

by jaikiran pai (JIRA)

Clicking on a subsytem in web console shows a "Could not reveal xxx" message ---------------------------------------------------------------------------- Key: JBAS-9205 URL: https://issues.jboss.org/browse/JBAS-9205 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Console Environment: JBoss AS7 upstream (March 31 2011) Reporter: jaikiran pai Assignee: Heiko Braun Attachments: ejb3-subsystem.png Logging into AS7 web console and clicking on any of the subsystems under the "Subsystem" tree shows a error message like: "Could not reveal: server/ejb3". The server has been started in standalone mode. OS: Ubuntu 10.10 Browser : Firefox 3.6.3 JDK: Sun Java 1.6.0_21 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (AS7-1139) Can't use jboss-admin.sh to add configuration to a subsystem

by Darrin Mison (JIRA)

Can't use jboss-admin.sh to add configuration to a subsystem ------------------------------------------------------------ Key: AS7-1139 URL: https://issues.jboss.org/browse/AS7-1139 Project: Application Server 7 Issue Type: Bug Components: CLI Reporter: Darrin Mison Trying to use the jboss-admin.sh to update configuration on standalone AS7 and think I'm missing either some documentation or I didn't understand it. For this particular example I was trying to disable sub-deployment module isolation as described https://docs.jboss.org/author/display/AS7/Class+Loading+in+AS7 but by using the admin CLI instead of hand editing XML. I can "cd" to the /subsystem=ee node fine. I just don't know how to add new configuration. I'm assuming this is possible in the API but not yet exposed in the tool? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
3
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 July 2011