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

Intermittent InterruptedException destroying Broadcaster #768

Closed
jeremy303 opened this issue Dec 12, 2012 · 1 comment
Closed

Intermittent InterruptedException destroying Broadcaster #768

jeremy303 opened this issue Dec 12, 2012 · 1 comment
Labels

Comments

@jeremy303
Copy link

I'm running into an intermittent issue which I'll usually hit if I run a dozen or so iterations of my integration test suite.

Basically, I'm getting an intermittent InterruptedException thrown on a DefaultBroadcaster call stack, although the exact stack can differ (for example, both on broadcast() and push()). This results in my Broadcaster being destroyed and any outgoing message on that Broadcaster to be cached.

It seems to happen on this call, although I think it's possibly happened elsewhere as well.
getBroadcasterFactory().lookup( channelId, true).addAtmosphereResource( atmosphereResource);

The atmosphere resource here is the original AtmosphereResource created in the handshake operation.

Here are Gists w/ two different logs of the behavior. I've also seen it manifest in slightly different ways, but I'm assuming (and hoping) the underlying cause is the same:

https://gist.github.com/d17d6e0a7d253ef39309
https://gist.github.com/5be96904631b332bebd3

I've updated my snapshot from 1.1-SNAPSHOT to 1.1.0-SNAPSHOT and I still see the same intermittent issue.

Here's the log output of a failing test, including the exception stacks:
https://gist.github.com/8254fec1e2ee6f2034a0

I've provided a test case via email.

Thanks!

@jfarcand
Copy link
Member

Using the latest 1.1.0-SNAPSHOT and modifying class WsEventListener (the API has been changed with onPreSuspend callback), I cannot reproduce the issue.

Please try it and let me know, I suspect the fix for #785 also fixed the current issue. Thanks!

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

2 participants