[
https://issues.apache.org/jira/browse/AMQ-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13662198#comment-13662198
]
Timothy Bish commented on AMQ-4338:
---
This one looks like its fixed now with the latest
[
https://issues.apache.org/jira/browse/AMQ-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13607508#comment-13607508
]
Pedro Marques commented on AMQ-4338:
I was testing the system with fusesource client...
[
https://issues.apache.org/jira/browse/AMQ-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606200#comment-13606200
]
Pedro Marques commented on AMQ-4338:
We have this problem in our servers (activemq
[
https://issues.apache.org/jira/browse/AMQ-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606479#comment-13606479
]
Timothy Bish commented on AMQ-4338:
---
Pedro, what MQTT client are you using to connect to
[
https://issues.apache.org/jira/browse/AMQ-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13587349#comment-13587349
]
Timothy Bish commented on AMQ-4338:
---
I did some profiling and testing today. So far I
[
https://issues.apache.org/jira/browse/AMQ-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13585924#comment-13585924
]
Timothy Bish commented on AMQ-4338:
---
Are you sure those timeouts are sensible, going from
[
https://issues.apache.org/jira/browse/AMQ-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13585942#comment-13585942
]
Kevin Earls commented on AMQ-4338:
--
Actually, you're right, those are probably not
[
https://issues.apache.org/jira/browse/AMQ-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13582646#comment-13582646
]
Timothy Bish commented on AMQ-4338:
---
Added the patch, guess we need to figure out why
