The NetConnection Debugger can display information about a variety of events, and you can select which types to display. The following sections describe the event types and the information that the event messages for different types provide.
The NetConnection Debugger displays information about events belonging to three categories of event: client, app_server, and flashcomm_server, and each category has one or more specific event types. You can enable or disable all events in a category, or specific event types.
Note: The Network Connection Debugger Filters panel provides the best method to select which events to display. However, you can use ActionScript to enable or disable specific event types for individual NetConnection objects. For more information on using ActionScript to enable or disable event information, see "Configuring debugger output in ActionScript".
The following table lists types of events that the NetConnection Debugger displays:
| Event type |
Description |
|---|---|
| client (default = true) |
Activity information sent from the client. For detailed information on client debug events, see "client event messages". You can selectively enable and disable the following subcategories of client events. |
trace |
Client NetConnection trace events. If client trace reporting is enabled, the NetConnection Debugger displays the output of NetConnection.trace and NetDebug.trace methods. |
http |
Client NetConnection events that communicate with the remote source using HTTP. These events include connecting to the server, and Flash Remoting service calls and result returns. |
recordset |
Events associated with the delivery of pageable record set data to the client. These events occur only if the record set is pageable. |
rtmp |
Client NetConnection events that communicate with the remote server using Real-Time Messaging Protocol (RTMP). Communication with the Flash Communication Server uses RTMP. Flash Remoting MX does not use RTMP. |
| app_server (default = true) |
Information about events on the application server. This category includes activities reported by the server itself and Flash Remoting gateway activities. For detailed information on server debug events, see "app_server event messages". You can selectively enable and disable the following subcategories of app_server events. |
trace |
Server trace events. Not currently used. |
error |
Server error events. These include any errors generated during the execution of the Flash Remoting gateway or adapters. |
httpheaders |
Server HTTP header events. When enabled, the NetConnection Debugger reports a server HTTP header event for each HTTP request. |
amfheaders |
Action message Format (AMF) header events. When enabled, the NetConnection Debugger reports a server AMF request header event and a server AMF response header event for each AMF request and response. A single AMF request can include multiple service function calls. |
amf |
Server AMF events. When enabled, the NetConnection Debugger reports a server AMF method call event and a server AMF method response event for each service function call and response. |
recordset |
Events associated with the partial delivery of pageable record set data from the server. These events occur only if the record set is pageable. |
coldfusion |
ColdFusion debug events. When enabled, any debug events enabled in ColdFusion are reported to the NetConnection Debugger. If ColdFusion debugging information is not enabled in ColdFusion, a single debug error event that notifies the developer that ColdFusion debugging information has not been enabled on the server is returned per transaction. For more information on configuring debugging information in ColdFusion, see the ColdFusion documentation. |
| flashcomm_server/realtime_server (default = true) |
Information about Macromedia Flash Communication Server MX events. This option is not used for debugging Flash Remoting applications. Note: The user interface uses the term flashcomm_server. In ActionScript, you must use realtime_server. You can selectively enable and disable the following subcategory of events. |
trace |
Flash Communication Server trace events. |
The following table describes the information that the NetConnection Debugger displays for all events. Two fields, DebugID and Protocol, are not used for trace events initiated by the Netdebug.trace method
The following table describes the specific client events that the NetConnection Debugger reports, and the information it displays for each event:
| Event type |
Description |
Information fields |
|---|---|---|
| Trace |
Flash executed a NetDebug.trace or NetConnection.trace method. |
Trace The object passed to the NetDebug.trace or NetConnection.trace method. Typically a message. |
| Connect |
The Flash application requested a connection to the gateway. |
ConnectString The connection string sent to the gateway. The gateway URL. |
| AddHeader |
The Flash Remoting client added an additional header that is sent with each message to the gateway. This event occurs when you use the NetConnection. method. |
HeaderName The type of header being sent, such as Credentials. MustUnderstand A Boolean value that specifies whether the server must understand and process this header before can handle any following headers or messages. HeaderObject The object that will be sent in the added header. For example, the password and user ID. |
| Result |
Flash Remoting MX received a result message from the gateway. |
Result The object sent by the gateway in response to the request. |
| Status |
Flash Remoting MX received an error message from the gateway. |
Status An error object that describes the error. For more information about the error object, see "The error object", |
| Call |
Flash Remoting MX sent a service function call to the gateway. |
MethodName The service function being called. Parameters The arguments to the service function call. |
| Close |
Flash Remoting MX closed the connection to the gateway. Initiated by a Netconnection.close method. |
None. |
The following table describes the specific app_server events that the NetConnection Debugger reports and the information it displays for each event:
| Event type |
Description |
Information fields |
|---|---|---|
| Error |
An unhandled error occurred in the Flash Remoting gateway or adapter. These errors should not occur in normal processing. |
Data Any object associated with the error event. Normally an Exception object. Message A message that describes the error. |
| HttpRequest Header |
The gateway received an HTTP request. |
HTTPHeaders The contents of the HTTP request headers. |
| AmfRequest Header |
The gateway received an AMF request message. Each HTTP request received by the gateway includes an AMF request. |
AmfHeaders - The contents of the AMF headers. The headers include the Credentials header, if the Flash Application uses the SetCredentials method, and the amf_server_debug header, which contains the NetConnection Debugger app_server debugging settings. |
| AmfResponseHeader |
The gateway returned a response to the Flash Remoting client. This event occurs for each HTTP request. |
AmfHeaders The contents of the AMF headers sent in the response, if any. The gateway returns a header if the client does not support cookies and URL rewriting is being used for session management. |
| AmfMethod Call |
The gateway received a service function call. A single AMF request can contain multiple AMF method calls. |
MethodName The service function being called. Response URI The client-side identifier for the responder. This value is internally generated by Flash Remoting MX. Parameters The arguments passed to the service function. |
| AmfResponseCall |
The Flash gateway sent result data to the client. |
MethodName The Response URI identified by the AmfMethodCall message, followed by/onResult.Response URI Normally "(undefined)". Parameters - The data returned by the service function. |
| AmfStatusCall |
The flash gateway or application server threw an exception. |
MethodName The Response URI identified by the AmfMethodCall message, followed by/onStatus.Response URI Normally "(undefined)". Parameters An error object that describes the error. For for more information about the error object, see "The error object". |
| Information |
Server or AMF status information. |
Message A message that provides information about the status. |
If you enable debugging output in ColdFusion, the NetConnection Debugger can report a subset of the debugging information that is normally displayed by the ColdFusion server. The NetConnection Debugger can report the following ColdFusion debugging information:
cftrace tag outputcfhttp tag)Note: The NetConnection Debugger displays an information event reporting that ColdFusion debugging is not enabled on the server if debugging is enabled but no debugging information is available, for example, if an error occurs when running a CFML service function.
For more information on ColdFusion debugging information, see Developing ColdFusion MX Applications with CFML.
If you enable Flash Communication Server (flashcom_server) debugging events, the NetConnection Debugger displays an event message when the Flash Communication Server application calls a trace function. The message includes the trace call parameter and the Flash Communication Server logging API Info object for the event.
RSS feed | Send me an e-mail when comments are added to this page | Comment Report
Current page: http://livedocs.adobe.com/flashremoting/mx/Using_Flash_Remoting_MX/DebugActionScript3.htm
Comments
No screen name said on May 3, 2004 at 1:57 PM : TroyWorks said on Aug 24, 2004 at 1:42 AM :