[
https://issues.jboss.org/browse/DROOLS-1101?page=com.atlassian.jira.plugi...
]
Geoffrey De Smet commented on DROOLS-1101:
------------------------------------------
The drools tests succeed, but there's a JBPM test that fails in drools-osgi in the
integration repo. Hidden in a stacktraces that gets logged and eat, I found this:
{code}
2016-03-21 17:35:57,492 | ERROR | (3)-192.168.1.16 | TransactionSynchronizationUtils | 76
- org.apache.servicemix.bundles.spring-tx - 3.2.9.RELEASE_1 |
TransactionSynchronization.beforeCompletion threw exception
java.lang.NoSuchMethodError:
org.drools.core.marshalling.impl.ProtobufMessages$ProcessData$Builder.setExtension(Lcom/google/protobuf/GeneratedMessage$GeneratedExtension;Ljava/lang/Object;)Lcom/google/protobuf/GeneratedMessage$ExtendableBuilder;
at
org.jbpm.marshalling.impl.ProtobufProcessMarshaller.writeProcessTimers(ProtobufProcessMarshaller.java:90)
at
org.drools.core.marshalling.impl.ProtobufOutputMarshaller.serializeSession(ProtobufOutputMarshaller.java:209)
at
org.drools.core.marshalling.impl.ProtobufOutputMarshaller.writeSession(ProtobufOutputMarshaller.java:120)
at
org.drools.core.marshalling.impl.ProtobufMarshaller.marshall(ProtobufMarshaller.java:164)
at
org.drools.core.marshalling.impl.ProtobufMarshaller.marshall(ProtobufMarshaller.java:148)
at
org.drools.persistence.SessionMarshallingHelper.getSnapshot(SessionMarshallingHelper.java:78)
at org.drools.persistence.info.SessionInfo.transform(SessionInfo.java:96)
at
org.drools.persistence.TriggerUpdateTransactionSynchronization.beforeCompletion(TriggerUpdateTransactionSynchronization.java:57)
at
org.kie.spring.persistence.SpringTransactionSynchronizationAdapter.beforeCompletion(SpringTransactionSynchronizationAdapter.java:54)
at
org.springframework.transaction.support.TransactionSynchronizationUtils.triggerBeforeCompletion(TransactionSynchronizationUtils.java:106)
{code}
Upgrade protobuf-java from 2.5.0 to 2.6.0
-----------------------------------------
Key: DROOLS-1101
URL:
https://issues.jboss.org/browse/DROOLS-1101
Project: Drools
Issue Type: Task
Components: core engine
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
From RPM discussion (BPMSPL-282)
Productization: protobuf-java redhat version is: 2.6.0-redhat-1, is it ok to upgrade
from 2.5.0->2.6.0?
Motivation:
- The 2.5 version isn't build from source by productization, there is no redhat
version.
- The 2.6 version is, which means they can do security patches on it easily (= important
for long term support) and it can be RPM'ed (important for BPMSPL-282, which has PM
support)
- 2.6 is higher than 2.5, so in theory this is low-risk change.
Needed on both master and 6.4.x.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)