Ok, as can be seen here, I've been having a problem with a program that I recently introduced table locking into (and have since removed thinking it may be the source of the problem, so far it doesn't look like it.) Now it seems to work only part of the time, and it fails and suceeds, aparantly, at random. I will execute it once with a certain set of operations to complete and it executes flawlessly, I execute it again with the same tasks to perform and it MIGHT work, or it might not. I've been able to hit refresh 20-30 times sometime and have it fail on 31, but it can fail anywhere from 1 to infinity as far as I can see.

I'm at a loss to even guess what the problem might be, beyond the fact that it seems to stem from the database for some reason, but the database remains accessable, I can still run identical queries from the mysql shell interface and have them function, and if I hit refresh a few dozen times without the commands, it eventually brings me back... usually, however it seems to do so without my session data (I use Apache::Session::Mysql), which furthers my suspicions about the database.

I'v been working with this database for the past several months without a problem, and aside from the brief time when I experemented with locking, nothing in it's interactions should have changed in the areas it seems to fail in... then again I have yet to find an area where it does reliably continue to work.

I have attempted, as can be seen in my previous post, which, while it did gain some reputation, failed to produce any useful assistance, to use the Apache::DB module to allow me to use a debugger on it, but I can't seem to get that working (see error messages in the referenced node.) I'm at a complete loss and under some severe time constraints to get my project complete, and I find myself unable to even debug it. Does anyone have ANY advice whatsoever?

While waiting, I'll try inserting warn statements to try to trace the problem line(s)... somehow I doubt I'll have much luck.


My code doesn't have bugs, it just develops random features.

Flame ~ Lead Programmer: GMS (DOWN) | GMS (DOWN)

In reply to mysql, locked databases, Apache::DBI and mod_perl by Flame

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.