Remote server is down. OCSSW is not accessible. Please start remote server.

[vimal459]

Dear sir,
I have installed seadas 7.5.3 in Windows 10 and configured ocssw in WSL 2-ubuntu16.04 as a Client server system and configuration done as follows

Seadas.config:
seadas.ocssw.root = ${seadas.home}/ocssw
seadas.ocssw.location = virtualMachine
seadas.ocssw.port=6400
seadas.ocssw.sharedDir=C:\Users\${user.name}\seadasClientServerShared
seadas.client.id=${user.name}
seadas.ocssw.keepFilesOnServer=false
seadas.ocssw.processInputStreamPort=6402
seadas.ocssw.processErrorStreamPort=6403

ocsswserver.config:

ocsswrest.version=1.0
baseUriPortNumber=6400
ocsswroot=${user.home}/ocssw
serverWorkingDirectory=/mnt/c/Users/${user.home}/seadasClientServerShared
clientServerSharedDir=true
keepIntermediateFilesOnServer=false
processInputStreamPortNumber=6402
processErrorStreamPortNumber=6403

When i start server i got message as :
argument: ocsswserver.config
-- listing properties --
processErrorStreamPortNumber=6403
java.runtime.name=Java(TM) SE Runtime Environment
sun.boot.library.path=/home/anitha/java/jdk1.8.0_271/jre/li...
java.vm.version=25.271-b09
java.vm.vendor=Oracle Corporation
java.vendor.url=http://java.oracle.com/
path.separator=:
java.vm.name=Java HotSpot(TM) 64-Bit Server VM
file.encoding.pkg=sun.io
user.country=US
sun.java.launcher=SUN_STANDARD
sun.os.patch.level=unknown
java.vm.specification.name=Java Virtual Machine Specification
user.dir=/home
java.runtime.version=1.8.0_271-b09
java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
java.endorsed.dirs=/home/anitha/java/jdk1.8.0_271/jre/li...
os.arch=amd64
java.io.tmpdir=/tmp
line.separator=

java.vm.specification.vendor=Oracle Corporation
os.name=Linux
sun.jnu.encoding=UTF-8
java.library.path=/usr/java/packages/lib/amd64:/usr/lib...
java.specification.name=Java Platform API Specification
java.class.version=52.0
sun.management.compiler=HotSpot 64-Bit Tiered Compilers
os.version=4.19.128-microsoft-standard
user.home=/root
user.timezone=
ocsswrest.version=1.0
java.awt.printerjob=sun.print.PSPrinterJob
file.encoding=UTF-8
java.specification.version=1.8
ocsswroot=/root/ocssw
user.name=root
java.class.path=seadas-ocsswserver.jar
keepIntermediateFilesOnServer=false
java.vm.specification.version=1.8
processInputStreamPortNumber=6402
sun.arch.data.model=64
java.home=/home/anitha/java/jdk1.8.0_271/jre
sun.java.command=seadas-ocsswserver.jar ocsswserver.co...
java.specification.vendor=Oracle Corporation
user.language=en
awt.toolkit=sun.awt.X11.XToolkit
java.vm.info=mixed mode
java.version=1.8.0_271
java.ext.dirs=/home/anitha/java/jdk1.8.0_271/jre/li...
clientServerSharedDir=true
sun.boot.class.path=/home/anitha/java/jdk1.8.0_271/jre/li...
java.vendor=Oracle Corporation
file.separator=/
java.vendor.url.bug=http://bugreport.sun.com/bugreport/
baseUriPortNumber=6400
sun.cpu.endian=little
sun.io.unicode.encoding=UnicodeLittle
serverWorkingDirectory=/mnt/c/Users/${user.home}/seadasClien...
sun.cpu.isalist=
server ocssw root path: /root/ocssw/scripts
ORS is starting at
Nov 27, 2020 7:06:48 PM org.glassfish.jersey.internal.inject.Providers checkProviderRuntime
WARNING: A provider java.io.InputStream registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider java.io.InputStream will be ignored.
Nov 27, 2020 7:06:48 PM org.glassfish.grizzly.http.server.NetworkListener start
INFO: Started listener bound to [xx.xxx.xx.xx:6400]
Nov 27, 2020 7:06:48 PM org.glassfish.grizzly.http.server.HttpServer start
INFO: [HttpServer] Started.
Jersey new app started with WADL available at http://xx.xxx.xx.xx:6400/ocsswws/application.wadl
Press 'Ctrl' + 'C'  to stop it...

Server starts, but when i opened seadas ocssw its shows "Remote server is down. OCSSW is not accessible. Please start remote server."
How to resolve this issue!?

Thanks
Vimal

[gnwiii]

I had this working with WSL 1 and a couple linux subsystems newer than 16.04.   Have you tested the ocssw software in your Ubuntu 16.04 subsystem?    There is no point trying the client-server configuration if the ocssw software isn't working. You should also know that WSL disk I/O is much slower than for native linux on the same hardware, so you may find the client-server system too slow for your workload.

With WSL 2 the linux system runs in a virtual machine with a separate IP address -- try using the virtual machine configuration.