RE: [flexcoders] Re: No debugging information available for invocation of methods on server-side

[Peter Farland]

Note that the reason why the Throwable class info "NullPointerException" wasn't included in the status info "type" property is because of a default setting on the AMF Gateway. Internal class information is not included in the form of stack traces or exception types as they shouldn't be exposed in a production environment.   To get the AMF Gateway to return exception class names you can turn on the show-stacktraces option in the /WEB-INF/flex/gateway-config.xml file.   From: Dan Tropp [mailto:[EMAIL PROTECTED] Sent: Monday, April 11, 2005 2:22 AM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Re: No debugging information available for invocation of methods on server-side Hi Andrew, {Tomcat_home}/logs/stdout.log is the only file that gets anything and it is minimal.  I don't seem to have a catalina.out, but perhaps this is stdout.log under Tomcat 5.0? Thanks for the reminder about the net debugger.  I picks up my calls but the information is limited. For example, when my java method threw a NullPointerException the NetDebugger gave me the following fairly cryptic message... DebugId: 0 EventType: "Status" MovieUrl: "http://localhost:8080/ge-flex/eMotor.mxml.swf" Protocol: "http" Source: "Client" Time: 1113200308656 Date (object #1) ....."Mon Apr 11 16:18:28 GMT+1000 2005" Status (object #2) .....code: "Server.Processing" .....description: (undefined) .....details: "" .....level: "error" .....type: "" .....rootcause (object #3) ..........code: (undefined) ..........description: (undefined) ..........details: "" ..........level: "error" ..........type: "" Have you got an example of debug output from remote calls from your logs? I'm interested what it looks like. cheers Dan Andrew Spaulding wrote: Hey Dan, have you tried looking at catalina.out? Also if you have turned on all of the debugging on the flex-config how about running the NetConnectionDebugger ? It will help monitor all remoteObject calls and the result/fault returns from your java backend. You can find it in your flex install directory /extras/netConnectionDebugger/ Andrew btw I use Flex 1.5, Tomcat 4.1.30, Windows XP --- In flexcoders@yahoogroups.com, Dan Tropp <[EMAIL PROTECTED]> wrote: > This is getting really frustrating.  I have turned all the debug flags > to true in the flex-config.xml file and the logging level to debug, and > I still get nothing! > > I can't locate any flashlog.txt (or similar) on the client and no debug > information is appearing in my WEB-INF/flex/logs/flex.log or in my > Tomcat server logs.  Have I missed some simple setting? > > I also installed the Debug Flash Player, but the Debugger option from > the context menu is always greyed out. > > What debugging information do people work with? > > Many thanks, > > Dan > (Tomcat5, Flex1.5, Windows XP) > > PS It has taken me a couple of hours to realise my server-side Java > method was throwing a Null Pointer exception.  The only information I > was getting was "Error: An error occurred during service invocation" in > my Tomcat log.  Urgh! Yahoo! Groups Links To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/   To unsubscribe from this group, send an email to: [EMAIL PROTECTED]   Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.