Matching versions, but "server uses incompatible communication protocol"

Started by Tursiops, February 10, 2016, 05:35:22 AM

Previous topic - Next topic

Tursiops

Hi,

After upgrading the server to version 2.0.2, followed by deploying the latest web nxmc-2.0.2.war to the local Tomcat server (stopped Tomcat, deleted the old .war and directory, deployed the new one, restarted Tomcat, confirmed it deployed), I can't login via web console anymore. The local management console (also upgraded to 2.0.2) works fine.
The error message is "server uses incompatible communication protocol", which tells me that there must be a wrong version somewhere. But netxmsd -v gives me a NetXMS Server Version 2.0.2 Build 8060 and the .war file is the one currently on the website: nxmc-2.0.2.war. Redeploying did not help. Different browsers and systems: same result.

Not sure if I'm going crazy or if there is something I am missing?

Thanks

tomaskir

What build does the web console show you?
Its in the bottom right corner.

Tursiops

 :o I admit I did not see that. Says version 2.0.1 so that'll obviously not work.

Now I just have no idea WHY it still says 2.0.1. I know I removed the old .war file and downloaded the nxmc-2.0.2.war one.
Tomcat was stopped, started, server rebooted...
Does Tomcat have some additional cache somewhere?

Tursiops

Ok, got it.

Not having used Tomcat before I didn't really think much about what effect renaming the .war files might have - I renamed nxmc-2.0.1.war to nxmc.war.
For the upgrade I stopped Tomcat, removed that .war file and the /var/lib/tomcat7/webapps/nxmc directory.
Then I downloaded the new nxmc-2.0.2.war file and renamed it to nxmc.war as well, prior to restarting Tomcat.
That's probably where things went wrong - as I found stuff still sitting in /var/lib/tomcat7/work/Catalina/localhost/nxmc. :-[

So I went through the process again, cleaning up that second directory too and it's all working now.

Cheers

Alex Kirhenshtein

Actually you don't need to restart Tomcat. In default configuration it support hot deploy – just remove old war file (don't remove uncompressed folder, just war) and copy new one. It even should detect if you just replace with new version.