In other words, the thread is sort of an HTTP server? If so, my question would still be why you're creating an HTTP server inside of an HTTP server.
I pinged from command prompt, it worked fine
I used ports 5555, 8080, 8082,6231. I will try 80 and 443.
In the trial you have the following architecture:
[ Internet ]
[ Jelastic Resolver ]
[ Your environment ]
This is because your environment only contains local IP addresses (10.x) so is not directly accessible across the Internet. So the Jelastic Resolver receives connections from the Internet and acts as a proxy to pass requests to your environment. It only proxies ports 80 and 443 (443 is only if the Jelastic Shared SSL feature is enabled).
Unfortunately this is not suitable for socket connections.
To use sockets you need to add a public IP address directly to your application server - then you may connect to the public IP and use any port that you like.
Ulf Dittmer wrote:My point is, you should not start a new thread for HTTP communication. Servlets already do all that - change your server-side code to be a servlet instead, then you don't have to do all that HTTP handling.
Partheban Udayakumar wrote:can the server (say this forum) send the message (data) to only the specified person (me). I mean like our private moosages. How do these redirect them from one client (you) to another (me)?
Ulf Dittmer wrote:
HTTP, web browser and web server are not an environment like the mobile phone system with its SMS and push notifications. You can emulate that to some degree if both clients have an open browser window to the server, but it's a bit of a hack.
1) The client who has to retrieve data from the server has to use his GET method right? Correct me if I am wrong.
2) The client who posts the data has to login to the server first. so there will be a post method. How will he send his message now that is after he uses his POST method for connection.
Think this as a messaging service over internet, do you think we still need to use AJAX for this?