Server output started showing this java error msg

Jaymer

And I even quit & restarted Aware and you can see the error come up within 30 secs.
Not saying this is an aware issue, just pointing out that something funky is going on.
Tomcat log is fine.
I can log in/out and run the app just fine.
But this error msg seems like a red flag.
Rebooting the server now.

PS _ Others have reported this error recently too. All was fine until yesterday and now this weird msg.
I already changed off of port 9000 when this happened months ago.

8.Java Service Wrapper
Copyright(c) 1999, 2018 Tanuki Software Inc.

9.Page Guide. Copyright (c) 2018 Tracelytics, AppNeta

10.Java-APNS library. Copyright 2018, Mahmood Ali. All rights reserved.

This product also includes software developed by the Apache Software Foundation (http://www.apache.org/).



Server started...
LoginListener: Exception thrown handling socket.
java.net.SocketException: Connection reset
	at java.net.SocketInputStream.read(SocketInputStream.java:209)
	at java.net.SocketInputStream.read(SocketInputStream.java:141)
	at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
	at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
	at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178-)
	at java.io.InputStreamReader.read(InputStreamReader.java:184)
	at java.io.BufferedReader.fill(BufferedReader.java:161)
	at java.io.BufferedReader.readLine(BufferedReader.java:324)
	at java.io.LineNumberReader.readLine(LineNumberReader.java:201)
	at com.bas.basserver.bsmanager.K$_A.run(Unknown Source)
	at java.lang.Thread.run(Thread.java:745)

ACDC

Sometime back with update 2710 there is an item : 1. More robust handling of the login port
I wonder if this has something to do with it ?

(I suspected this was done as a result of my discovery of port 9000 hijacking vulnerability, something that plagued AwareIM for many years ... users were being locked out for no reason that required a server reset )