Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TimeoutExceptions cause Null reference exceptions #177

Closed
jgoyvaerts opened this issue Jan 16, 2018 · 4 comments
Closed

TimeoutExceptions cause Null reference exceptions #177

jgoyvaerts opened this issue Jan 16, 2018 · 4 comments
Labels
Milestone

Comments

@jgoyvaerts
Copy link
Contributor

jgoyvaerts commented Jan 16, 2018

When a timeout exception occurs when you refresh Queues or other top nodes, a null reference exception occurs as a result of incorrect nodes list removal (relayServiceListNode is attempted to be removed for queues, topics, event hubs and notification hubs)

jgoyvaerts added a commit to jgoyvaerts/ServiceBusExplorer that referenced this issue Jan 16, 2018
@SeanFeldman SeanFeldman added this to the 4.0.106 milestone Jan 17, 2018
@SeanFeldman
Copy link
Collaborator

Thank you @jgoyvaerts for catching this and sending a PR.
I took the liberty to update issue with details why the NullReference why taking place.

@paolosalvatori
Copy link
Owner

Thanks @jgoyvaerts

@PratikMSFT
Copy link

Customers has issue connecting through latest SB explorer version with 1000 entities in queues getting timeout, any options to tackle this problem please

@ErikMogensen
Copy link
Collaborator

@PratikMSFT , increase the Receive timeout setting and perhaps the Server timeout setting too in the View -> Options dialog.

In the next release the default settings for these are greatly increased.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants