1.hazelcast client is not able to connect to Hazelcast server .
2.on console following message is shown :
INFO: hz.client_1 [simpleserver] [5.1.2] Trying to connect to [192.168.156.149]:5701
hazelcast server hazelcast.xml and client code
Your server XML is 3.6, and the server is something in the 3.* series.
The client is 5.1.2.
See here on compatibility.
Since newer is better, upgrade the server if you can.
Related
I'm trying to develop a web application in nodejs. I'm using an npm package called "simple-peer" but i don't think this issue is related to that. I was able to use this package and get it working when integrating it with a laravel application using an apache server as the back end. I could access the host machine through it's IP:PORT on the network and connect a separate client to the host successfully with a peer-to-peer connection. However, I'm now trying to develop this specifically in node without an apache back end. I have my express server up and running on port 3000, I can access the index page from a remote client on the same network through IP:3000. But when I try to connect through webrtc, I get a "Connection failed" error. If I connect two different browser instances on the same localhost device, the connection succeeds.
For reference: i'm just using the copy/pasted code from this usage demo. I have the "simplepeer.min.js" included and referenced in the correct directory.
So my main questions are: is there a setting or some webRTC protocol that could be blocking the remote clients from connecting? What would I need to change to meet this requirement? Why would it work in a laravel/webpack app with apache and not with express?
If your remote clients can not get icecandidates, you need TURN server.
When WebRTC Peer behind NAT, firewall or using Cellular Network(like smartphone), P2P Connection will fail.
At that time, for fallback, TURN server will work as a relay server.
I recommend coTURN.
Here is an simple implementation of simple-peer with nodejs backend for multi-user video/audio chat. You can find the client code in /public/js/main.js. Github Project and the Demo.
And just like #JinhoJang said. You do need a turn server to pass the information. Here is a list of public stun/turn servers.
The option -Dhazelcast.jmx=true seems to have no effect if I connect to the cluster as a cient:
hzInstance = HazelcastClient.newHazelcastClient(clientConfig);
It works in server mode. What am I doing wrong?
As per the documentation:
You can monitor your Hazelcast members via the JMX protocol
Emphasis mine. As such, you can only get the JMX metrics on a server JVM, from the Hazelcast node it's running.
I was wondering if it would be possible to host a node.js socket.io app in IIS 7 using iisnode? I've read that WebSockets are only supported in IIS 8 but I also read that it might be possible so I am a little bit confused.
Thanks!
From what I've read IIS 8 is the first version of IIS with WebSockets, until then longpolling is used.
As for the output in your comment, you will see that because the Socket.io client is going to attempt to establish a connection by default with longpolling and then will attempt to upgrade the connection to WebSockets, unless you explicitly specify that it shouldn't. This can be done in the options passed to the server and the client at instantiation via the transports Array.
An explanation of how Socket.io works is available here
See the documentation for the Socket.io Server Engine here and the Socket.io Client Engine here
I am working on a project in which I am trying to communicate to the HBase Server via thrift server from a C# client.
I have HBase server set up. I am able to open the socket.
When calling the API: _hbase.getTableNames(), it throws an exception; I stepped into this function ,
it is internally calling - send_getTableNames(); and recv_getTableNames();.
The first function passes (internally they are writing to the socket) but in the second
function they are trying to read from the socket and the client thrift code is receiving zero bytes,
hence it's throwing an exception.
What could be reason for this?
NOTE: the server has HBase 0.92.0 installed on it and using HBase.thrift that comes with it on the thrift server side.
But on the client side we are using the HBase.thrift file that comes with the HBase 0.94.0.
I am guessing this could be the reason( though I may not be correct).
Following is the code snippet on the client side which fails:
transport.Open();
var names = _hbase.getTableNames();
I was using AWS HBase over EMR and then thrift server spinned over the HBase server. while setting up the thrift server, there is an option in AWS Management console to set the allowed IP addresses and the port numbers. I was allowing the port number as 9000 , but the thrift server listens at port number 9090. Once I added the port number 9090 to the allowed port number list I was able to connect to it.
I am trying to connect from Node to a server that is using SSL. The connection works when I connect to a test server, but not the live server I need to connect to.
Does anyone know if Node requires some sort of configuration to support outbound connections?
Thanks
I upgraded node to 0.8 and this started working.