search

mashirui521 / RobotVision

A matlab-based robot controller as well as image processor using android smartphone
0 stars 0 forks source link

[Bug] PhoneClient is locked if the server or wifi is not available #11

Closed mashirui521 closed 9 years ago

mashirui521 commented 9 years ago

How-to-repeat: input a ip address and port without starting the server(or make wifi inavailable) click login button

->an no connection exception is logged in LogCat and the app is locked.

Advisement-to-bugfix The exception must be handled.

mashirui521 commented 9 years ago

The availability of server and wifi should be check before coupling

mashirui521 commented 9 years ago

Bugfix is finished.

mashirui521 commented 9 years ago

After Bugfix. The client cannot find server even the server is available.

mashirui521 commented 9 years ago

An action for testing server availability was created. But the testing causes an exception popping up in server: java.io.EOFException at java.io.DataInputStream.readInt(DataInputStream.java:392) at com.robotvision.javaserver.utils.Receiver.run(Receiver.java:31) at com.robotvision.javaserver.ServerSupporter.findClient(ServerSupporter.java:40) at com.robotvision.javaserver.utest.UTestSuite01.UTest01(UTestSuite01.java:18) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.junit.runners.Suite.runChild(Suite.java:127) at org.junit.runners.Suite.runChild(Suite.java:26) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)

more details must be analyzed, but the locking problem on client side has been removed.

mashirui521 commented 9 years ago

The error message was ignored. If the exception causes other bugs in the future, this issue will be reopened.