blankensteiner commented on issue #228:
URL: 
https://github.com/apache/pulsar-dotpulsar/issues/228#issuecomment-2228029703

   Hi @htbmw 
   We have never seen this issue before but would like to help.
   As stated in the StackOverflow post, using 'PrepareSerializer' might bring 
about another issue.
   This seems to be an old 
[issue](https://github.com/protobuf-net/protobuf-net/issues/218) so I guess no 
solution is coming from protobuf-net.
   We could protect the 'ProtoBuf.Serializer.Serialize' call with a lock, but I 
think that will hurt performance.
   If you can, could you create your own DotPulsar.dll after adding:
   `static Serializer() => Serialize(new BaseCommand());`
   to 'DotPulsar.Internal.Serializer'? I hope this call will force protobuf-net 
to create stuff needed for serializing the base command so that we don't see 
this issue. It's a long shot, but worth a try.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to