Unprocessed transactions were not added to empty or non full blocks

[ManuGowda]

Expected behavior

Blocks should be full when we have enough unprocessed transactions in the queue.

Actual behavior

Node doesn't process transactions even though there are enough unprocessed transactions in the queue
This block contains only 4 transactions even though during that point of time there were many unprocessed transactions http://alpha4-seed-01.liskdev.net:6040/block/13226538873268144676

Same here, the below link shows empty blocks even though there were 100's of unprocessed transactions
http://alpha4-seed-01.liskdev.net:6040/block/558195309841882412
http://alpha4-seed-01.liskdev.net:6040/block/15706719315041840789
http://alpha4-seed-01.liskdev.net:6040/block/17560937340718727312

Steps to reproduce

• Run stress test and you will be able to observe the issue (deploy at least 50 nodes)

Which version(s) does this affect? (Environment, OS, etc...)

2.0.0

[SargeKhan]

@MaciejBaj, my PR partially fixed this issue but the network still has partially filled blocked during stress tests are executed. There are still some unknown problem in broadcasting, I am debugging it and reopening the issue.

[shuse2]

3 problems needs to be addressed

• Remove balance sequence from receiveTransaction
• add bundle flag in the transaction pool, to emit event after verify
• increase releaseLimit to 100

[ManuGowda]

With 2.0.0, except the multi-signature transaction, all other transaction processed with a full block(25 transactions).