VBC ack problem

During user testing, at least one case of VirtualByteChannel ack problems has been encountered. The following is a log of the problem:

13:37:49.980 WARN  c.s.i.VirtualByteChannel - Channel 2 will be closed because a data ack from the peer referenced message 20009, which is unknown.
13:37:49.981 WARN  c.s.i.VirtualByteChannel - Channel 2 will be closed because a data ack from the peer referenced message 20009, which is unknown.
13:37:49.981 WARN  c.s.i.VirtualByteChannel - Channel 2 will be closed because a data ack from the peer referenced message 20009, which is unknown.
13:37:49.981 WARN  c.s.i.VirtualByteChannel - Channel 2 will be closed because a data ack from the peer referenced message 20009, which is unknown.
13:37:49.982 WARN  c.s.i.VirtualByteChannel - Channel 2 will be closed because a data ack from the peer referenced message 20009, which is unknown.
13:37:49.985 WARN  c.t.t.a.u.ManagedFileSupport - Error writing image mod
java.nio.channels.ClosedChannelException: null
    at com.starlight.intrepid.VirtualByteChannel.write(VirtualByteChannel.java:285)
    at com.logicartisan.common.core.IOKit.copy(IOKit.java:287)
    at <package/class redacted>.lambda$null$1(<class redacted>.java:9999)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

Comments (1)