StompProtocolAndroid
StompProtocolAndroid copied to clipboard
NaikSoftware
STOMP protocol via WebSocket for Android
When the payload is to big, the callback won't be fired. Can this be fixed?
mStompClient = Stomp.over(WebSocket.class, HostConfig.SERVICE_INCOMING); mStompClient.topic("/topic/hello").subscribe(topicMessage -> { Log.d("listenStomp", topicMessage.getPayload()); }); mStompClient.connect(); **_but Logcat show only following lines._** D/WebSocketsConnectionProvider: Emit STOMP message: MESSAGE expires:0 correlation-id: destination:/topic/hello subscription:341c8a71-267a-40b2-a9ef- 3dc36177c2c9 priority:0 type: message-id:ID:Laptop-Jiban-50526-...
I'm facing the same problem which is described [here](https://github.com/NaikSoftware/StompProtocolAndroid/issues/78). The condition for sockets being closed is never met as there is no promise that emitter is already canceled before `doOnCancell()`...
When I pass a brief data message, the framework to work properly. But when I pass large text data content (about> 8k), Android console can not normally accept the message,...
When we use rabbitmq message broker, the heartbeat frame's opcode is 1 instead of 0x9 or 0xA. The android client gets an empty "TEXT" frame. The message broker will close...
when the server parses the message from the BASE64 error occurs because of the characters "\n\n" after the messages: ```java public String compile() { StringBuilder builder = new StringBuilder(); builder.append(mStompCommand).append('\n');...
If I do this ``` mStompClient = Stomp.over(WebSocket.class, endpoint); mStompClient.connect(); ``` and immediately following with ``` switch (lifecycleEvent.getType()) { case OPENED: mStompClient.send(stomp_p2p_channel, msg_body); ``` then message is sent successfully. If...
Hu I have this problem with the last android studio java 1.8..... the lib doesnt work when set the topic or try to connect...help I need this for urgent project....
I just using the demo to connect our websocket url with the authority passcode and login . and I connect successfully,but after few seconds the websocket will automatically closed ....
