For information.
I implemented a workaround and opened a pull request for this issue:
https://github.com/droolsjbpm/drools/pull/176
The implemented workaround is the lowest impact workaround I could think of:
Preload the stream into memory before unmarshalling, and ProtoBuf will not
enforce the message size limit that causes the exception.
It's implemented as a COMPLETELY OPTIONAL toggle where the default behavior
is the old non preloading implementation. I.e. you only activate the
workaround if you know what you're doing.
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Unmarshall-large-session-fa...
Sent from the Drools: User forum mailing list archive at
Nabble.com.