It seems that this is some kind of security mechanism in googles' protobuf
(the serialization framework Drools is using).
From protobuf's documentation:
CodeInputStream.setSizeLimit():
"Set the maximum message size. In order to prevent malicious messages from
exhausting memory or causing integer overflows, CodedInputStream limits how
large a message may be. The default limit is 64MB. You should set this
limit as small as you can without harming your app's functionality. Note
that size limits only apply when reading from an InputStream, not when
constructed around a raw byte array (nor with
ByteString.newCodedInput()<https://developers.google.com/protocol-buff...
)."
It appears to me that Drools needs to expose this configuration to end
users in some way (not sure if it is already exposed), or use a ridiculous
large predefined size.
Best Regards,
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Esteban Aliverti
- Blog @
http://ilesteban.wordpress.com
On Mon, Jul 23, 2012 at 3:06 PM, chrisLi <shengtao0077(a)163.com> wrote:
Hi Laune,
Thank you very much for your quick response.
I did not understand your response very clearly. Could you explain it
in
more detail.
Thank you!
--
View this message in context:
http://drools.46999.n3.nabble.com/com-google-protobuf-InvalidProtocolBuff...
Sent from the Drools: User forum mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users