Bug 1002971 - a4j:push is not working in Showcase
Summary: a4j:push is not working in Showcase
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: PortletBridge
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DR01
: 6.1.1
Assignee: Nobody
QA Contact: Tomas Kyjovsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-30 11:44 UTC by Petr Mensik
Modified: 2021-10-23 04:23 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
Atmosphere, the push library used by a4j:push, was attempting to use a WebSocket class that is no longer compatible with Red Hat JBoss Enterprise Application Platform. This caused a4j:push to throw server exceptions instead of producing a valid result. To work around the issue, disable WebSocket support in Atmosphere with the web.xml context-param directive: [source,XML] ---- <context-param> <param-name>org.atmosphere.useWebSocket</param-name> <param-value>false</param-value> </context-param> ----
Clone Of:
Environment:
Last Closed:
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RF-13154 0 Major Resolved Upgrade Atmosphere to 1.0.17 (a4j:push fails with CNFE for org.apache.coyote.http11.upgrade.UpgradeInbound on latest EAP... 2014-08-22 09:07:59 UTC

Description Petr Mensik 2013-08-30 11:44:54 UTC 
Both Topics Context Usage and CDI push doesn't work, however no exceptions are thrown and server log is empty.

Comment from Ken Finnigan

This is now a different issue.

It appears the classpath/modules available between EAP 6.1.0 and latest EAP 6.1.1 have changed, causing a ClassNotFoundException when running the a4j:push example of the showcase.

In JPP, failed network requests can be seen in the developer console of the browser. Attempting to issue one of those failed requests directly in the browser shows the ClassNotFoundException.

Issue has been raised with RichFaces: https://issues.jboss.org/browse/RF-13154.
Comment 2 Ken Finnigan 2013-11-07 15:16:14 UTC 
Resolved with upgrade to RichFaces 4.3.4.Final
Comment 3 Petr Mensik 2013-12-17 13:31:20 UTC 
Verified it's working with the upgraded version.
Note You need to log in before you can comment on or make changes to this bug.