v8 + Latest Win 2012 Update? Tomcat Fails to RE-Launch

Jaymer

All I know is that recently, when I restart aware, I get the following error and MUST reboot the entire server to correct.

FROM TOMCAT OUTPUT WINDOW IN CONTROL PANEL
SEVERE: StandardServer.await: create[localhost:8005]:
java.net.BindException: Address already in use: JVM_Bind
at java.net.DualStackPlainSocketImpl.bind0(Native Method)
at java.net.DualStackPlainSocketImpl.socketBind(DualStackPlainSocketImpl.java:106)

Today, I just wanted to adjust memory setting in the Control Panel.
So I shutdown and re-launch and Tomcat will not start.
I know both servers had a forced Wind 2012 server update 10 days ago and this has happened on my production machine and a test/play server.
Works as expected on fresh boot.
jaymer...

Rennur

Any chance you've also updated to JDK 1.8.0_181?

Jaymer

no, i don't believe i messed with that.
I tinkered with the Kendo update, just before the latest build, but removed those lines from startup.html

main server is still on v8 - way older version.
only thing changed was the required win2012 updates.

Jaymer

Also just got this after Aware running for 2 days.
Stop config, then Aware.
At re-start, this appeared:

Exception starting JMS adaptors ERROR: org.openadaptor.adaptor.jms.JMSSink - init() failed with JMS Queue/Topic PublishException: org.openadaptor.adaptor.jms.PublishException: org.openadaptor.adaptor.jms.JMSPublisher - connect() failed with JMSException: javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection timed out: connect [java.net.ConnectException: Connection timed out: connect]
Server startup error Unable to start the JMS queues or topics.
Please check that your application server is running
and that the queues and topics are properly configured. exiting...

PointsWell

Are you running with a remote server with a name other than localhost?

If you have run the server and then use the menu items Settings / Database or Settings / Logging then the BASServer.props file gets overwritten and replaces your server name with localhost.

You then get a message similar to the

Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection timed out: connect [java.net.ConnectException: Connection timed out: connect]

Jaymer

sean, this has worked this way fine for more than 6 months... maybe a year.
not remote

just installed latest build 2467 as a test.
noticed that when i started it, i had to stop/restart it a few times to adjust settings.
restarted fine then.
over the weekend, after it has been up a while, i'll see if it still has the issue.
thx

codrin

I can confirm that I am experiencing this same issue on a server that has applied a windows update and the only way to relaunch Tomcat is to reboot the server first. I hope someone finds a solution.

Jaymer

just tried this on build 2467 and did NOT have to reboot.
Acted different than before (ie. didn't need the reboot). Was up about 24 hours.
jaymer...