History | Log In     View a printable version of the current page.  
Issue Details (XML)

Key: BLZ-239
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Assignee: aglosban
Reporter: aglosban
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
BlazeDS

Checkintests failing on BlazeDS/trunk.

Created: 08/29/08 09:03 AM   Updated: 10/08/08 08:05 AM
Component/s: Messaging
Security Level: Public (All JIRA Users )

Issue Links:
Relationship
This issue relates to:
SDK-16659 Trying to send a message over a bad H... None Closed
 

Severity: Incorrectly Functioning
Reproducibility: Every Time
Discoverability: High
Found in Version: BlazeDS 4
Milestone: BlazeDS 4
Affected OS(s): All OS Platforms
Steps to Reproduce:
Steps to reproduce:
1. On BlazeDS/trunk run "ant checkintests".
2.
3.
 
 Actual Results: The developer messaging tests are throwing a RTE which is causing the test results to not get reported. The actual test that is throwing the RTE is the testSendWithHunting test method in the flexunit test mx.messaing.tests.ChannelSetTest.

Here is the RTE.

[MessagingError message='Invalid AMFX packet. Content must start with an <amfx> node']
at mx.messaging.channels.amfx::AMFXDecoder$/decodePacket()[E:\dev\trunk\frameworks\projects\rpc\src\mx\messaging\channels\amfx\AMFXDecoder.as:149]
at mx.messaging.channels.amfx::AMFXDecoder/decode()[E:\dev\trunk\frameworks\projects\rpc\src\mx\messaging\channels\amfx\AMFXDecoder.as:91]
at mx.messaging.channels::HTTPChannel/decodePacket()[E:\dev\trunk\frameworks\projects\rpc\src\mx\messaging\channels\HTTPChannel.as:559]
at mx.messaging.channels::HTTPChannel/pingCompleteHandler()[E:\dev\trunk\frameworks\projects\rpc\src\mx\messaging\channels\HTTPChannel.as:597]
at ChannelRequestLoader/callEventCallback()[E:\dev\trunk\frameworks\projects\rpc\src\mx\messaging\channels\HTTPChannel.as:1159]
at ChannelRequestLoader/completeHandler()[E:\dev\trunk\frameworks\projects\rpc\src\mx\messaging\channels\HTTPChannel.as:1195]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at flash.net::URLLoader/onComplete()

 
 
 Expected Results: The test shouldn't be throwing an RTE. The RTE is being caused by the following SDK bug which I logged: https://bugs.adobe.com/jira/browse/SDK-16659.
 
 
 Workaround (if any):
 
 
 
Language Found: English
Bugbase Id: none
Triaged: Yes
Regression: Yes
QA Owner: aglosban
Resolved by: aglosban
Participants: aglosban
JDK: Sun JDK 5
Application Server: Apache Tomcat 6.x


 All   Comments      Sort Order:
aglosban - [08/29/08 09:12 AM ]
A couple of the messaging_unit flexunit tests that are part of the checkintests are failing on blazeds/trunk. I think these are due to problems in Flex SDK 4. These failures don't show up when the tests are built with the target player version set to player 9. I recently switched the target player version to 10 and started seeing these failures. Even if rpc.swc is built with the target player version set to 9, I think we should still be testing with our test apps compiled for player 10 otherwise we might miss some bugs in Flex SDK 4 especially bugs that may have been introduced by the recent Marshall plan work. I think someone in Dev should look into these failures and see if there any more issues that can be logged against the SDK besides the issue I already logged.

aglosban - [10/08/08 08:05 AM ]
These failures were due to a bug in player 10 that has been fixed. I verified that checkintests ran successfully using build 3519.