Bug 1004414 - NoClassDefFoundError: org/drools/marshalling/impl/ProtobufMessages$RuleData
Summary: NoClassDefFoundError: org/drools/marshalling/impl/ProtobufMessages$RuleData
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: jBPM Console
Version: BRMS 5.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: ---
Assignee: Kris Verlaenen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 986451
TreeView+ depends on / blocked
 
Reported: 2013-09-04 15:06 UTC by Zuzana Krejčová
Modified: 2025-02-10 03:28 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:28:28 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
server log excerpt from EAP 6.1 (64.02 KB, text/x-log)
2013-09-04 15:06 UTC, Zuzana Krejčová
no flags Details
server log excerpt from standalone package (40.40 KB, text/x-log)
2013-09-04 15:07 UTC, Zuzana Krejčová
no flags Details
popup after signing in (199.67 KB, image/png)
2013-09-04 15:08 UTC, Zuzana Krejčová
no flags Details
popup after switching to Process overview (228.68 KB, image/png)
2013-09-04 15:09 UTC, Zuzana Krejčová
no flags Details
Exception when serializing a jBPM process instance (5.53 KB, text/plain)
2013-09-12 11:06 UTC, Marek Winkler
no flags Details

Description Zuzana Krejčová 2013-09-04 15:06:47 UTC
Created attachment 793722 [details]
server log excerpt from EAP 6.1

Description of problem:
When opening the business-central app, error popup is shown, exception stack trace appears in the server log.

The main message is:
java.lang.RuntimeException: java.lang.NoClassDefFoundError: org/drools/marshalling/impl/ProtobufMessages$RuleData

Reproduced with standalone package, EAP 5.1.2 and EAP 6.1.


Version-Release number of selected component (if applicable):
Roll up patch BRMS_5.3.1_3_2013

Comment 1 Zuzana Krejčová 2013-09-04 15:07:26 UTC
Created attachment 793724 [details]
server log excerpt from standalone package

Comment 2 Zuzana Krejčová 2013-09-04 15:08:31 UTC
Created attachment 793726 [details]
popup after signing in

Comment 3 Zuzana Krejčová 2013-09-04 15:09:53 UTC
Created attachment 793727 [details]
popup after switching to Process overview

On EAP 6.1, I am able to close the first error popup and switch to Process overview. This happens then.

Comment 4 Marek Winkler 2013-09-04 15:45:57 UTC
The problem is probably caused by using wrong version of protobuf library, see the following exception cause in the log:

Caused by: java.lang.VerifyError: class org.drools.marshalling.impl.ProtobufMessages$RuleData overrides final method getUnknownFields.()Lcom/google/protobuf/UnknownFieldSet

Comment 5 Alessandro Lazarotti 2013-09-04 15:48:23 UTC
Exactly. As mentioned in Bug 1000385 (included for that roll up list) all protobuf jars must be updated to version 2.5.0.

Comment 6 Marek Winkler 2013-09-12 11:04:27 UTC
The protobuf libraries version is now correct, but it seems that protobuf classes have not been regenerated for jBPM engine:

Caused by: java.lang.UnsupportedOperationException: This is supposed to be overridden by subclasses.
     [java] 	at com.google.protobuf.GeneratedMessage.getUnknownFields(GeneratedMessage.java:180) ~[protobuf-java-2.5.0.jar:na]

(see attachement for full stack trace)

It seems the following commit did not make it into the patch: 

https://github.com/droolsjbpm/jbpm/commit/9b08e628d0fb9a45aaebbdc84e5961163aa70203

however, it is in the 5.3.x branch - it should probably be cherry-picked into 5.2.x first.

Comment 7 Marek Winkler 2013-09-12 11:06:35 UTC
Created attachment 796781 [details]
Exception when serializing a jBPM process instance

Comment 8 Kris Verlaenen 2013-09-12 15:00:23 UTC
It seems the files were regenerated incorrectly on the 5.3.x instead of the 5.2.x branch.  The files have been regenerated for 5.2.x now.

http://github.com/droolsjbpm/jbpm/commit/2ae56b254

Comment 14 Red Hat Bugzilla 2025-02-10 03:28:28 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


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