gpt4 book ai didi

java - 使用 MQTT Android 服务从飞行模式重新连接

转载 作者:搜寻专家 更新时间:2023-11-01 08:45:42 26 4
gpt4 key购买 nike

我正在实现此处找到的 Dale Lane MQTT Android 服务示例 http://dalelane.co.uk/blog/?p=1599 ,该示例对于我的特定目的运行良好,但我正在处理 1 个我似乎无法解决的问题。

经过相当广泛的测试,我发现在手机完全失去连接后,该服务不会重新连接。例如,如果手机处于飞行模式然后退出飞行模式,该服务将继续尝试 connectToBroker() 但永远不会连接。

如果我按下主屏幕上的“连接”按钮以使用给定的主机/主题参数启动服务,应用程序将正确连接。

我该如何解决这个问题?应用程序从 Wifi 网络重新连接没有问题,反之亦然。

02-16 12:19:39.348: E/mqtt(23628): ping failed - MQTT exception
02-16 12:19:39.348: E/mqtt(23628): com.ibm.mqtt.MqttNotConnectedException
02-16 12:19:39.348: E/mqtt(23628): at com.ibm.mqtt.Mqtt.writePacket(Unknown Source)
02-16 12:19:39.348: E/mqtt(23628): at com.ibm.mqtt.Mqtt.pingOut(Unknown Source)
02-16 12:19:39.348: E/mqtt(23628): at com.ibm.mqtt.MqttClient.ping(Unknown Source)
02-16 12:19:39.348: E/mqtt(23628): at com.limosys.limosystestmqtt.MQTTService$PingSender.onReceive(MQTTService.java:919)
02-16 12:19:39.348: E/mqtt(23628): at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:778)
02-16 12:19:39.348: E/mqtt(23628): at android.os.Handler.handleCallback(Handler.java:733)
02-16 12:19:39.348: E/mqtt(23628): at android.os.Handler.dispatchMessage(Handler.java:95)
02-16 12:19:39.348: E/mqtt(23628): at android.os.Looper.loop(Looper.java:136)
02-16 12:19:39.348: E/mqtt(23628): at android.app.ActivityThread.main(ActivityThread.java:5105)
02-16 12:19:39.348: E/mqtt(23628): at java.lang.reflect.Method.invokeNative(Native Method)
02-16 12:19:39.348: E/mqtt(23628): at java.lang.reflect.Method.invoke(Method.java:515)
02-16 12:19:39.348: E/mqtt(23628): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:792)
02-16 12:19:39.348: E/mqtt(23628): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:608)
02-16 12:19:39.348: E/mqtt(23628): at dalvik.system.NativeStart.main(Native Method)

这是 ping 失败时抛出的异常的堆栈跟踪,应用程序会根据给定的 keepAliveSecond 值继续尝试每 10 秒连接一次。

连接丢失

/*
* callback - method called when we no longer have a connection to the message broker server
*/
public void connectionLost() throws Exception {
// we protect against the phone switching off while we're doing this
// by requesting a wake lock - we request the minimum possible wake
// lock - just enough to keep the CPU running until we've finished
PowerManager pm = (PowerManager) getSystemService(POWER_SERVICE);
WakeLock wl = pm.newWakeLock(PowerManager.PARTIAL_WAKE_LOCK, "MQTT");
wl.acquire();


//
// have we lost our data connection?
//

if (isOnline() == false) {
Log.e("CONNECTION LOST", "LOST CONNECTION");
connectionStatus = MQTTConnectionStatus.NOTCONNECTED_WAITINGFORINTERNET;

// inform the app that we are not connected any more
broadcastServiceStatus("Connection lost - no network connection");

//
// inform the user (for times when the Activity UI isn't running)
// that we are no longer able to receive messages
notifyUser("Connection lost - no network connection", "MQTT",
"Connection lost - no network connection");

//
// wait until the phone has a network connection again, when we
// the network connection receiver will fire, and attempt another
// connection to the broker
} else {
//
// we are still online
// the most likely reason for this connectionLost is that we've
// switched from wifi to cell, or vice versa
// so we try to reconnect immediately
//

connectionStatus = MQTTConnectionStatus.NOTCONNECTED_UNKNOWNREASON;

// inform the app that we are not connected any more, and are
// attempting to reconnect
broadcastServiceStatus("Connection lost - reconnecting...");

// try to reconnect
if (connectToBroker()) {
subscribeToTopic(topicName);
}
}

// we're finished - if the phone is switched off, it's okay for the CPU
// to sleep now
wl.release();
}

连接到经纪人此代码在服务可用后调用多次(即退出飞行模式并连接到 4G/Wifi)

 /*
* (Re-)connect to the message broker
*/
private boolean connectToBroker() {
try {
// try to connect
Log.e("CONNECTTOBROKER", "TRYING TO CONNECT");
Log.e("SERVICE HOST - CONNECT TO BROKER", "" + brokerHostName);
Log.e("SERVICE TOPIC - CONNECT TO BROKER", "" + topicName);

mqttClient.connect(generateClientId(), cleanStart, keepAliveSeconds);

//
// inform the app that the app has successfully connected
broadcastServiceStatus("Connected");

// we are connected
connectionStatus = MQTTConnectionStatus.CONNECTED;

// we need to wake up the phone's CPU frequently enough so that the
// keep alive messages can be sent
// we schedule the first one of these now
scheduleNextPing();


return true;
} catch (MqttException e) {
// something went wrong!

connectionStatus = MQTTConnectionStatus.NOTCONNECTED_UNKNOWNREASON;

//
// inform the app that we failed to connect so that it can update
// the UI accordingly
broadcastServiceStatus("Unable to connect");

//
// inform the user (for times when the Activity UI isn't running)
// that we failed to connect
notifyUser("Unable to connect", "MQTT", "Unable to connect - will retry later");

// if something has failed, we wait for one keep-alive period before
// trying again
// in a real implementation, you would probably want to keep count
// of how many times you attempt this, and stop trying after a
// certain number, or length of time - rather than keep trying
// forever.
// a failure is often an intermittent network issue, however, so
// some limited retry is a good idea
scheduleNextPing();

return false;
}
}

最佳答案

从paho下载最新的android service jar(1.02)和java client(1.02)。最新的 Android 服务 jar 已修复此问题。一旦网络连接恢复,它就会重新连接。

在 Activity 的 onResume() 中添加这个

mqttclient.registerResources(this);     

和这个在同一个 Activity 的 onDestroy() 中

mqttclient.unregisterResources();

这对我有用。

关于java - 使用 MQTT Android 服务从飞行模式重新连接,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/28546973/

26 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com