I’ve programming a JAVA application that run on a 4005CD, firmware 11.3s0, the lastest one
This application establishing a TCP connection in order later to analyse the date received by a dedicate PLC
This works fine on my bench test ewon.
I’ve uploaded my Jar and Jad file on another ewon in production line and start the JVM.
My application try to connect on TCP, but immediately close it
I’ve only the event log:
|12/05/2020 10:30:14|JVM|socket::close0 res=7352144 ne=0
|12/05/2020 10:30:13|JVM|socket::open0-connect ipn=1d6a8c0 addr=192.168.214.1 port=102 res=0 ne=0
|12/05/2020 10:30:13|JVM|socket::new fd=40 ne=11
My context is the same than my bench test, the ewon is connected to the same type of equipement in TCP.
As I don’t have a lot of knowledge into JAVA socket connection, i don’t understand the result of the socket close:
socket::close0 res=7352144 ne=0
One remark,not sure it’s linked, but when I have run the JVM, my Ewon Memory has reduce a lot, making appear a red cross into the Status page, memory:
Again, I’m not familiar to the memory page status, and I don’t know how decoding the value given and what can be done on the Ewon or Java in order to recover a good status