[#BLZ-292] Data Push sample does not work in BlazeDS Turnkey

BlazeDS

Data Push sample does not work in BlazeDS Turnkey

Created: 12/15/08 09:03 AM Updated: 04/20/09 12:54 PM

Component/s:

Channels: Streaming AMF

Security Level:

Public (All JIRA Users )

Severity:	Non Functioning
Reproducibility:	Every Time
Discoverability:	High
Found in Version:	BlazeDS 3.2.0
Milestone:	BlazeDS 4 Alpha 2
Affected OS(s):	Windows - Vista
Steps to Reproduce:	« Hide Steps to reproduce: 1. Download BalzeDS Turnkey 3.2.0.3978 2. Start the tomcat (startup.bat) 3. Try Data Push sample (Sample 6) from the 30 minutes Test Drive Actual Results: The feed started (Random numbers in Tomcat window) All attempts to subscribe failed. Expected Results: Subscription succseeded and the numbers appear on the form. Workaround (if any): No Couple more details: 1. I am using Windows Vista Home Premium SP1, Java 1.6.0_03-b05 2. This does not work in IE7 but works OK in Firefox3 3. This works OK in 3.0 and 3.0.1 BlazeDS releases using IE7 Show » Steps to reproduce: 1. Download BalzeDS Turnkey 3.2.0.3978 2. Start the tomcat (startup.bat) 3. Try Data Push sample (Sample 6) from the 30 minutes Test Drive Actual Results: The feed started (Random numbers in Tomcat window) All attempts to subscribe failed. Expected Results: Subscription succseeded and the numbers appear on the form. Workaround (if any): No Couple more details: 1. I am using Windows Vista Home Premium SP1, Java 1.6.0_03-b05 2. This does not work in IE7 but works OK in Firefox3 3. This works OK in 3.0 and 3.0.1 BlazeDS releases using IE7
Language Found:	English
Bugbase Id:	none
Triaged:	Yes
Regression:	Yes
QA Owner:	Ken Smith
Resolved by:	Seth Hodgson
Participants:	aglosban, Boris Rekhtman, Ken Smith and Seth Hodgson
Browser:	Internet Explorer 7.x
JDK:	Sun JDK 6
Application Server:	Apache Tomcat 6.x

All

Comments

Sort Order:

[ Permlink | « Hide ]

Ken Smith - [12/16/08 10:24 AM ]

Reproduced issue. Issue occurs using 1.5.0_17 JVM, although may be more pronounced with 1.6.X JVM. I reproduced also using 1.6.011 JVM. Issue seems to be with streamingAMF channel. Issue reproduces on IE6 and IE7. The testdrive datapush sample as user stated. It also occurs with Trader Desktop example if channel is set to streaming AMF.

Intermittantly the data is updated in either sample, but it occurs very slowly. Most messages are dropped, if any at all get picked up. I see no error when debugging in Charles.

[ Permlink | « Hide ]

aglosban - [12/16/08 11:55 AM ]

Streaming endpoints aren't working if the channel in services-config.xml doesn't have the max-streaming-clients property defined. When max-streaming-clients isn't defined, it should default to 10 but doesn't look like this is working.

To reproduce, remove the max-streaming-clients setting from the qa-streaming-amf channel in the services-config.xml file for the qa-regress webapp. Then restart the server and run the following test: http://localhost:8400/qa-regress/testsuites/mxunit/tests/messagingService/simpleMessagingTest.mxml

The test over the streaming amf channel is timing out. If you add the max-streaming-clients setting back in and rerun the test it passes.

Not calling this a regression as it's broken in BlazeDS 3.2 and on trunk. Not sure if it was always broken. As soon as this is fixed, I'll remove the max-streaming-clients setting from the qa-streaming-amf channel in qa-regress so the regressions will cover this scenario.

[ Permlink | « Hide ]

aglosban - [12/16/08 12:25 PM ]

Changing this to a regression. I verified that the streaming channel works without the max-streaming-clients setting in 3.0.1.1755.

[ Permlink | « Hide ]

Seth Hodgson - [12/22/08 06:17 PM ]

Regression due to some refactoring of user-agent handling that was failing to set up defaults if no explicit <properties> were defined for the <channel-definition>. This meant that for IE, no kick-start bytes were being pushed down the streaming connection at setup time...

Fixed in trunk revision 4377.

[ Permlink | « Hide ]

Ken Smith - [12/23/08 03:24 PM ]

Please run against your testcase, confirm and close.

[ Permlink | « Hide ]

aglosban - [01/08/09 01:01 PM ]

Closing. Verified in BlazeDS build 4422. Changed qa-streaming-amf channel in qa-regress so that the automated tests will now cover this. See checkin 4444.

[ Permlink | « Hide ]

Seth Hodgson - [04/20/09 12:54 PM ]

Merged fix over to branches/3.x in revision 6166.