jetstream consumes 100% cpu and becomes un responsive about jetstream

[derekcollison]

Thanks will take a look.

[derekcollison]

I see it is requesting deliverAll and deliverLast which it properly errors on, you can only chose one. But it must not clean it self up properly or something..

[ripienaar]

On jsm side I will be more careful about these combos, will check tomorrow

[derekcollison]

Might also be the advisory being generated.. Will check it out.

[matthiashanel]

Yes I realized that this is what is going on inside the server.
I do not explicitly set both...

In general can we improve the errors returned?
Currently we return a generic error, can we add details? (: )
This is probably a bigger issue and came up on the ngs prod slack today as well.

[ripienaar]

jsm uses a starting template and merged your options with that template. I wasn’t careful to avoid impossible combos there

Regardless server needs to not do what it does. I have worked on better errors but people don’t seem to like it (myself included)

[derekcollison]

I will fix server issue.

[derekcollison]

ok fixed in jetstream branch.

[matthiashanel]

That seems to have done it.

[matthiashanel]

@ripienaar , I created a separate issue for the jsm library. Personally I'd fix this by making it impossible through changing the format altogether. Similar for consumer options.