July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2794) Running More Than 100 Threads Results in ArrayIndexOutOfBoundsException from Drools AbstractHashTable

by Anatoly Polinsky (JIRA)

Running More Than 100 Threads Results in ArrayIndexOutOfBoundsException from Drools AbstractHashTable ----------------------------------------------------------------------------------------------------- Key: JBRULES-2794 URL: https://jira.jboss.org/browse/JBRULES-2794 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.1.1.FINAL, FUTURE Environment: Ubuntu, Intellij / Windows XP, Eclipse Reporter: Anatoly Polinsky Assignee: Mark Proctor Unfortunately it is not a consistent behaviour, but happens quite often. This is not observed at all when running with e.g. 50 threads. java.util.concurrent.ExecutionException: org.drools.RuntimeDroolsException: Unexpected exception executing action org.drools.reteoo.ReteooWorkingMemory$WorkingMemoryReteAssertAction@1102fab at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) at java.util.concurrent.FutureTask.get(FutureTask.java:83) at com.jpmc.tss.admincenter.framework.workflow.stress.test.WorkflowStressTest.shouldRunFlow(WorkflowStressTest.java:50) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:74) at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:82) at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:72) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:240) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:180) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:94) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:192) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:64) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:115) Caused by: org.drools.RuntimeDroolsException: Unexpected exception executing action org.drools.reteoo.ReteooWorkingMemory$WorkingMemoryReteAssertAction@1102fab at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:1473) at org.drools.common.AbstractWorkingMemory.startProcess(AbstractWorkingMemory.java:1631) at org.drools.impl.StatefulKnowledgeSessionImpl.startProcess(StatefulKnowledgeSessionImpl.java:318) at org.drools.command.runtime.process.StartProcessCommand.execute(StartProcessCommand.java:99) at org.drools.command.runtime.process.StartProcessCommand.execute(StartProcessCommand.java:38) at org.drools.persistence.session.SingleSessionCommandService.execute(SingleSessionCommandService.java:285) at org.drools.command.impl.CommandBasedStatefulKnowledgeSession.startProcess(CommandBasedStatefulKnowledgeSession.java:193) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:191) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:692) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:625) at org.custom.workflow.stress.test.WorkflowRunner.call(WorkflowRunner.java:18) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) 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:662) Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 at org.drools.core.util.AbstractHashTable$HashTableIterator.next(AbstractHashTable.java:317) at org.drools.reteoo.EntryPointNode.updateSink(EntryPointNode.java:323) at org.drools.reteoo.ObjectTypeNode.attach(ObjectTypeNode.java:303) at org.drools.reteoo.builder.PatternBuilder.attachObjectTypeNode(PatternBuilder.java:257) at org.drools.reteoo.ClassObjectTypeConf.<init>(ClassObjectTypeConf.java:92) at org.drools.common.ObjectTypeConfigurationRegistry.getObjectTypeConf(ObjectTypeConfigurationRegistry.java:68) at org.drools.reteoo.Rete.assertObject(Rete.java:111) at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:280) at org.drools.reteoo.ReteooWorkingMemory$WorkingMemoryReteAssertAction.execute(ReteooWorkingMemory.java:360) at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:1471) ... 24 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
9
0 / 0

[JBoss JIRA] Created: (JBAS-7832) VFSDirContext issues

by Remy Maucherat (JIRA)

VFSDirContext issues -------------------- Key: JBAS-7832 URL: https://jira.jboss.org/jira/browse/JBAS-7832 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-6.0.0.M3 Reporter: Remy Maucherat Assignee: Remy Maucherat Following the update to VFS 3, VFSDirContext exhibits weird behavior, although it is partially working. Workaround using a regular FileDirContext. -- 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

13 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8014) Complete Site and Documentation for AS6 EJB

by Stan Silvert (JIRA)

Complete Site and Documentation for AS6 EJB ------------------------------------------- Key: JBAS-8014 URL: https://jira.jboss.org/jira/browse/JBAS-8014 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Stan Silvert -- 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

13 years, 8 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-9024) Consolidated AS 7 Javadocs

