March 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1060) Unexpected exit with no stack trace or other information

by christopher barham (JIRA)

Unexpected exit with no stack trace or other information -------------------------------------------------------- Key: JBRULES-1060 URL: http://jira.jboss.com/jira/browse/JBRULES-1060 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.GA Environment: Windows XP sp2, 1GB RAM, Sun Java JDK 1.5.0_11, Eclipse 3.3 Build id: I20070621-1340, JBOSS Rules feature/plugin 4.0.0 Reporter: christopher barham Assigned To: Mark Proctor When inserting a number of facts, (seems to be somewhere around 450 facts in this test example here), the rules system exits unexpectedly with no stack trace or other information. I pared down my code to a simple example that demonstrates this below. I can get it to run normally if I insert 450 facts, however 475 or above exhibits this unexpected system exit. I am running this from Eclipse. Garbage.java (fact bean): package com.sample; public class Garbage { private char id; private int someNumber; public Garbage(char garbageId, int someNumber) { setSomeNumber(someNumber); setId(garbageId); } public char getId() { return id; } public int getSomeNumber() { return someNumber; } public void setId(char id) { this.id = id; } public void setSomeNumber(int someNumber) { this.someNumber = someNumber; } @Override public String toString() { StringBuilder sb = new StringBuilder(); sb.append("a Garbage { "); sb.append("someNumber= "); sb.append(getSomeNumber()); sb.append(", id= "); sb.append(getId()); sb.append(" }"); return sb.toString(); } } StrangeExit.Java (Rule Engine startup and fact insertion): package com.sample; import java.io.InputStreamReader; import java.io.Reader; import org.drools.RuleBase; import org.drools.RuleBaseFactory; import org.drools.WorkingMemory; import org.drools.compiler.PackageBuilder; import org.drools.event.DebugWorkingMemoryEventListener; import org.drools.rule.Package; public class StrangeExit { public static final void main(String[] args) { try { long startTime = System.currentTimeMillis(); System.out.println("Starting problem at " + new java.util.Date()); RuleBase ruleBase = readRule(); WorkingMemory workingMemory = ruleBase.newStatefulSession(); workingMemory.addEventListener(new DebugWorkingMemoryEventListener()); assertAllFacts(workingMemory); workingMemory.fireAllRules(); long stopTime = System.currentTimeMillis(); long runTime = stopTime - startTime; System.out.println("Run time (milliseconds): " + runTime); System.out.println("Finished problem at " + new java.util.Date()); } catch (Throwable t) { t.printStackTrace(); } } private static void assertAllFacts(WorkingMemory workingMemory) { for (int i = 1; i <= 3; i++) { for (int j = 1; j <= 475; j++) { Garbage gar = new Garbage((char)(i + 64), j); workingMemory.insert(gar); } } } private static RuleBase readRule() throws Exception { Reader source = new InputStreamReader(StrangeExit.class.getResourceAsStream("/strange.drl")); PackageBuilder builder = new PackageBuilder(); builder.addPackageFromDrl(source); Package pkg = builder.getPackage(); RuleBase ruleBase = RuleBaseFactory.newRuleBase(); ruleBase.addPackage(pkg); return ruleBase; } } The Rule itself: package com.sample import com.sample.Garbage; rule "Weird exit with no stack trace error" when $garA : Garbage( ) $garB : Garbage( id == 'B' , someNumber >= $garA.someNumber ) then System.out.println("Something is up"); end -- 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

18 years, 2 months

4
10
0 / 0

[JBoss JIRA] Created: (JBRULES-1439) Property Name inconsistent on RHS

by greywind (JIRA)

