Bug 1044581 - Intermittent ArrayIndexOutOfBoundsException under high load in drools
Summary: Intermittent ArrayIndexOutOfBoundsException under high load in drools
Status: NEW
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBoss Rules
Version: 5.3.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
Depends On: 1044577 1054313
TreeView+ depends on / blocked
Reported: 2013-12-18 15:34 UTC by Anton Giertli
Modified: 2020-04-27 01:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1044577
Last Closed:
Type: Bug

Attachments (Terms of Use)
reproducer (822.17 KB, application/zip)
2013-12-18 15:34 UTC, Anton Giertli
no flags Details

Description Anton Giertli 2013-12-18 15:34:49 UTC
Created attachment 838410 [details]

+++ This bug was initially created as a clone of Bug #1044577 +++

Description of problem:
A customer is running CEP with a JPA persisted ksession (created by JPAKnowledgeService.newStatefulKnowledgeSession()) on SOA-P. They are seeing the Exception below intermittently under high-load.

Version-Release number of selected component (if applicable):

How reproducible:
See the attachment

Steps to Reproduce:
- Create one ksession by JPAKnowledgeService.newStatefulKnowledgeSession()
- Insert events to a shared EntryPoint from multiple threads
Run CEPTest
Actual results:
Caused by: java.lang.ArrayIndexOutOfBoundsException: 4
        at org.drools.marshalling.impl.ProtobufOutputMarshaller.orderFacts(ProtobufOutputMarshaller.java:592)
        at org.drools.marshalling.impl.ProtobufOutputMarshaller.writeFactHandles(ProtobufOutputMarshaller.java:533)
        at org.drools.marshalling.impl.ProtobufOutputMarshaller.serializeSession(ProtobufOutputMarshaller.java:139)
        at org.drools.marshalling.impl.ProtobufOutputMarshaller.writeSession(ProtobufOutputMarshaller.java:100)

Expected results:

Additional info:

Comment 1 Rick Wagner 2013-12-18 16:21:39 UTC
This BZ has been added to the inclusion list for the next SOA-P 5.3.1 Roll up, tracked at [1].

If the underlying BRMS issue is still open at the time the Roll up is productised, we will move it to the next.


[1] https://mojo.redhat.com/docs/DOC-87990

Note You need to log in before you can comment on or make changes to this bug.