Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / hivemq/hivemq-mqtt-client issues and pull requests

#494 - Concurrent handling of messages on high load

Issue - State: closed - Opened by rubengees over 3 years ago - 3 comments
Labels: question

#494 - Concurrent handling of messages on high load

Issue - State: closed - Opened by rubengees over 3 years ago - 3 comments
Labels: question

#493 - Connection to mqtt server failed! (recvfrom failed)

Issue - State: closed - Opened by amindadgar over 3 years ago - 2 comments
Labels: question

#493 - Connection to mqtt server failed! (recvfrom failed)

Issue - State: closed - Opened by amindadgar over 3 years ago - 2 comments
Labels: question

#493 - Connection to mqtt server failed! (recvfrom failed)

Issue - State: closed - Opened by amindadgar over 3 years ago - 2 comments
Labels: question

#493 - Connection to mqtt server failed! (recvfrom failed)

Issue - State: closed - Opened by amindadgar over 3 years ago - 2 comments
Labels: question

#491 - QoS 1 PUBLISH must not be resent during the same connection

Issue - State: closed - Opened by HiwayChe over 3 years ago - 8 comments
Labels: question

#491 - QoS 1 PUBLISH must not be resent during the same connection

Issue - State: closed - Opened by HiwayChe over 3 years ago - 8 comments
Labels: question

#491 - QoS 1 PUBLISH must not be resent during the same connection

Issue - State: closed - Opened by HiwayChe over 3 years ago - 8 comments
Labels: question

#491 - QoS 1 PUBLISH must not be resent during the same connection

Issue - State: closed - Opened by HiwayChe over 3 years ago - 8 comments
Labels: question

#490 - Regarding Netty 4.1.48.Final vulnerability

Issue - State: open - Opened by endevcy over 3 years ago - 4 comments

#490 - Regarding Netty 4.1.48.Final vulnerability

Issue - State: closed - Opened by endevcy over 3 years ago - 6 comments

#490 - Regarding Netty 4.1.48.Final vulnerability

Issue - State: open - Opened by endevcy over 3 years ago - 4 comments

#490 - Regarding Netty 4.1.48.Final vulnerability

Issue - State: open - Opened by endevcy over 3 years ago - 4 comments

#490 - Regarding Netty 4.1.48.Final vulnerability

Issue - State: open - Opened by endevcy over 3 years ago - 4 comments

#490 - Regarding Netty 4.1.48.Final vulnerability

Issue - State: open - Opened by endevcy over 3 years ago - 4 comments

#488 - NoClassDefFoundError in Android 5-6 when built in Android Studio 4.2.1

Issue - State: closed - Opened by aloz77 over 3 years ago - 15 comments

#488 - NoClassDefFoundError in Android 5-6 when built in Android Studio 4.2.1

Issue - State: closed - Opened by aloz77 over 3 years ago - 15 comments

#488 - NoClassDefFoundError in Android 5-6 when built in Android Studio 4.2.1

Issue - State: closed - Opened by aloz77 over 3 years ago - 15 comments

#488 - NoClassDefFoundError in Android 5-6 when built in Android Studio 4.2.1

Issue - State: closed - Opened by aloz77 over 3 years ago - 15 comments

#488 - NoClassDefFoundError in Android 5-6 when built in Android Studio 4.2.1

Issue - State: closed - Opened by aloz77 over 3 years ago - 15 comments

#488 - NoClassDefFoundError in Android 5-6 when built in Android Studio 4.2.1

Issue - State: closed - Opened by aloz77 over 3 years ago - 15 comments

#486 - HiveMQ client doesn't send ping request to broker if smartwatch screen is off (Android)

Issue - State: closed - Opened by cd over 3 years ago - 10 comments
Labels: question

#486 - HiveMQ client doesn't send ping request to broker if smartwatch screen is off (Android)

Issue - State: closed - Opened by cd over 3 years ago - 10 comments
Labels: question

#486 - HiveMQ client doesn't send ping request to broker if smartwatch screen is off (Android)

Issue - State: closed - Opened by cd over 3 years ago - 10 comments
Labels: question

#486 - HiveMQ client doesn't send ping request to broker if smartwatch screen is off (Android)

Issue - State: closed - Opened by cd over 3 years ago - 10 comments
Labels: question

#486 - HiveMQ client doesn't send ping request to broker if smartwatch screen is off (Android)

Issue - State: closed - Opened by cd over 3 years ago - 10 comments
Labels: question

#485 - How to Handle Timeouts While Publishing a Message

Issue - State: closed - Opened by teivah over 3 years ago - 2 comments

#485 - How to Handle Timeouts While Publishing a Message

Issue - State: closed - Opened by teivah over 3 years ago - 2 comments

#485 - How to Handle Timeouts While Publishing a Message

Issue - State: closed - Opened by teivah over 3 years ago - 4 comments

#484 - Mqtt5PubRecException: PUBREC contained an Error Code

Issue - State: closed - Opened by digrec over 3 years ago - 7 comments
Labels: question

