-
Notifications
You must be signed in to change notification settings - Fork 9
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
UH OH!! MqttException (0) #2
Comments
Hello, |
Neither am I and I'm just going to bash my way through the java to see if I can get it resolved and will feed back. |
I am also seeing this same issue with this extension, trying to send events over MQTT to confluent MQTT-proxy. Permissions issues seems unlikely but I could be way off. Looks like its using a simple in memory persistence object. Line 66 in 079d47c
Edit: My situation was an admin event which doesnt use the MemoryPersistence object. So it very well could be a permissions issue. |
Do you have a traceback you can share? |
I have keycloak running in a docker container. I made a small modification to the admin event code to use in memory persistence and im going to test that out now. |
thanks for investigating! I still see a reference to org.eclipse.paho.client.mqttv3.persist.MqttDefaultFilePersistence.open in the traceback, hence why I suspect a file permission problem. The docker container might set tighter file permissions than expected. |
I think its definitely a permission issue, by using the MemoryPersistence instance for admin events the problem goes away (as far as i can tell). I'm still dealing with a connection refused issue at the moment. |
I've faced with the same issue, KeyCloak v9 + this event listener, and get a "connection refused". After some investigation looks like listener use default value for mqtt serverUri parameter that leads to connection refused issue. I didn't get proper solution, but tried to hardcode my mqtt url, and seems it works. Hope it will be helpful for further debugging. |
You can set the event listener's properties in standalone.xml next to the other SPI sections, like so:
This was explained in the README. |
@mhuin I did, but it didn't work. |
Ok, there is my setup, anyone interested - feel free to try reproduce it:
built by: |
@ivanovmi I think your problem is the permissions of standalone.xml after the copy, they change during the copy in my experience and can no longer be read by keycloak. |
@hitchan good point, thank you. I've updated permissions/ownership to be consistent with base image, but still get the same connection refused error, with the same default serverUri in connection string. |
@ivanovmi @hitchan
|
Apologies for the late resolution. I believe the issue is fixed in the latest release. Thanks to @xaralis for their help in solving the issue! |
Hi,
I've added this event listener to keycloak 9, and for the first few messages all seems fine (both tcp and ws), however after a while it then drops out and struggles to reconnect.
The text was updated successfully, but these errors were encountered: