[BUG] Client stops sending messages #152

Closed
opened 2013-05-15 18:57:47 +02:00 by Dokument · 2 comments
Dokument commented 2013-05-15 18:57:47 +02:00 (Migrated from github.com)

With the spike of traffic last night I, and several others, noticed that we had to re-start our clients in order for them to start processing messages again.

Notes (knowns):
-OS>Windows7,Server2008
-Not processing old messages (only 10 old messages, all of which received ack.)
-CPU> not higher than during idle
-RAM> not higher than during idle
-Message>Work queued for all outgoing messages except those already sent

Fix: Restart required (I did have to restart one client every few hours last night)

With the spike of traffic last night I, and several others, noticed that we had to re-start our clients in order for them to start processing messages again. Notes (knowns): -OS>Windows7,Server2008 -Not processing old messages (only 10 old messages, all of which received ack.) -CPU> not higher than during idle -RAM> not higher than during idle -Message>Work queued for all outgoing messages except those already sent Fix: Restart required (I did have to restart one client every few hours last night)
Atheros1 commented 2013-05-15 23:42:01 +02:00 (Migrated from github.com)

Something must have happened to the worker thread. If you are able to output the console output to a file and, when it happens again, let me know what the exception was and perhaps some other output that happened around it, I would be happy to fix it or add exception-handling to keep the worker thread from dying.
I'm sorry for the inconvenience.

Something must have happened to the worker thread. If you are able to output the console output to a file and, when it happens again, let me know what the exception was and perhaps some other output that happened around it, I would be happy to fix it or add exception-handling to keep the worker thread from dying. I'm sorry for the inconvenience.
Dokument commented 2013-05-20 08:16:59 +02:00 (Migrated from github.com)

Verified with Atheros and fixed here: b5fef550bf

Verified with Atheros and fixed here: https://github.com/Bitmessage/PyBitmessage/commit/b5fef550bfe617548391e1f20c0947bf216e7b70
This repo is archived. You cannot comment on issues.
No Milestone
No project
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2024-12-20#152
No description provided.