perlquestion punkish I asked this question on the dbi list (no response yet), so am posting it here for collective wisdom of the monks. I have three MySQL/Perl Dancer [http://perldancer.org] powered web apps. The user goes to app A which serves up a Google maps base layer. On document ready, app A makes three jQuery ajax calls -- two to app B like so <code> http://app_B/points.json http://app_B/polys.json </code> and one to app C <code> http://app_C/polys.json </code> Apps B and C query the MySQL database via DBI, and serve up json packets of points and polys that are rendered in the user's browser. All three apps are proxies through Apache to Perl Starman running via plackup started like so <code> $ plackup -E production -s Starman -w 10 -p <port> path/to/respective/app.pl </code> From time to time, I start getting errors back from the apps called via Ajax. The initial symptoms were <code> {"error":"Warning caught during route execution: DBD::mysql::st fetchall_arrayref failed: fetch() without execute() at <path/to/app.pm> line 79.\n"} </code> The offending lines are <code> 71> my $sql = qq{ 72> .. 73> 74> 75> }; 76> 77> my $sth = $dbh->prepare($sql); 78> $sth->execute(); 79> my $res = $sth->fetchall_arrayref({}); </code> This is bizarre... how can execute() not take place above? Perl doesn't have a habit of jumping over lines, does it? So, I turned on DBI_TRACE <code> $DBI_TRACE=2=logs/dbi.log plackup -E production -p 5001 -s Starman -w 10 -a bin/app.pl </code> And, following is what stood out to me as the potential culprit in the log file <code> > Handle is not in asynchronous mode error 2000 recorded: Handle is > not in asynchronous mode > !! ERROR: 2000 CLEARED by call to fetch method </code> What is going on? Basically, as is, app A is non-functional because the other apps don't return data "reliably" -- I put that in quotes because they do work correctly occasionally, so I know I don't have any logic or syntax errors in my code. I have some kind of intrinsic plumbing errors. quick update: I did find the following [http://search.cpan.org/~capttofu/DBD-mysql-4.019/lib/DBD/mysql.pm#ASYNCHRONOUS_QUERIES] and am wondering if this is the cause and the solution of my problem. Would a DBI/mysql savvy monk kindly elucidate?  <div class="pmsig"><div class="pmsig-231169"> when small people start casting long shadows, it is time to go to bed </div></div>