Hi Sean, Thx for the suggestions. I believe that I am kind of have an idea on what causing the issue of this transaction to suddently stop working. Since I thought it might be 1.5.1 SDK issue, so I build it using 1.5.2 SDK but the result is the same. All I can tell right now is this issue seems to only appear on Windows but not on Mac. Both have AIR runtime version 1.5.2.
So be warn for those of you who are using transaction heavily (my app needs to do at least lots of transaction where each transaction process 10 - 200 inserts). I am still building this app through FlexBuilder. Will migrate to Ant pretty soon. --- In [email protected], "seanmcmonahan" <s...@...> wrote: > > I can recommend three things as I've been doing a fair amount of debugging > lately: > > 1) Check out MonsterDebugger for debugging from your release build > > 2) Try opening your SQLConnection before calling begin(). I think begin > opens a connection but I'm not entirely sure. Also try adding an event > listener for the open event to ensure your connection is being opened as well. > > 3) How are you building the release build? Recently I'd experienced some > issues related to an Ant build script that targeted Flash Player 10 while the > Flex Debugger targeted 9.0.28. Setting the Ant script to target 9.0.28 > cleared up my problems. Check this article for details: > http://kb2.adobe.com/cps/404/kb404341.html > > --- In [email protected], "handitan" <handitan@> wrote: > > > > Hi all, > > > > I have this weird issue that I am having. > > I am using transaction on this function call functA(). And functA() has > > been called many times, the transaction worked perfect. > > > > BUT...for a reason that I still don't know, the transaction sometimes will > > not work. > > And it seems that this phenomenon only happens on the release build because > > I couldn't reproduce it at all when I am debugging it. > > > > How do I find out that the issue was the transaction on release build? > > I log the before I call transaction begin, and its result and fault > > handler. I notice that the begin got called but it never got to neither > > result nor fault handler, which just baffled me. > > And I did make sure my transaction listener are NOT using weak references. > > > > Here's a snip of the code if you are curious: > > > > public class AsyncTransactionClass extends EventDispatcher > > { > > public function functA():void > > { > > sqlStatement = new SQLStatement; > > sqlStatement.text = "some query"; > > sqlStatement.sqlConnection = <a sql connection>; > > > > sqlStatement.sqlConnection.addEventListener(SQLEvent.BEGIN,transactionSetupResultHandler); > > > > sqlStatement.sqlConnection.addEventListener(SQLErrorEvent.ERROR,transactionSetupFaultHandler); > > > > > > sqlStatement.sqlConnection.begin(); > > } > > > > private function transactionSetupResultHandler(pEvent:SQLEvent):void > > { > > trace("I AM AT RESULT"); > > } > > > > private function transactionSetupFaultHandler(pEvent:SQLErrorEvent):void > > { > > trace("I AM AT FAULT"); > > } > > } > > > > Does anyone else have this problem? > > I am really out of ideas now on how to solve this. > > > > Thank you. > > >
