anhlephuoc
anhlephuoc
MQTT3.1.1: The Server, upon the reception of a CONN packet, may or may not reply with a CONNACK (which this code is waiting for) but may just close the network...
One of the forks may have that fixed already but I haven't check. An temporary immediate fix is to check for the $string to be of the required length (4)...
And you should also do similar check a few lines later for the when the error message is printed as well. If code arrives here, it means that you have...
Further investigation with a protocol analyser (wireshark) connected indicate the following problems: phpMQTT closes connection too liberally when it detect some problems. MQTT uses(require) reliable TCP protocol or equivalent. So...
php 7.3 or later should be OK. If you can't upgrade php then just remove the :void, but that would only defer the problem to return and haunt you at...
This can be fixed by inserting at line 479: $found = true; // mark matched topic as found
Apart from the Broker response(CONNACK) to the connect() call, phpMQTT does not have any code to receive or send any acknowledgments from/to the MQTT Broker. Consequently it will not be...
This happens usually when the Broker drops the connection on purpose and for good reason. Returning a false is not useful because this is called from many different places, and...
The problem actual occurs at fwrite() not just $this->_fwrite(). The false is returned when fwrite() face the condition: invalid stream ID, physical connection error, connection closure by local or remote...
The $con variable you used in the procMsg() function is a local version because it is undeclared. An uninitialised $con is used. If you want to refer to the GLOBAL...