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

Key: SDK-13765
Type: Bug Bug
Status: Closed Closed
Priority: B B
Assignee: Trevor Baker
Reporter: Chris Stockwell
Votes: 14
Watchers: 8
Operations

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

REOPEN WebService fault details are hidden by Flex SDK

Created: 11/28/07 03:37 PM   Updated: 03/16/09 02:35 PM
Component/s: RPC: WebService
Security Level: Public (All JIRA Users )

Issue Links:
Cloners
This issue is cloned by:
SDK-19956 CLONE -REOPEN WebService fault detail... B Closed
This issue was cloned from:
SDK-11841 WebService fault details are hidden b... C Closed
Duplicate
This issue duplicates:
SDK-11841 WebService fault details are hidden b... C Closed
 

Severity: Data Loss/Corruption
Reproducibility: Every Time
Discoverability: High
Found in Version: SDK Moxie M2 (Beta) - 172402
Milestone:
Affected OS(s): Windows - XP
Steps to Reproduce:
Steps to reproduce:
1. create a soap web service (tested in .NET, but should be same regardless of back end)
2. make the service generate a soap error
3. create a WebService control to call the web service
3. view fault object in flex debugger
 
 Actual Results:
 
 Flex reports an IO error with it's own details, not the soap error

 Expected Results:
 
 The soap error should have been available as a fault in Flex.

 Workaround (if any):
 
None, you can not get fault info in Flex with Web Services.



here's an example fault captured with Charles:

<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>System.Web.Services.Protocols.SoapException: Server was unable to process request. ---&gt; System.Data.DataException: Unable to connect to Northwind database. ---&gt; System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
   at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Northwind.CreateConnection()
   --- End of inner exception stack trace ---
   at Northwind.CreateConnection()
   at Categories.FindAll(Int32 categoryId, String orderField, Boolean orderDesc)
   --- End of inner exception stack trace ---</faultstring><detail /></soap:Fault></soap:Body></soap:Envelope>



but here's the error I saw in Flex:


mx.rpc.events.FaultEvent (@e068501)
bubbles false
cancelable true
currentTarget mx.rpc.soap.WebService (@dde7d81)
eventPhase 2
fault mx.rpc.Fault (@dede421)
errorID 0
faultCode "Server.Error.Request"
faultDetail "Error: [IOErrorEvent type="ioError" bubbles=false cancelable=false eventPhase=2 text="Error #2032: Stream Error. URL: http://localhost/AspxManual/Categories.asmx"]. URL: http://localhost/AspxManual/Categories.asmx"
faultString "HTTP request error"
message "faultCode:Server.Error.Request faultString:'HTTP request error' faultDetail:'Error: [IOErrorEvent type="ioError" bubbles=false cancelable=false eventPhase=2 text="Error #2032: Stream Error. URL: http://localhost/AspxManual/Categories.asmx"]. URL: http://localhost/AspxManual/Categories.asmx'"
name "Error"
rootCause flash.events.IOErrorEvent (@dfccd29)
bubbles false
cancelable false
currentTarget flash.net.URLLoader (@e1f7241)
bytesLoaded 0
bytesTotal 0
data undefined
dataFormat "text"
eventPhase 2
target flash.net.URLLoader (@e1f7241)
text "Error #2032: Stream Error. URL: http://localhost/AspxManual/Categories.asmx"
type "ioError"
message mx.messaging.messages.ErrorMessage (@dfbce49)
messageId "F26044F3-8DFD-52C5-7D41-DF914C34D699"
target mx.rpc.soap.WebService (@dde7d81)
token mx.rpc.AsyncToken (@e0a7f41)
type "fault"

 
 
Language Found: English
Bugbase Id: none
Triaged: Yes
Regression: No
QA Owner: Trevor Baker
Participants: A Wilber, Bill Sahlas, Chris Stockwell, Dan, Matt Chotin, Tom Olsen and Trevor Baker


 All   Comments      Sort Order:
Bill Sahlas - [12/03/07 09:46 AM ]
The LCDS server is required in order to get the full error message back to the client. You'd need to setup a 'destination' and useProxy=true. The server code is able to circumvent the player limitation

Tom Olsen - [12/04/07 12:29 AM ]
Adobe's position on this issue is truly disappointing. To require that we license LCDS server, spending tens of thousands of dollars, to correct for a shortcoming of an Adobe product, whether it be Flex or the Flash Player itself, is shocking. The need for accurate error propagation can hardly be described as a feature request. It is a bug, apparently due to a design flaw, and I urge Adobe to keep this issue open for future consideration.

A Wilber - [12/04/07 12:00 PM ]
I agree with Tom (and the others that expressed this sentiment in the previously closed ticket http://bugs.adobe.com/jira/browse/SDK-11841). It's especially frustrating to just have this ticket closed again without stated recognition of the position people are taking and why Adobe feels that this position is invalid. Perhaps if people understood why Adobe felt this is not a bug... Heck, I'd even be more satisfied (if very disappointed) if the answer was "yeah it's a bug, but for now we'd like to get some revenue off of LCDS".

Matt Chotin - [02/10/08 01:59 PM ]
Closing as a duplicate. The other bug is now open.

Dan - [10/22/08 01:50 PM ]
More than a year later, and still nothing from Adobe. Are the bug owners on this one paying attention?!?!?

Just for a little reference, this bug is the reason no one uses Flash or AIR clients for Amazon Web Services, and any number of other major web services:
http://docs.amazonwebservices.com/AlexaSiteThumbnail/2006-05-15/SoapErrorResponseArticle.html

Hmm... guess we'd better have Amazon return a non-error response code... oh, wait, they are the ones that are standards compliant, and this YEAR OLD BUG is the problem.