Property Name inconsistent on RHS --------------------------------- Key: JBRULES-1439 URL: http://jira.jboss.com/jira/browse/JBRULES-1439 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.4 Reporter: greywind Priority: Minor I apologize right from the start if this is a know thing, but I couldn't find it in the Documentation or the mailing Lists: public class Settlement { public String InstrumentType,InstrumentName; public String getInstrumentType() { return InstrumentType; } public void setInstrumentType(String instrumentType) { InstrumentType = instrumentType; } public String getInstrumentName() { return InstrumentName; } public void setInstrumentName(String instrumentName) { InstrumentName = instrumentName; } } The following Role leads to an error during compilation as the Property instrumentName can not be found on the RHS. in the LHS it is found: rule "TestEntity" //dialect "mvel" when $s : Settlement(instrumentType == "BOND", name : instrumentName) #conditions then System.out.println("Found: " + $s.instrumentName); end It seems that in the java dialect the LHS follows java bean notation (property start with lower case) on the RHS not. I have to specify the property with UpperCamelCase on RHS to make it work: rule "TestEntity" //dialect "mvel" when $s : Settlement(instrumentType == "BOND", name : instrumentName) #conditions then System.out.println("Found: " + $s.InstrumentName); end the MVEL dialect on the other hand handles this as expected. the property is LowerCamelCase on both sides: rule "TestEntity" dialect "mvel" when $s : Settlement(instrumentType == "BOND", name : instrumentName) #conditions then System.out.println("Found: " + $s.instrumentName); end I would expect that the java dialect should work the same way here, should it not? -- 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

18 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-5226) ClientUserTransaction should be configured with Unified invoker

by Galder Zamarreno (JIRA)

ClientUserTransaction should be configured with Unified invoker --------------------------------------------------------------- Key: JBAS-5226 URL: http://jira.jboss.com/jira/browse/JBAS-5226 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.2.GA Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Priority: Minor Even though unified invokers are default for EJBs, jboss:service=ClientUserTransaction service is still using JRMP invokers by default. ClientUserTransaction service definition should be changed to used unified invokers as below:  <mbean code="org.jboss.tm.usertx.server.ClientUserTransactionService" name="jboss:service=ClientUserTransaction" xmbean-dd="resource:xmdesc/ClientUserTransaction-xmbean.xml"> <depends> <mbean code="org.jboss.invocation.jrmp.server.JRMPProxyFactory" name="jboss:service=proxyFactory,target=ClientUserTransactionFactory">  <attribute name="InvokerName">jboss:service=invoker,type=unified</attribute> <attribute name="TargetName">jboss:service=ClientUserTransaction</attribute> <attribute name="JndiName">UserTransactionSessionFactory</attribute> <attribute name="ExportedInterface">org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory</attribute> <attribute name="ClientInterceptors"> <interceptors> <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor> <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor> </interceptors> </attribute>  <depends>jboss:service=invoker,type=unified</depends> </mbean> </depends> <depends optional-attribute-name="TxProxyName"> <mbean code="org.jboss.invocation.jrmp.server.JRMPProxyFactory" name="jboss:service=proxyFactory,target=ClientUserTransaction">  <attribute name="InvokerName">jboss:service=invoker,type=unified</attribute> <attribute name="TargetName">jboss:service=ClientUserTransaction</attribute> <attribute name="JndiName"></attribute> <attribute name="ExportedInterface">org.jboss.tm.usertx.interfaces.UserTransactionSession</attribute> <attribute name="ClientInterceptors"> <interceptors> <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor> <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor> </interceptors> </attribute>  <depends>jboss:service=invoker,type=unified</depends> </mbean> </depends> </mbean> Bear in mind that even though ClientUserTransactionService uses JRMPProxyFactory, this is just a wrapper and you can set any type of invokers with it. You can indeed set the unified invoker as InvokerName. -- 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

18 years, 2 months

1
5
0 / 0

[JBoss JIRA] Created: (JGRP-713) UNICAST: eager acks

by Bela Ban (JIRA)

