9:05 a.m.
Stian Thorgersen created RF-12013:
-------------------------------------
Summary: Deadlock in push component
Key: RF-12013
URL: https://issues.jboss.org/browse/RF-12013
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.Final
Reporter: Stian Thorgersen
Deadlocked threads in the push component prevented server from stopping. Not sure whether
or not this happened when I initiated shutdown or if these where hanging around for a
while.
Relevant output from jstack:
{code}
Found one Java-level deadlock:
=============================
"push-publish-thread-1":
waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a
org.richfaces.application.push.impl.RequestImpl),
which is held by "Atmosphere-AsyncWrite-0"
"Atmosphere-AsyncWrite-0":
waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a
org.richfaces.application.push.impl.SessionImpl),
which is held by "push-publish-thread-1"
Java stack information for the threads listed above:
===================================================
"push-publish-thread-1":
at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85)
- waiting to lock <0x00000000e5ed5a50> (a
org.richfaces.application.push.impl.RequestImpl)
at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237)
- locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl)
at
org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88)
at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
"Atmosphere-AsyncWrite-0":
at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
- waiting to lock <0x00000000e5ed59a0> (a
org.richfaces.application.push.impl.SessionImpl)
at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107)
at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115)
at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185)
- locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl)
at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129)
- locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl)
at
org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713)
at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747)
- locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Found 1 deadlock.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:38 p.m.
[
https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.s...
]
Brian Leathem reassigned RF-12013:
----------------------------------
Assignee: Lukáš Fryč
Lukas, please assess and schedule this issue as appropriate.
Deadlock in push component
--------------------------
Key: RF-12013
URL: https://issues.jboss.org/browse/RF-12013
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.Final
Reporter: Stian Thorgersen
Assignee: Lukáš Fryč
Deadlocked threads in the push component prevented server from stopping. Not sure whether
or not this happened when I initiated shutdown or if these where hanging around for a
while.
Relevant output from jstack:
{code}
Found one Java-level deadlock:
=============================
"push-publish-thread-1":
waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a
org.richfaces.application.push.impl.RequestImpl),
which is held by "Atmosphere-AsyncWrite-0"
"Atmosphere-AsyncWrite-0":
waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a
org.richfaces.application.push.impl.SessionImpl),
which is held by "push-publish-thread-1"
Java stack information for the threads listed above:
===================================================
"push-publish-thread-1":
at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85)
- waiting to lock <0x00000000e5ed5a50> (a
org.richfaces.application.push.impl.RequestImpl)
at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237)
- locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl)
at
org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88)
at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
"Atmosphere-AsyncWrite-0":
at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
- waiting to lock <0x00000000e5ed59a0> (a
org.richfaces.application.push.impl.SessionImpl)
at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107)
at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115)
at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185)
- locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl)
at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129)
- locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl)
at
org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713)
at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747)
- locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Found 1 deadlock.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:37 a.m.
[
https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.s...
]
Stian Thorgersen commented on RF-12013:
---------------------------------------
Happened again now, this time it was caused by a re-deploy
Deadlock in push component
--------------------------
Key: RF-12013
URL: https://issues.jboss.org/browse/RF-12013
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.Final
Reporter: Stian Thorgersen
Assignee: Lukáš Fryč
Deadlocked threads in the push component prevented server from stopping. Not sure whether
or not this happened when I initiated shutdown or if these where hanging around for a
while.
Relevant output from jstack:
{code}
Found one Java-level deadlock:
=============================
"push-publish-thread-1":
waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a
org.richfaces.application.push.impl.RequestImpl),
which is held by "Atmosphere-AsyncWrite-0"
"Atmosphere-AsyncWrite-0":
waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a
org.richfaces.application.push.impl.SessionImpl),
which is held by "push-publish-thread-1"
Java stack information for the threads listed above:
===================================================
"push-publish-thread-1":
at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85)
- waiting to lock <0x00000000e5ed5a50> (a
org.richfaces.application.push.impl.RequestImpl)
at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237)
- locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl)
at
org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88)
at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
"Atmosphere-AsyncWrite-0":
at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
- waiting to lock <0x00000000e5ed59a0> (a
org.richfaces.application.push.impl.SessionImpl)
at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107)
at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115)
at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185)
- locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl)
at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129)
- locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl)
at
org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713)
at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747)
- locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Found 1 deadlock.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:47 p.m.
[
https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-12013:
---------------------------------
Hi Stian, thanks for the report, there is really the deadlock caused by initiating
shutdown (destroying push SessionImpl) in time when session tries to post messages.
Deadlock in push component
--------------------------
Key: RF-12013
URL: https://issues.jboss.org/browse/RF-12013
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.Final
Reporter: Stian Thorgersen
Assignee: Lukáš Fryč
Deadlocked threads in the push component prevented server from stopping. Not sure whether
or not this happened when I initiated shutdown or if these where hanging around for a
while.
Relevant output from jstack:
{code}
Found one Java-level deadlock:
=============================
"push-publish-thread-1":
waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a
org.richfaces.application.push.impl.RequestImpl),
which is held by "Atmosphere-AsyncWrite-0"
"Atmosphere-AsyncWrite-0":
waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a
org.richfaces.application.push.impl.SessionImpl),
which is held by "push-publish-thread-1"
Java stack information for the threads listed above:
===================================================
"push-publish-thread-1":
at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85)
- waiting to lock <0x00000000e5ed5a50> (a
org.richfaces.application.push.impl.RequestImpl)
at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237)
- locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl)
at
org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88)
at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
"Atmosphere-AsyncWrite-0":
at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
- waiting to lock <0x00000000e5ed59a0> (a
org.richfaces.application.push.impl.SessionImpl)
at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107)
at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115)
at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185)
- locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl)
at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129)
- locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl)
at
org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713)
at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747)
- locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Found 1 deadlock.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:49 p.m.
[
https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč updated RF-12013:
----------------------------
Fix Version/s: 4.2.1.CR1
Deadlock in push component
--------------------------
Key: RF-12013
URL: https://issues.jboss.org/browse/RF-12013
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.Final
Reporter: Stian Thorgersen
Assignee: Lukáš Fryč
Fix For: 4.2.1.CR1
Deadlocked threads in the push component prevented server from stopping. Not sure whether
or not this happened when I initiated shutdown or if these where hanging around for a
while.
Relevant output from jstack:
{code}
Found one Java-level deadlock:
=============================
"push-publish-thread-1":
waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a
org.richfaces.application.push.impl.RequestImpl),
which is held by "Atmosphere-AsyncWrite-0"
"Atmosphere-AsyncWrite-0":
waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a
org.richfaces.application.push.impl.SessionImpl),
which is held by "push-publish-thread-1"
Java stack information for the threads listed above:
===================================================
"push-publish-thread-1":
at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85)
- waiting to lock <0x00000000e5ed5a50> (a
org.richfaces.application.push.impl.RequestImpl)
at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237)
- locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl)
at
org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88)
at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
"Atmosphere-AsyncWrite-0":
at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
- waiting to lock <0x00000000e5ed59a0> (a
org.richfaces.application.push.impl.SessionImpl)
at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107)
at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115)
at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185)
- locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl)
at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129)
- locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl)
at
org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713)
at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747)
- locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Found 1 deadlock.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:55 a.m.
[
https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč edited comment on RF-12013 at 3/19/12 12:54 PM:
-----------------------------------------------------------
Hi Stian, thanks for the report, there is really the race condition caused by initiating
shutdown (destroying push SessionImpl) in time when session tries to post messages.
was (Author: lfryc):
Hi Stian, thanks for the report, there is really the deadlock caused by initiating
shutdown (destroying push SessionImpl) in time when session tries to post messages.
Deadlock in push component
--------------------------
Key: RF-12013
URL: https://issues.jboss.org/browse/RF-12013
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.Final
Reporter: Stian Thorgersen
Assignee: Lukáš Fryč
Fix For: 4.2.1.CR1
Deadlocked threads in the push component prevented server from stopping. Not sure whether
or not this happened when I initiated shutdown or if these where hanging around for a
while.
Relevant output from jstack:
{code}
Found one Java-level deadlock:
=============================
"push-publish-thread-1":
waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a
org.richfaces.application.push.impl.RequestImpl),
which is held by "Atmosphere-AsyncWrite-0"
"Atmosphere-AsyncWrite-0":
waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a
org.richfaces.application.push.impl.SessionImpl),
which is held by "push-publish-thread-1"
Java stack information for the threads listed above:
===================================================
"push-publish-thread-1":
at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85)
- waiting to lock <0x00000000e5ed5a50> (a
org.richfaces.application.push.impl.RequestImpl)
at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237)
- locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl)
at
org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88)
at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
"Atmosphere-AsyncWrite-0":
at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
- waiting to lock <0x00000000e5ed59a0> (a
org.richfaces.application.push.impl.SessionImpl)
at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107)
at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115)
at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185)
- locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl)
at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129)
- locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl)
at
org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713)
at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747)
- locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Found 1 deadlock.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:09 p.m.
[
https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-12013:
---------------------------------
There are several resources which needs to be locked in {{SessionImpl}} (or maybe more):
{{boolean active}} and {{Request request}}.
On the other hand, there is only resource in {{RequestImpl}} in the race condition:
{{hasActiveBroadcaster}}.
----
I propose to use {{AtomicBoolean}} instead of synchronization to lock broadcasting process
- we will ensure that there is no race condition on {{RequestImpl}} and thus no circular
dependency.
Deadlock in push component
--------------------------
Key: RF-12013
URL: https://issues.jboss.org/browse/RF-12013
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.Final
Reporter: Stian Thorgersen
Assignee: Lukáš Fryč
Fix For: 4.2.1.CR1
Deadlocked threads in the push component prevented server from stopping. Not sure whether
or not this happened when I initiated shutdown or if these where hanging around for a
while.
Relevant output from jstack:
{code}
Found one Java-level deadlock:
=============================
"push-publish-thread-1":
waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a
org.richfaces.application.push.impl.RequestImpl),
which is held by "Atmosphere-AsyncWrite-0"
"Atmosphere-AsyncWrite-0":
waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a
org.richfaces.application.push.impl.SessionImpl),
which is held by "push-publish-thread-1"
Java stack information for the threads listed above:
===================================================
"push-publish-thread-1":
at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85)
- waiting to lock <0x00000000e5ed5a50> (a
org.richfaces.application.push.impl.RequestImpl)
at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237)
- locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl)
at
org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88)
at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
"Atmosphere-AsyncWrite-0":
at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
- waiting to lock <0x00000000e5ed59a0> (a
org.richfaces.application.push.impl.SessionImpl)
at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107)
at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115)
at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185)
- locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl)
at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129)
- locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl)
at
org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713)
at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747)
- locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Found 1 deadlock.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:28 p.m.
[
https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč edited comment on RF-12013 at 3/19/12 1:28 PM:
----------------------------------------------------------
Sent pull request and tested on Showcase.
Stian, it would be great if you could grab the source and build {{richfaces-core-impl}}
and try in your project.
Let me know if you would like to test that and I could offer you any assistance.
was (Author: lfryc):
Sent pull request and tested on Showcase.
Stian, it would be great if you could grab the source and build {{richfaces-core-impl}}
and try in your project.
Deadlock in push component
--------------------------
Key: RF-12013
URL: https://issues.jboss.org/browse/RF-12013
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.Final
Reporter: Stian Thorgersen
Assignee: Lukáš Fryč
Fix For: 4.2.1.CR1
Deadlocked threads in the push component prevented server from stopping. Not sure whether
or not this happened when I initiated shutdown or if these where hanging around for a
while.
Relevant output from jstack:
{code}
Found one Java-level deadlock:
=============================
"push-publish-thread-1":
waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a
org.richfaces.application.push.impl.RequestImpl),
which is held by "Atmosphere-AsyncWrite-0"
"Atmosphere-AsyncWrite-0":
waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a
org.richfaces.application.push.impl.SessionImpl),
which is held by "push-publish-thread-1"
Java stack information for the threads listed above:
===================================================
"push-publish-thread-1":
at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85)
- waiting to lock <0x00000000e5ed5a50> (a
org.richfaces.application.push.impl.RequestImpl)
at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237)
- locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl)
at
org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88)
at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
"Atmosphere-AsyncWrite-0":
at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
- waiting to lock <0x00000000e5ed59a0> (a
org.richfaces.application.push.impl.SessionImpl)
at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107)
at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115)
at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185)
- locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl)
at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129)
- locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl)
at
org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713)
at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747)
- locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Found 1 deadlock.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:28 p.m.
[
https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-12013:
---------------------------------
Sent pull request and tested on Showcase.
Stian, it would be great if you could grab the source and build {{richfaces-core-impl}}
and try in your project.
Deadlock in push component
--------------------------
Key: RF-12013
URL: https://issues.jboss.org/browse/RF-12013
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.Final
Reporter: Stian Thorgersen
Assignee: Lukáš Fryč
Fix For: 4.2.1.CR1
Deadlocked threads in the push component prevented server from stopping. Not sure whether
or not this happened when I initiated shutdown or if these where hanging around for a
while.
Relevant output from jstack:
{code}
Found one Java-level deadlock:
=============================
"push-publish-thread-1":
waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a
org.richfaces.application.push.impl.RequestImpl),
which is held by "Atmosphere-AsyncWrite-0"
"Atmosphere-AsyncWrite-0":
waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a
org.richfaces.application.push.impl.SessionImpl),
which is held by "push-publish-thread-1"
Java stack information for the threads listed above:
===================================================
"push-publish-thread-1":
at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85)
- waiting to lock <0x00000000e5ed5a50> (a
org.richfaces.application.push.impl.RequestImpl)
at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237)
- locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl)
at
org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88)
at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
"Atmosphere-AsyncWrite-0":
at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
- waiting to lock <0x00000000e5ed59a0> (a
org.richfaces.application.push.impl.SessionImpl)
at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107)
at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115)
at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185)
- locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl)
at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129)
- locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl)
at
org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713)
at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747)
- locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Found 1 deadlock.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:53 p.m.
[
https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč updated RF-12013:
----------------------------
Fix Version/s: 4.3.0.Milestone1
(was: 4.2.1.CR1)
Git Pull Request: https://github.com/richfaces/core/pull/8 (was:
https://github.com/richfaces/core/pull/8)
Deadlock in push component
--------------------------
Key: RF-12013
URL: https://issues.jboss.org/browse/RF-12013
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.Final
Reporter: Stian Thorgersen
Assignee: Lukáš Fryč
Fix For: 4.3.0.Milestone1
Deadlocked threads in the push component prevented server from stopping. Not sure whether
or not this happened when I initiated shutdown or if these where hanging around for a
while.
Relevant output from jstack:
{code}
Found one Java-level deadlock:
=============================
"push-publish-thread-1":
waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a
org.richfaces.application.push.impl.RequestImpl),
which is held by "Atmosphere-AsyncWrite-0"
"Atmosphere-AsyncWrite-0":
waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a
org.richfaces.application.push.impl.SessionImpl),
which is held by "push-publish-thread-1"
Java stack information for the threads listed above:
===================================================
"push-publish-thread-1":
at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85)
- waiting to lock <0x00000000e5ed5a50> (a
org.richfaces.application.push.impl.RequestImpl)
at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237)
- locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl)
at
org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88)
at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
"Atmosphere-AsyncWrite-0":
at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
- waiting to lock <0x00000000e5ed59a0> (a
org.richfaces.application.push.impl.SessionImpl)
at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107)
at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115)
at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185)
- locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl)
at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129)
- locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl)
at
org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713)
at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747)
- locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Found 1 deadlock.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:25 a.m.
[
https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.s...
]
Stian Thorgersen commented on RF-12013:
---------------------------------------
I'm happy to do that, trying out the instructions on
https://community.jboss.org/wiki/HowToBuildRichFaces4x at the moment. I'll let you
know how I get on, although the problem only happens infrequently so would be hard to
guarantee its actually fixed
Deadlock in push component
--------------------------
Key: RF-12013
URL: https://issues.jboss.org/browse/RF-12013
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.Final
Reporter: Stian Thorgersen
Assignee: Lukáš Fryč
Fix For: 4.3.0.Milestone1
Deadlocked threads in the push component prevented server from stopping. Not sure whether
or not this happened when I initiated shutdown or if these where hanging around for a
while.
Relevant output from jstack:
{code}
Found one Java-level deadlock:
=============================
"push-publish-thread-1":
waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a
org.richfaces.application.push.impl.RequestImpl),
which is held by "Atmosphere-AsyncWrite-0"
"Atmosphere-AsyncWrite-0":
waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a
org.richfaces.application.push.impl.SessionImpl),
which is held by "push-publish-thread-1"
Java stack information for the threads listed above:
===================================================
"push-publish-thread-1":
at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85)
- waiting to lock <0x00000000e5ed5a50> (a
org.richfaces.application.push.impl.RequestImpl)
at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237)
- locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl)
at
org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88)
at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
"Atmosphere-AsyncWrite-0":
at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
- waiting to lock <0x00000000e5ed59a0> (a
org.richfaces.application.push.impl.SessionImpl)
at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107)
at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115)
at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185)
- locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl)
at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129)
- locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl)
at
org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713)
at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747)
- locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Found 1 deadlock.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:50 a.m.
[
https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-12013:
-------------------------------
Fix Version/s: 4.2.1.CR1
(was: 4.3.0.Milestone1)
Git Pull Request: https://github.com/richfaces/core/pull/8 (was:
https://github.com/richfaces/core/pull/8)
Deadlock in push component
--------------------------
Key: RF-12013
URL: https://issues.jboss.org/browse/RF-12013
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.Final
Reporter: Stian Thorgersen
Assignee: Lukáš Fryč
Fix For: 4.2.1.CR1
Deadlocked threads in the push component prevented server from stopping. Not sure whether
or not this happened when I initiated shutdown or if these where hanging around for a
while.
Relevant output from jstack:
{code}
Found one Java-level deadlock:
=============================
"push-publish-thread-1":
waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a
org.richfaces.application.push.impl.RequestImpl),
which is held by "Atmosphere-AsyncWrite-0"
"Atmosphere-AsyncWrite-0":
waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a
org.richfaces.application.push.impl.SessionImpl),
which is held by "push-publish-thread-1"
Java stack information for the threads listed above:
===================================================
"push-publish-thread-1":
at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85)
- waiting to lock <0x00000000e5ed5a50> (a
org.richfaces.application.push.impl.RequestImpl)
at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237)
- locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl)
at
org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88)
at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
"Atmosphere-AsyncWrite-0":
at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
- waiting to lock <0x00000000e5ed59a0> (a
org.richfaces.application.push.impl.SessionImpl)
at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107)
at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115)
at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185)
- locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl)
at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129)
- locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl)
at
org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713)
at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747)
- locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Found 1 deadlock.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:42 a.m.
[
https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.s...
]
Stian Thorgersen commented on RF-12013:
---------------------------------------
Tried to get the problem to happen, but no luck. So can't actually test the fix
properly.
Deadlock in push component
--------------------------
Key: RF-12013
URL: https://issues.jboss.org/browse/RF-12013
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.Final
Reporter: Stian Thorgersen
Assignee: Lukáš Fryč
Fix For: 4.2.1.CR1
Deadlocked threads in the push component prevented server from stopping. Not sure whether
or not this happened when I initiated shutdown or if these where hanging around for a
while.
Relevant output from jstack:
{code}
Found one Java-level deadlock:
=============================
"push-publish-thread-1":
waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a
org.richfaces.application.push.impl.RequestImpl),
which is held by "Atmosphere-AsyncWrite-0"
"Atmosphere-AsyncWrite-0":
waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a
org.richfaces.application.push.impl.SessionImpl),
which is held by "push-publish-thread-1"
Java stack information for the threads listed above:
===================================================
"push-publish-thread-1":
at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85)
- waiting to lock <0x00000000e5ed5a50> (a
org.richfaces.application.push.impl.RequestImpl)
at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237)
- locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl)
at
org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88)
at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
"Atmosphere-AsyncWrite-0":
at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
- waiting to lock <0x00000000e5ed59a0> (a
org.richfaces.application.push.impl.SessionImpl)
at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107)
at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115)
at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185)
- locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl)
at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129)
- locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl)
at
org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713)
at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747)
- locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Found 1 deadlock.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:39 p.m.
[
https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-12013:
---------------------------------
Thanks for trying, Stian, I'm pretty sure it's hard to reproduce it.
Otherwise Push works as expected?
Deadlock in push component
--------------------------
Key: RF-12013
URL: https://issues.jboss.org/browse/RF-12013
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.Final
Reporter: Stian Thorgersen
Assignee: Lukáš Fryč
Fix For: 4.2.1.CR1
Deadlocked threads in the push component prevented server from stopping. Not sure whether
or not this happened when I initiated shutdown or if these where hanging around for a
while.
Relevant output from jstack:
{code}
Found one Java-level deadlock:
=============================
"push-publish-thread-1":
waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a
org.richfaces.application.push.impl.RequestImpl),
which is held by "Atmosphere-AsyncWrite-0"
"Atmosphere-AsyncWrite-0":
waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a
org.richfaces.application.push.impl.SessionImpl),
which is held by "push-publish-thread-1"
Java stack information for the threads listed above:
===================================================
"push-publish-thread-1":
at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85)
- waiting to lock <0x00000000e5ed5a50> (a
org.richfaces.application.push.impl.RequestImpl)
at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237)
- locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl)
at
org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88)
at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
"Atmosphere-AsyncWrite-0":
at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
- waiting to lock <0x00000000e5ed59a0> (a
org.richfaces.application.push.impl.SessionImpl)
at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107)
at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115)
at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185)
- locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl)
at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129)
- locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl)
at
org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713)
at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747)
- locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Found 1 deadlock.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:02 p.m.
[
https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.s...
]
Stian Thorgersen commented on RF-12013:
---------------------------------------
Thanks for the fix, I've built it from GIT and will use that on my dev box.
Other than this issue, the push component is mostly working, except for another issue
I've recently discovered. I'm loosing events if they are fired between the model
is updated and the page is viewed. See https://issues.jboss.org/browse/RF-12072. I'm
currently using TopicsContext to publish messages, I tried to use CDI events to see if
that made any difference but got an exception with "Service Tracker has not been
initialized".
Deadlock in push component
--------------------------
Key: RF-12013
URL: https://issues.jboss.org/browse/RF-12013
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.Final
Reporter: Stian Thorgersen
Assignee: Lukáš Fryč
Fix For: 4.2.1.CR1
Deadlocked threads in the push component prevented server from stopping. Not sure whether
or not this happened when I initiated shutdown or if these where hanging around for a
while.
Relevant output from jstack:
{code}
Found one Java-level deadlock:
=============================
"push-publish-thread-1":
waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a
org.richfaces.application.push.impl.RequestImpl),
which is held by "Atmosphere-AsyncWrite-0"
"Atmosphere-AsyncWrite-0":
waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a
org.richfaces.application.push.impl.SessionImpl),
which is held by "push-publish-thread-1"
Java stack information for the threads listed above:
===================================================
"push-publish-thread-1":
at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85)
- waiting to lock <0x00000000e5ed5a50> (a
org.richfaces.application.push.impl.RequestImpl)
at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237)
- locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl)
at
org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88)
at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
"Atmosphere-AsyncWrite-0":
at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
- waiting to lock <0x00000000e5ed59a0> (a
org.richfaces.application.push.impl.SessionImpl)
at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107)
at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115)
at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185)
- locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl)
at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129)
- locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl)
at
org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713)
at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747)
- locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Found 1 deadlock.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:13 a.m.
[
https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-12013:
---------------------------------
Hey Stian, thanks for your efforts.
I'm looking into RF-12072 now.
Just for clarity, RF-12072 appeared with this patch or have you experienced it before?
Just note that CDI events just delegates to TopicsContext, so {{Service Tracker has not
been initialized}} issue won't disappear.
I would recommend you
readinghttp://rik-ansikter.blogspot.com/2012/02/configuring-richfaces-pus...
and the troubleshooting section linked there.
Deadlock in push component
--------------------------
Key: RF-12013
URL: https://issues.jboss.org/browse/RF-12013
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.Final
Reporter: Stian Thorgersen
Assignee: Lukáš Fryč
Fix For: 4.2.1.CR1
Deadlocked threads in the push component prevented server from stopping. Not sure whether
or not this happened when I initiated shutdown or if these where hanging around for a
while.
Relevant output from jstack:
{code}
Found one Java-level deadlock:
=============================
"push-publish-thread-1":
waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a
org.richfaces.application.push.impl.RequestImpl),
which is held by "Atmosphere-AsyncWrite-0"
"Atmosphere-AsyncWrite-0":
waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a
org.richfaces.application.push.impl.SessionImpl),
which is held by "push-publish-thread-1"
Java stack information for the threads listed above:
===================================================
"push-publish-thread-1":
at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85)
- waiting to lock <0x00000000e5ed5a50> (a
org.richfaces.application.push.impl.RequestImpl)
at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237)
- locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl)
at
org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88)
at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
"Atmosphere-AsyncWrite-0":
at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
- waiting to lock <0x00000000e5ed59a0> (a
org.richfaces.application.push.impl.SessionImpl)
at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107)
at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115)
at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185)
- locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl)
at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129)
- locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl)
at
org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713)
at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747)
- locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Found 1 deadlock.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:54 a.m.
[
https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-12013:
---------------------------------
Merged to {{release/4.2.1.CR1}}.
Deadlock in push component
--------------------------
Key: RF-12013
URL: https://issues.jboss.org/browse/RF-12013
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.Final
Reporter: Stian Thorgersen
Assignee: Lukáš Fryč
Fix For: 4.2.1.CR1
Deadlocked threads in the push component prevented server from stopping. Not sure whether
or not this happened when I initiated shutdown or if these where hanging around for a
while.
Relevant output from jstack:
{code}
Found one Java-level deadlock:
=============================
"push-publish-thread-1":
waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a
org.richfaces.application.push.impl.RequestImpl),
which is held by "Atmosphere-AsyncWrite-0"
"Atmosphere-AsyncWrite-0":
waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a
org.richfaces.application.push.impl.SessionImpl),
which is held by "push-publish-thread-1"
Java stack information for the threads listed above:
===================================================
"push-publish-thread-1":
at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85)
- waiting to lock <0x00000000e5ed5a50> (a
org.richfaces.application.push.impl.RequestImpl)
at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237)
- locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl)
at
org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88)
at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
"Atmosphere-AsyncWrite-0":
at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
- waiting to lock <0x00000000e5ed59a0> (a
org.richfaces.application.push.impl.SessionImpl)
at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107)
at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115)
at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185)
- locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl)
at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129)
- locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl)
at
org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713)
at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747)
- locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Found 1 deadlock.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:54 a.m.
[
https://issues.jboss.org/browse/RF-12013?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč edited comment on RF-12013 at 3/23/12 6:54 AM:
----------------------------------------------------------
Hey Stian, thanks for your efforts.
I'm looking into RF-12072 now.
Just for clarity, RF-12072 appeared with this patch or have you experienced it before?
Just note that CDI events just delegates to TopicsContext, so {{Service Tracker has not
been initialized}} issue won't disappear.
I would recommend you reading
http://rik-ansikter.blogspot.com/2012/02/configuring-richfaces-push-with-... and the
troubleshooting section linked there.
was (Author: lfryc):
Hey Stian, thanks for your efforts.
I'm looking into RF-12072 now.
Just for clarity, RF-12072 appeared with this patch or have you experienced it before?
Just note that CDI events just delegates to TopicsContext, so {{Service Tracker has not
been initialized}} issue won't disappear.
I would recommend you
readinghttp://rik-ansikter.blogspot.com/2012/02/configuring-richfaces-pus...
and the troubleshooting section linked there.
Deadlock in push component
--------------------------
Key: RF-12013
URL: https://issues.jboss.org/browse/RF-12013
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.Final
Reporter: Stian Thorgersen
Assignee: Lukáš Fryč
Fix For: 4.2.1.CR1
Deadlocked threads in the push component prevented server from stopping. Not sure whether
or not this happened when I initiated shutdown or if these where hanging around for a
while.
Relevant output from jstack:
{code}
Found one Java-level deadlock:
=============================
"push-publish-thread-1":
waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a
org.richfaces.application.push.impl.RequestImpl),
which is held by "Atmosphere-AsyncWrite-0"
"Atmosphere-AsyncWrite-0":
waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a
org.richfaces.application.push.impl.SessionImpl),
which is held by "push-publish-thread-1"
Java stack information for the threads listed above:
===================================================
"push-publish-thread-1":
at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85)
- waiting to lock <0x00000000e5ed5a50> (a
org.richfaces.application.push.impl.RequestImpl)
at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237)
- locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl)
at
org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88)
at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
"Atmosphere-AsyncWrite-0":
at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
- waiting to lock <0x00000000e5ed59a0> (a
org.richfaces.application.push.impl.SessionImpl)
at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107)
at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115)
at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185)
- locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl)
at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129)
- locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl)
at
org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608)
at
org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713)
at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747)
- locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Found 1 deadlock.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5092
days inactive
5116
days old
richfaces-issues@lists.jboss.org
17 comments
3 participants
participants (3)
-
Brian Leathem (JIRA) -
Lukáš Fryč (JIRA)
-
Stian Thorgersen (JIRA)