#484 - Mqtt5PubRecException: PUBREC contained an Error Code

Issue - State: open - Opened by digrec over 3 years ago - 4 comments
Labels: question

#484 - Mqtt5PubRecException: PUBREC contained an Error Code

Issue - State: open - Opened by digrec over 3 years ago - 4 comments
Labels: question

#484 - Mqtt5PubRecException: PUBREC contained an Error Code

Issue - State: open - Opened by digrec over 3 years ago - 4 comments
Labels: question

#481 - Manual Acknowledgment not working after reconnect

Issue - State: closed - Opened by PMacho over 3 years ago - 13 comments
Labels: invalid

#481 - Manual Acknowledgment not working after reconnect

Issue - State: closed - Opened by PMacho over 3 years ago - 13 comments
Labels: invalid

#481 - Manual Acknowledgment not working after reconnect

Issue - State: closed - Opened by PMacho over 3 years ago - 13 comments
Labels: invalid

#481 - Manual Acknowledgment not working after reconnect

Issue - State: closed - Opened by PMacho over 3 years ago - 13 comments
Labels: invalid

#479 - Feature/info logging

Pull Request - State: open - Opened by Sarek over 3 years ago - 5 comments

#465 - Support For RxJava3

Issue - State: closed - Opened by Brabalawuka almost 4 years ago - 2 comments
Labels: question

#465 - Support For RxJava3

Issue - State: closed - Opened by Brabalawuka almost 4 years ago - 2 comments
Labels: question

#464 - Feature Request: Options to pass ALPN and SNI while connecting to AWS IoT

Issue - State: open - Opened by onlybytes almost 4 years ago - 5 comments
Labels: feature-request

#459 - Variant resolution failure since gradle 6

Issue - State: closed - Opened by mathieuruellan almost 4 years ago - 4 comments

#459 - Variant resolution failure since gradle 6

Issue - State: closed - Opened by mathieuruellan almost 4 years ago - 4 comments

#459 - Variant resolution failure since gradle 6

Issue - State: closed - Opened by mathieuruellan almost 4 years ago - 4 comments

#459 - Variant resolution failure since gradle 6

Issue - State: closed - Opened by mathieuruellan almost 4 years ago - 4 comments

#459 - Variant resolution failure since gradle 6

Issue - State: closed - Opened by mathieuruellan almost 4 years ago - 4 comments

#456 - Feature Request: offer control over message buffering when disconnected

Issue - State: open - Opened by fraschbi almost 4 years ago - 3 comments
Labels: feature-request

#456 - Feature Request: offer control over message buffering when disconnected

Issue - State: open - Opened by fraschbi almost 4 years ago - 3 comments
Labels: feature-request

#456 - Feature Request: offer control over message buffering when disconnected

Issue - State: open - Opened by fraschbi almost 4 years ago - 3 comments
Labels: feature-request

#456 - Feature Request: offer control over message buffering when disconnected

Issue - State: open - Opened by fraschbi almost 4 years ago - 3 comments
Labels: feature-request

#456 - Feature Request: offer control over message buffering when disconnected

Issue - State: open - Opened by fraschbi almost 4 years ago - 3 comments
Labels: feature-request

#455 - incoming publishes are acknowledged when publish flow dies

Issue - State: closed - Opened by smaugs almost 4 years ago - 7 comments
Labels: question

#455 - incoming publishes are acknowledged when publish flow dies

Issue - State: closed - Opened by smaugs almost 4 years ago - 7 comments
Labels: question

#455 - incoming publishes are acknowledged when publish flow dies

Issue - State: closed - Opened by smaugs almost 4 years ago - 7 comments
Labels: question

#455 - incoming publishes are acknowledged when publish flow dies

Issue - State: closed - Opened by smaugs almost 4 years ago - 7 comments
Labels: question

#455 - incoming publishes are acknowledged when publish flow dies

Issue - State: closed - Opened by smaugs almost 4 years ago - 7 comments
Labels: question

#453 - Any plans for writing a Kotlin Coroutines/Flow API?

Issue - State: open - Opened by FilippoVigani almost 4 years ago - 3 comments
Labels: help wanted, question, feature-request

#453 - Any plans for writing a Kotlin Coroutines/Flow API?

Issue - State: open - Opened by FilippoVigani almost 4 years ago - 5 comments
Labels: help wanted, question, feature-request

#453 - Any plans for writing a Kotlin Coroutines/Flow API?

Issue - State: open - Opened by FilippoVigani almost 4 years ago - 3 comments
Labels: help wanted, question, feature-request

#453 - Any plans for writing a Kotlin Coroutines/Flow API?

Issue - State: open - Opened by FilippoVigani almost 4 years ago - 3 comments
Labels: help wanted, question, feature-request

#448 - GraalVM Native Image

Issue - State: closed - Opened by deen13 about 4 years ago - 1 comment
Labels: question

#448 - GraalVM Native Image

Issue - State: closed - Opened by deen13 about 4 years ago - 1 comment
Labels: question