UNICAST: eager acks ------------------- Key: JGRP-713 URL: http://jira.jboss.com/jira/browse/JGRP-713 Project: JGroups Issue Type: Feature Request Affects Versions: 2.6.1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6.3, 2.7 [Gray Watson] The http://www.nabble.com/file/p15994217/UNICAST.java.patch patch to UNICAST.java adds an "immediate_ack" boolean to the UNICAST protocol which causes it to return the ACK to the client _before_ processing it. UNICAST, by design, only allows one packet up the stack per sender at any time. We had some flow control issues earlier and this was one of the mechanisms we used to alleviate the retransmit cycles where packets would be retransmitted 4-5 times even though many had already been received by the received -- just not ACK'd. -- 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

18 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAOP-529) Document maven plugin and add pom.xml for most of the examples in the dist

by Stale Pedersen (JIRA)

Document maven plugin and add pom.xml for most of the examples in the dist -------------------------------------------------------------------------- Key: JBAOP-529 URL: http://jira.jboss.com/jira/browse/JBAOP-529 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Stale Pedersen Assigned To: Stale Pedersen Fix For: 2.0.0.GA -- 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

18 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAOP-517) Enable Advisor.methodInterceptors field

by Flavia Rainone (JIRA)

Enable Advisor.methodInterceptors field --------------------------------------- Key: JBAOP-517 URL: http://jira.jboss.com/jira/browse/JBAOP-517 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR3 Reporter: Flavia Rainone Assigned To: Flavia Rainone Fix For: 2.0.0.GA During JBAOP-487 implementation, this field has been disabled. It needs to be enabled again, since this broke compatiblity with JBoss 4.0.x EJB3. This task includes also adding tests for that. -- 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

18 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1214) Pointcut expression which applies to sub-classes is not applied to super-methods

by Carlo de Wolf (JIRA)

Pointcut expression which applies to sub-classes is not applied to super-methods -------------------------------------------------------------------------------- Key: EJBTHREE-1214 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1214 Project: EJB 3.0 Issue Type: Bug Components: interceptors Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: AS 5.0.0.CR1 The AroundInvokeBean implements SessionSynchronization, so all methods should contain the SessionSynchronizationInterceptor as per: <bind pointcut="execution(public * $instanceof{javax.ejb.SessionSynchronization}->*(..))"> <interceptor-ref name="org.jboss.ejb3.stateful.SessionSynchronizationInterceptor"/> </bind> But methods defined on the super class AroundInvokeBase do not contain this interceptor in the chain. Test is in interceptors/supermethod -- 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

18 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-708) persistence factory spits out error messages when it should be debug

by Gray Watson (JIRA)

persistence factory spits out error messages when it should be debug -------------------------------------------------------------------- Key: JGRP-708 URL: http://jira.jboss.com/jira/browse/JGRP-708 Project: JGroups Issue Type: Task Affects Versions: 2.6.1 Reporter: Gray Watson Assigned To: Bela Ban Priority: Minor PersistanceFactory.java spits out error messages in a debug situation. -- 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

18 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-707) stats logic NPE in NAKACK

by Gray Watson (JIRA)

stats logic NPE in NAKACK ------------------------- Key: JGRP-707 URL: http://jira.jboss.com/jira/browse/JGRP-707 Project: JGroups Issue Type: Bug Affects Versions: 2.6.1 Reporter: Gray Watson Assigned To: Bela Ban Priority: Minor In the code for NAKACK, the first packet which is recorded as part of the stats for an address throws NPE. StatsEntry entry=map.get(key); if(entry == null) { entry = new StatsEntry(); entry = map.putIfAbsent(key, entry); // ^^^^ this can return null if key does not exist } entry.xmit_reqs+=req; -- 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

18 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-710) VIEW_SYNC needs more statistics

by Gray Watson (JIRA)

VIEW_SYNC needs more statistics ------------------------------- Key: JGRP-710 URL: http://jira.jboss.com/jira/browse/JGRP-710 Project: JGroups Issue Type: Feature Request Affects Versions: 2.6.1 Reporter: Gray Watson Assigned To: Bela Ban Priority: Minor Attachments: VIEW_SYNC.java.patches In trying to debug some VIEW_SYNC issues, we found the following extra statistics very helpful. Please consider rolling them in. -- 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

18 years, 2 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 March 2008