by David Lloyd (JIRA)

Consolidated AS 7 Javadocs -------------------------- Key: JBAS-9024 URL: https://issues.jboss.org/browse/JBAS-9024 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: John Casey Fix For: 7.0.0.CR1 Parent issue for tracking tasks required to accomplish a consolidated javadoc bundle for AS 7. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

5
5
0 / 0

[JBoss JIRA] Created: (JBAS-9029) Identify modules with inadequate/missing JavaDoc

by David Lloyd (JIRA)

Identify modules with inadequate/missing JavaDoc ------------------------------------------------ Key: JBAS-9029 URL: https://issues.jboss.org/browse/JBAS-9029 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
9
0 / 0

[JBoss JIRA] Created: (JBAS-8325) graceful shutdown

by Emanuel Muckenhuber (JIRA)

graceful shutdown ----------------- Key: JBAS-8325 URL: https://jira.jboss.org/browse/JBAS-8325 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Emanuel Muckenhuber Fix For: 7.0.0.M1 We need to define a clear contract between these networking services and the services that use them in order to be able to perform a graceful shutdown of remote connectors. -- 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

13 years, 9 months

6
11
0 / 0

[JBoss JIRA] Created: (JBAS-9086) Add Notification support to the domain management API

by Brian Stansberry (JIRA)

Add Notification support to the domain management API ----------------------------------------------------- Key: JBAS-9086 URL: https://issues.jboss.org/browse/JBAS-9086 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.CR1 Management resource should be able to emit notifications; clients can register listeners. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

6
10
0 / 0

[JBoss JIRA] Created: (AS7-1268) Can't update subhandler on async handler

by Stan Silvert (JIRA)

Can't update subhandler on async handler ---------------------------------------- Key: AS7-1268 URL: https://issues.jboss.org/browse/AS7-1268 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.1.0.Alpha1 Reporter: Stan Silvert Assignee: David Lloyd David, sorry if I'm assigning to the wrong person. I guess this could be a CLI bug. [standalone@localhost:9999 /] cd subsystem=logging/async-handler=ASYNC [standalone@localhost:9999 async-handler=ASYNC] :read-resource(recursive=true) { "outcome" => "success", "result" => { "level" => "INFO", "overflow-action" => "BLOCK", "queue-length" => 1024, "subhandlers" => ["FILE"] } } [standalone@localhost:9999 async-handler=ASYNC] :update-properties(subhandlers=["CONSOLE"]) {"outcome" => "success"} [standalone@localhost:9999 async-handler=ASYNC] :read-resource(recursive=true) { "outcome" => "success", "result" => { "level" => "INFO", "overflow-action" => "BLOCK", "queue-length" => 1024, "subhandlers" => ["FILE"] } } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-8201) Patching system

by Brian Stansberry (JIRA)

Patching system --------------- Key: JBAS-8201 URL: https://jira.jboss.org/browse/JBAS-8201 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Fix For: 7.0.0.M2 "Server" side of the patching system. Server not in the sense of the domain model Server, but rather client-server where the client is whatever tool (JON) determines there are patches available and asks the server to apply them. This does not need to implemented until M2 but thinking about it during the design of the InstalledImage is good. -- 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

13 years, 9 months

6
9
0 / 0

[JBoss JIRA] Created: (AS7-887) Support legacy ServiceMBeans in SAR deployments

by Matt Drees (JIRA)

Support legacy ServiceMBeans in SAR deployments ----------------------------------------------- Key: AS7-887 URL: https://issues.jboss.org/browse/AS7-887 Project: Application Server 7 Issue Type: Enhancement Reporter: Matt Drees It looks like the current SAR deployment code (jboss-as-sar) will deploy simple MBeans just fine. However, users may expect to be able to deploy older ServiceMBeans from previous Jboss AS versions. Currently, attempting to do this results in a ClassNotFoundException, since the org.jboss.system.ServiceMBean interface doesn't exist anymore. Ideally this would also involve supporting ServiceMBeans that extend org.jboss.system.ServiceMBeanSupport, which also doesn't exist anymore. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

7
13
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