3 Replies Latest reply on Jan 11, 2013 4:45 AM by Flemming Harms

    Problem with pgpool2 degenerate one of the databases with messaging is involved

    Flemming Harms Novice

      Hi Guys


      I'm investigated a problem we have with pgpool2 degenerate one of the databases in the cluster. JBoss messaging 1.4.8-SP2 is involved in the process and actual it happen when the statement below is executed. Since messaging communicate through pgpool I do not suspect at this point it has anything to do with messaging.


      "DELETE

      FROM JBM_MSG WHERE MESSAGE_ID = $1 AND NOT EXISTS (SELECT

      JBM_MSG_REF.MESSAGE_ID FROM JBM_MSG_REF WHERE JBM_MSG_REF.MESSAGE_ID =

      $2)"


      But I got this questions from pgpool forum:


      Well there some possibilities:


      1) JBoss uses functions which has side effect(updating tables).


      2) JBoss uses triggers which updates the table in question.


      3) the transaction updating the table in question committed on node 1

         but not committed on node 0 for some reason. Maybe the connection

         between JBoss and pgpool between those two commit commands were

         disconnected?


      I have searched through the code and AFAIK messaging are not using any functions or triggers, right?


      Link pgpool post http://www.pgpool.net/pipermail/pgpool-general/2012-December/001284.html

       

      Any help will be appreciated, thanks!

       

      Cheers,

      Flemming