In the Azure Cloud raised Tomcat. In Tomcott, there is a REST service (for system user clients), which has a service that raises a server socket to accept connections from system service clients and respond to requests. Also, the service can connect to these same service clients directly over IP through the same sockets. Service clients - android and pc.

The problem is that when you start the service on the local Tomketa server-socket works fine, and when running in Azure - the desired port is not available. I cannot configure server.xml in Azura, because when I try to change it, Azur gives an access rights error. The current configuration of the connector Tomcat in Azura:

<Connector port="${port.http}" protocol="HTTP/1.1" address="127.0.0.1" connectionTimeout="20000" />

Actually the question is: is it possible to somehow open the required port in Tomcate within Azura?

If not, which option is preferable?

  1. Web sockets
  2. Make a connection to the server in REST, and leave the reverse connection through sockets
  3. something else?
  • Wait, how did you deploy TomCat there? On a simple virtual machine (IaaS) or on a CloudService (PaaS)? Why choose not to use the Azure Website? There TomCat works better and less hassle with administration. TomCat can be raised in various ways and the problem will be solved in completely different ways. Maybe this is not a problem at all of Tom Cate, but the settings of the firewall of the machine. - Walter Nuss
  • @Walter TomCat raised as a ready-made web application (Create -> Internet + mobile devices -> Web application). I tried to create "Azure Website + SQL" - my DreamSpark subscription did not allow me to do this: ( - dranzerx
  • I did not find a solution, I switched to web sockets. - dranzerx

0