[Coco] Houston, we have a problem...

[William Astle]

The Java DW4 server does quite a few things that are questionable and 
generally not particularly portable. For instance, it relies on a native 
code library for serial I/O. It also seems to exercise pretty much the 
entire JVM in one way or another.

Interestingly, the version prior to the major GUI change was very 
stable. But after the GUI change, it was only ever really stable on 
Windows. I can't remember which version number introduced the current 
GUI and it's not certain that that older version would be any more 
functional on current systems.

On 2019-06-06 12:07 p.m., Gene Heskett wrote:
> On Thursday 06 June 2019 09:29:34 am Rich Carreiro wrote:
> 
>> Out of curiosity, what is it about newer JVMs that breaks DW?
>>
> Quite a lengthy and many times repeated list of java errors, and when it
> does settle down to looking almost normal guiwise, its still not talking
> to the coco.
> java.net.SocketException: Address already in use (Listen failed)
>          at java.net.PlainSocketImpl.socketListen(Native Method)
>          at
> java.net.AbstractPlainSocketImpl.listen(AbstractPlainSocketImpl.java:399)
>          at java.net.ServerSocket.bind(ServerSocket.java:376)
>          at java.net.ServerSocket.<init>(ServerSocket.java:237)
>          at java.net.ServerSocket.<init>(ServerSocket.java:128)
>          at
> com.groupunix.drivewireui.nineserver.NineServer.run(NineServer.java:25)
>          at java.lang.Thread.run(Thread.java:748)
> 
> (DriveWire:5987): libsoup-CRITICAL **: soup_session_feature_detach:
> assertion 'SOUP_IS_SESSION_FEATURE (feature)' failed
> 
> (DriveWire:5987): libsoup-CRITICAL **: soup_session_feature_attach:
> assertion 'SOUP_IS_SESSION_FEATURE (feature)' failed
> 
> (DriveWire:5987): GLib-GObject-CRITICAL **:
> g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers <
> CLOSURE_MAX_N_INOTIFIERS' failed
> 
> (DriveWire:5987): GLib-GObject-CRITICAL **:
> g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers <
> CLOSURE_MAX_N_INOTIFIERS' failed
> 
> And it goes on for at least another 20k, changing the message
> occasionally.
> 
> 
> 
>