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

ArrayIndexOutOfBoundsException in AbstractBroadcasterCache #709

Closed
dhoffer opened this issue Oct 26, 2012 · 0 comments
Closed

ArrayIndexOutOfBoundsException in AbstractBroadcasterCache #709

dhoffer opened this issue Oct 26, 2012 · 0 comments
Labels

Comments

@dhoffer
Copy link

dhoffer commented Oct 26, 2012

This was observed in 1.0.1.

Recently I got the following error in AbstractBroadcasterCache.

22 Oct 2012 13:19:07,910 WARN  DefaultBroadcaster []: Unable to track
messages ipt.tas.chatdashboard.ui.gwt.client.comet.CometPayload@745375c0
java.lang.ArrayIndexOutOfBoundsException: 541
        at java.util.concurrent.CopyOnWriteArrayList.get(CopyOnWriteArrayList.java:368)
        at java.util.concurrent.CopyOnWriteArrayList.get(CopyOnWriteArrayList.java:377)
        at org.atmosphere.cache.AbstractBroadcasterCache.addToCache(AbstractBroadcasterCache.java:135)
        at org.atmosphere.cpr.DefaultBroadcaster.trackBroadcastMessage(DefaultBroadcaster.java:845)
        at org.atmosphere.cpr.DefaultBroadcaster.push(DefaultBroadcaster.java:618)
        at org.atmosphere.cpr.DefaultBroadcaster.push(DefaultBroadcaster.java:556)
        at org.atmosphere.cpr.DefaultBroadcaster$2.run(DefaultBroadcaster.java:527)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:722)

Not sure what actually caused this but I notice in code that queue is not fully synchronized (start method) so that could cause this, perhaps something else too? Perhaps in derived classes since queue is protected??

jfarcand added a commit that referenced this issue Oct 26, 2012
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