#448 - GraalVM Native Image

Issue - State: closed - Opened by deen13 about 4 years ago - 1 comment
Labels: question

#448 - GraalVM Native Image

Issue - State: closed - Opened by deen13 about 4 years ago - 1 comment
Labels: question

#448 - GraalVM Native Image

Issue - State: closed - Opened by deen13 about 4 years ago - 1 comment
Labels: question

#441 - Quarkus native builds

Issue - State: closed - Opened by Tockra over 4 years ago - 8 comments
Labels: question

#441 - Quarkus native builds

Issue - State: closed - Opened by Tockra over 4 years ago - 8 comments
Labels: question

#441 - Quarkus native builds

Issue - State: closed - Opened by Tockra over 4 years ago - 8 comments
Labels: question

#441 - Quarkus native builds

Issue - State: closed - Opened by Tockra over 4 years ago - 8 comments
Labels: question

#441 - Quarkus native builds

Issue - State: closed - Opened by Tockra over 4 years ago - 8 comments
Labels: question

#384 - W3C trace context propagation and OpenTracing / OpenTelemetry support

Issue - State: open - Opened by frittentheke over 4 years ago - 4 comments
Labels: help wanted, feature-request

#381 - Support URIs to connect to a cluster (multiple server)

Issue - State: open - Opened by FrVaBe over 4 years ago - 2 comments
Labels: help wanted, feature-request

#381 - Support URIs to connect to a cluster (multiple server)

Issue - State: open - Opened by FrVaBe over 4 years ago - 2 comments
Labels: help wanted, feature-request

#381 - Support URIs to connect to a cluster (multiple server)

Issue - State: open - Opened by FrVaBe over 4 years ago - 2 comments
Labels: help wanted, feature-request

#381 - Support URIs to connect to a cluster (multiple server)

Issue - State: open - Opened by FrVaBe over 4 years ago - 2 comments
Labels: help wanted, feature-request

#381 - Support URIs to connect to a cluster (multiple server)

Issue - State: open - Opened by FrVaBe over 4 years ago - 2 comments
Labels: help wanted, feature-request

#361 - Reconnection is not successful with ActiveMQ broker with MQTT enabled.

Issue - State: closed - Opened by dileepmandapam almost 5 years ago - 3 comments
Labels: question

#361 - Reconnection is not successful with ActiveMQ broker with MQTT enabled.

Issue - State: closed - Opened by dileepmandapam almost 5 years ago - 3 comments
Labels: question

#361 - Reconnection is not successful with ActiveMQ broker with MQTT enabled.

Issue - State: closed - Opened by dileepmandapam almost 5 years ago - 3 comments
Labels: question

#361 - Reconnection is not successful with ActiveMQ broker with MQTT enabled.

Issue - State: closed - Opened by dileepmandapam almost 5 years ago - 3 comments
Labels: question

#361 - Reconnection is not successful with ActiveMQ broker with MQTT enabled.

Issue - State: closed - Opened by dileepmandapam almost 5 years ago - 3 comments
Labels: question

#346 - Option to specify more then one server in disconnected listener ?

Issue - State: closed - Opened by jayjamba almost 5 years ago - 7 comments
Labels: question

#346 - Option to specify more then one server in disconnected listener ?

Issue - State: closed - Opened by jayjamba almost 5 years ago - 7 comments
Labels: question

#344 - Setting credentials in MqttClientDisconnectedListener

Issue - State: closed - Opened by samuelbacaner about 5 years ago - 4 comments
Labels: question

#344 - Setting credentials in MqttClientDisconnectedListener

Issue - State: closed - Opened by samuelbacaner about 5 years ago - 4 comments
Labels: question

#344 - Setting credentials in MqttClientDisconnectedListener

Issue - State: closed - Opened by samuelbacaner about 5 years ago - 4 comments
Labels: question

#344 - Setting credentials in MqttClientDisconnectedListener

Issue - State: closed - Opened by samuelbacaner about 5 years ago - 4 comments
Labels: question

#344 - Setting credentials in MqttClientDisconnectedListener

Issue - State: closed - Opened by samuelbacaner about 5 years ago - 4 comments
Labels: question

#309 - A Complete Android Project Would be Helpful

Issue - State: open - Opened by shriharsha-bhagwat over 5 years ago - 3 comments
Labels: help wanted, good first issue

#309 - A Complete Android Project Would be Helpful

Issue - State: open - Opened by shriharsha-bhagwat over 5 years ago - 3 comments
Labels: help wanted, good first issue

#309 - A Complete Android Project Would be Helpful

Issue - State: open - Opened by shriharsha-bhagwat over 5 years ago - 3 comments
Labels: help wanted, good first issue

#309 - A Complete Android Project Would be Helpful

Issue - State: open - Opened by shriharsha-bhagwat over 5 years ago - 3 comments
Labels: help wanted, good first issue

#306 - Cancel automatic reconnect calling connect or disconnect

Issue - State: closed - Opened by SgtSilvio over 5 years ago - 9 comments
Labels: improvement