serial-port-json-server
serial-port-json-server copied to clipboard
chilipeppr
Question
We are using the 1.95 version of the serial json service. Is there a command to check if a comport is already open? When we sending JSON command to open com port in several browser instances we get open com3 9600 (for example) and then the JSON services stops. doesn't respond anymore to request and we need to restart
You can list the serial ports and it returns whether the port is open or not.
I have seen the bug you're describing occur every now and then and it's probably not hard to track down if you wanted to help fix it and check in your changes on Github.
On Tue, Oct 2, 2018 at 5:29 AM Taillaert [email protected] wrote:
We are using the 1.95 version of the serial json service. Is there a command to check if a comport is already open? When we sending JSON command to open com port in several browser instances we get open com3 9600 (for example) and then the JSON services stops. doesn't respond anymore to request and we need to restart
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/chilipeppr/serial-port-json-server/issues/58, or mute the thread https://github.com/notifications/unsubscribe-auth/AHidbagPOiaqen_D5L6lx8vJWpt1Jcggks5ug1wlgaJpZM4XD7bB .
Thank you for the reply. I've found! Seems when opening the port 2-3 times it gives this bug.
Hi,
Here you can find verbose logging when error occurs. At the end it gives inside spHandler and then it stops. http://prntscr.com/l1aaug
Any way you could take a look at spHandler in the code and see where it might be getting stuck?
On Tue, Oct 2, 2018 at 6:58 AM Taillaert [email protected] wrote:
Hi,
Here you can find verbose logging when error occurs. At the end it gives inside spHandler and then it stops. http://prntscr.com/l1aaug
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/chilipeppr/serial-port-json-server/issues/58#issuecomment-426283969, or mute the thread https://github.com/notifications/unsubscribe-auth/AHidbcZ0DyAQr3azT5f851V-Ljnqh_2Oks5ug3EggaJpZM4XD7bB .
Have problems with pushing it to git now, but looks like issue is solved with this patch:
This patch looks good. So you're saying that on that error there was just an oversight on not removing the mutex lock. Makes sense actually that this got missed. Thanks for the help.