Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Transactions are not broadcasted after received by postTransactions #3588

Closed
4miners opened this issue May 10, 2019 · 2 comments
Closed

Transactions are not broadcasted after received by postTransactions #3588

4miners opened this issue May 10, 2019 · 2 comments
Assignees
@SargeKhan
Labels
type: bug

Comments

@4miners
Copy link
Contributor

4miners commented May 10, 2019

Expected behavior

Transactions should be broadcasted to rest of the network after received by API.

Actual behavior

They are not.

Steps to reproduce

Send the transaction to a node that has forging disabled, check for its presence on other nodes.

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

2.0.0-alpha.0
@4miners 4miners changed the title Transactions are not broadcasted after receiving by postTransactions Transactions are not broadcasted after received by postTransactions May 10, 2019
@shuse2 shuse2 mentioned this issue May 10, 2019
Merged
@shuse2 shuse2 self-assigned this May 10, 2019
@shuse2 shuse2 closed this as completed in aca5d1f May 13, 2019
@4miners
Copy link
Contributor Author

4miners commented May 13, 2019 •
edited
Loading

The issue is still present in 2.0.0-alpha.2.

Some more details:

The network is deployed as alphanet.

Transactions send to:
http://alpha2-seed-01.liskdev.net:4000/api/node/status

Transactions not present on other nodes, for example:
http://nyc1-alpha2-000.liskdev.net:4000/api/node/status
http://ams2-alpha2-000.liskdev.net:4000/api/node/status

@4miners 4miners reopened this May 13, 2019
@shuse2 shuse2 assigned SargeKhan and unassigned shuse2 May 13, 2019
@4miners
Copy link
Contributor Author

4miners commented May 14, 2019

This issue is happening because of LiskArchive/lisk-newrelic#14

@4miners 4miners closed this as completed May 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@SargeKhan SargeKhan

Labels
type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@shuse2 @SargeKhan @4miners