[ https://issues.jboss.org/browse/RFPL-1607?page=com.atlassian.jira.plugin.... ] Jay Balunas updated RFPL-1607: ------------------------------ Fix Version/s: 4.1.0.Milestone3 (was: 4.1.0.Milestone2) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RFPL-1607?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-1607: -------------------------------- Assignee: Pavol Pitonak (was: Lukáš Fryč) Fix Version/s: 4.1.0.CR1 (was: 4.1.0.Tracking) Component/s: components Is this something we are already testing as part of our 4.1 release testing. -- 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

[ https://issues.jboss.org/browse/RFPL-1607?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-1607: -------------------------------- Comment: was deleted (was: Is this something we are already testing as part of our 4.1 release testing.) -- 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

[ https://issues.jboss.org/browse/RFPL-1607?page=com.atlassian.jira.plugin.... ] Pavol Pitonak updated RFPL-1607: -------------------------------- Fix Version/s: 4.Future (was: 4.1.0.Milestone4) Resolve as soon as it works on supported servers. -- 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

[ https://issues.jboss.org/browse/RFPL-1607?page=com.atlassian.jira.plugin.... ] Lukáš Fryč commented on RFPL-1607: ---------------------------------- Forum reference: https://community.jboss.org/message/753677#753677 -- 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

[ https://issues.jboss.org/browse/RFPL-1607?page=com.atlassian.jira.plugin.... ] Ján Jamrich commented on RFPL-1607: ----------------------------------- Even configuration above, still getting following exception in log and push component doesn't start receive updates: [#|2012-09-03T16:23:03.302+0200|WARNING|glassfish3.1.2|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=303;_ThreadName=Thread-2;|GRIZZLY0024: Terminate process interrupted. java.lang.InterruptedException at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1325) at java.util.concurrent.Semaphore.tryAcquire(Semaphore.java:414) at com.sun.grizzly.http.ProcessorTask.terminateProcess(ProcessorTask.java:1021) at com.sun.grizzly.arp.DefaultAsyncExecutor.finishResponse(DefaultAsyncExecutor.java:186) at com.sun.grizzly.arp.DefaultAsyncExecutor.finishExecute(DefaultAsyncExecutor.java:210) at com.sun.grizzly.arp.AsyncProcessorTask.doTask(AsyncProcessorTask.java:133) at com.sun.grizzly.comet.CometEngine.flushPostExecute(CometEngine.java:426) at com.sun.grizzly.comet.CometEngine.interrupt0(CometEngine.java:405) at com.sun.grizzly.comet.CometEngine.interrupt(CometEngine.java:383) at com.sun.grizzly.comet.CometContext.resumeCometHandler(CometContext.java:442) at org.atmosphere.container.GrizzlyCometSupport.resume(GrizzlyCometSupport.java:172) at org.atmosphere.container.GrizzlyCometSupport.action(GrizzlyCometSupport.java:184) at org.atmosphere.container.GrizzlyCometSupport.action(GrizzlyCometSupport.java:81) at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:317) at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:171) at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:811) at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:755) at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:729) at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:763) at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:793) 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) |#] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RFPL-1607?page=com.atlassian.jira.plugin.... ] Ján Jamrich edited comment on RFPL-1607 at 9/4/12 6:42 AM: ----------------------------------------------------------- Steps need to be done before deploy Metamer (from appropriate branch [1]) to glassfish: 1. create ConnectionFactory: Resources/JMS Resources/Connection Factories new one: Pool Name: ConnectionFactory JNDI Name: ConnectionFactory Resource Type: javax.jms.ConnectionFactory 2. create topics: Resources/JMS Resources/Destination Resources new one: JNDI Name: {/topic/pushJms | /topic/pushTopicsContext } Physical Destination Name: {pushJmsTopic|pushTopicsContext} Resource Type: javax.jms.Topic 3. enable Comet support on Glassfish Configurations/{default|server}-config/Network Config/Network Listeners/http-listener-{1|2} (tab HTTP): Coment support: true Configurations/{default|server}/Network Config/Network Protocols/http-listener-{1|2} (tab HTTP): Coment support: true and Websocket Support: true [1] https://github.com/richfaces/qa/tree/websocket-support-poc was (Author: jjamrich): Steps need to be done before deploy Metamer (from appropriate branch) to glassfish: 1. create ConnectionFactory: Resources/JMS Resources/Connection Factories new one: Pool Name: ConnectionFactory JNDI Name: ConnectionFactory Resource Type: javax.jms.ConnectionFactory 2. create topics: Resources/JMS Resources/Destination Resources new one: JNDI Name: /topic/pushJms Physical Destination Name: pushJmsTopic Resource Type: javax.jms.Topic 3. enable Comet support on Glassfish Configurations/{default|server}-config/Network Config/Network Listeners/http-listener-{1|2} (tab HTTP): Coment support: true Configurations/{default|server}/Network Config/Network Protocols/http-listener-{1|2} (tab HTTP): Coment support: true and Websocket Support: true -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RFPL-1607?page=com.atlassian.jira.plugin.... ] Lukáš Fryč updated RFPL-1607: ----------------------------- Component/s: QE (was: CDK) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira