Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid Packet Type #1030

Open
realdognose opened this issue Dec 30, 2023 · 0 comments
Open

Invalid Packet Type #1030

realdognose opened this issue Dec 30, 2023 · 0 comments

Comments

@realdognose
Copy link

realdognose commented Dec 30, 2023

After some time of usage, the Pharo-client just disconnects with the error:

relates to REASON_CODE_INVALID_MESSAGE

Paket nicht erkannt (32108)
at org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:31)
at org.eclipse.paho.client.mqttv3.internal.wire.MqttInputStream.readMqttWireMessage(MqttInputStream.java:99)
at org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:137)

Restarting the application immediately produces the same error again, only restarting the broker helps (for some time)

So, apparently the broker is sending "something" invalid there.

However, this exception can't be handled code-wise (from the app) because paho itself decides that this is a non-recoverable error and goes into stop-state. at:

catch (MqttException ex) {
	//@TRACE 856=Stopping, MQttException
	log.fine(CLASS_NAME,methodName,"856",null,ex);
	synchronized (lifecycle) {
		target_state = State.STOPPED;
	}
	// Token maybe null but that is handled in shutdown
	clientComms.shutdownConnection(token, ex);
}

Any Workarounds to "reject / ignore" invalid messages?
Other MQTT-Clients are just working fine at the same time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant