Bitmessage/PyBitmessage-2024-12-18
Archived
2
0
Fork 0
Code Issues 168 Pull Requests 52 Actions Packages Projects Releases 5 Wiki Activity

[BUG] Client stops sending messages #152

New Issue
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)
Copy Link

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)
Copy Link

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)
Copy Link

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 Branch/Tag Specified
Branches Tags
Labels
Clear labels   
bug

Something isn't working as it's supposed to

  
build

Related to building or build system

  
dependencies

Pull requests that update a dependency file

  
developers

The issue is relevant mainly for developers rather than users

  
documentation

   
duplicate

   
enhancement

New feature

  
formatting

Code or UI text formatting

  
invalid

   
legal

   
mobile

Frontend for mobile devices (kivy)

  
obsolete

   
packaging

   
performance

   
protocol

Protocol change

  
question

   
refactoring

   
regression

Some issue, fixed in the past, appears again

  
security

   
test

   
translation

   
usability

   
wontfix
No Label
bug
build
dependencies
developers
documentation
duplicate
enhancement
formatting
invalid
legal
mobile
obsolete
packaging
performance
protocol
question
refactoring
regression
security
test
translation
usability
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
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-18#152
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?