Looks like the fix was ByteArray.shareable = true, on all messages being sent over the channel. I hadn't thought that was necessary, as I was expecting a copy of the ByteArray would happen. And 99% of the time, it did. Just randomly wouldn't send it.. which is weird, but anyways, shareable = true solved my issue and it's running stable now.
Thanks -Sean Thayne On Tue, Apr 8, 2014 at 2:04 PM, Gary Yang <[email protected]> wrote: > Please do tell us when you found the root cause, thanks. > > > On Tue, Apr 8, 2014 at 3:54 PM, Sean Thayne <[email protected]> wrote: > > > Ya, I've tried that, the thing is that the ByteArray.length is zero. > > > > -Sean Thayne > > > > > > On Tue, Apr 8, 2014 at 1:38 PM, Gary Yang <[email protected]> > wrote: > > > > > bytesarray.position = 0 before read again? > > > > > > > > > On Tue, Apr 8, 2014 at 3:35 PM, Sean Thayne <[email protected]> wrote: > > > > > > > Hi, > > > > > > > > Has anybody ran into end of file errors when using the MessageChannel > > > > classes with workers? > > > > > > > > Sometimes (randomly) the message that are sent over the > MessageChannel > > > are > > > > empty. Which causes Error #2030 Unexpected End of File. > > > > > > > > > > > > -Sean Thayne > > > > > > > > > >
