tomcat server slow start for each page- 1+ minute

[swiftinitpvtltd]

Suddenly our tomcat server is doing slow start for few pages(login, forget password)- 1+ minute
It waits for port 9000 connecting and after 1 minute it loads any page.
waits for port 9000 connecting - did anyone saw this issue before on tomcat?

Strange thing is Once after login then subsequent aware query operations connecting to mysql db are not slow.


The same issue is happening for CRM sample app. Just before login it takes 1 minute. Its building a session-connecting to port 9000 taking 1+ minute. After login everything is fast. So its not specific BSV issue as both BSV's showing same issue.

[cishpix]

Do you run it in Linux, right?

I have face this issue too, try restart the server or AwareIM, update the AwareIM, create new one folder but the error still same but now I have fixed it.

[swiftinitpvtltd]

Thanks cishpix. Its on windows 2016 server. We tried restarting entire server, aware IM and tomact but issue remains the same. On login user waits for 1 minute-log shows listening to 9000 port, once login everything is fast.
same for guest user forget password-takes 1 minute to load forget password.

[cishpix]

You're right. When you login, the AwareIM status always said connecting to port 9000 and then will delay for 1-2 mins. After that you can connect into your AwareIM server but when you logout and try login again, the problem is back again.

When you didn't connect, try see your AwareIM status log, is like the below image?

AIM-issue.jpeg (240.43 KiB) Viewed 10426 times

[swiftinitpvtltd]

we have the same error....


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.run(Unknown Source)
at java.lang.Thread.run(Thread.java:745)

[swiftinitpvtltd]

Now luckily everything is just fine today and its fast on login!

May be it was because of global phenomenon in china there was a storm and in US there was a cold weather but finally onset of summer in India balanced the things out and now tomcat server is just balanced with calm. Who knows but now its all good .

[Jaymer]

I had this happen 3 times yesterday. Twice today so far.
I run ConfigTool on a PC connected to remote server.

I notice it first after "Going to Test / Alt-Q" on PC.
Then after switching to Browser, I refresh and nothing happens.

Sometimes I go back to Config and Reconnect to Server (makes me re-enter password).
This sometimes reconnects, other times hangs for minutes.

Right now, I'm going to have to restart Aware on server.
But 2 prior times it corrected itself.

LoginListener: Exception thrown handling socket.
java.lang.NullPointerException
at com.bas.connectionserver.server.ConnectionFactory.isLocalConnection(ConnectionFactory.java:860)
at com.bas.basserver.bsmanager.K.run(Unknown Source)
at java.lang.Thread.run(Thread.java:745)
LoginListener: Exception thrown handling socket.
java.lang.NullPointerException
at com.bas.connectionserver.server.ConnectionFactory.isLocalConnection(ConnectionFactory.java:860)
at com.bas.basserver.bsmanager.K.run(Unknown Source)
at java.lang.Thread.run(Thread.java:745)
LoginListener: Exception thrown handling socket.
java.lang.NullPointerException
at com.bas.connectionserver.server.ConnectionFactory.isLocalConnection(ConnectionFactory.java:860)
at com.bas.basserver.bsmanager.K.run(Unknown Source)
at java.lang.Thread.run(Thread.java:745)
LoginListener: Exception thrown handling socket.

[ACDC]

Change port 9000 to something else, the problem is bound to go away. Sometimes other elements interfere with port 9000 and this results in long login times or no login at all. Also, make sure it's not open for incoming in the firewall