1 2 Previous Next 17 Replies Latest reply on Jan 24, 2008 6:48 AM by lovelyliatroim Go to original post
      • 15. Re: JDBCacheLoader & hot redeploy
        lovelyliatroim

        I think i found the cause.

        On the redeploy i get 2 log statements like so


        2008-01-24 10:46:52,602 DEBUG [org.jboss.cache.loader.JDBCCacheLoader] executing ddl: drop table jbosscache^M


        and later on i get

        2008-01-24 10:47:19,415 DEBUG [org.jboss.cache.loader.JDBCCacheLoader] executing ddl: create table jbosscache(fqn varchar(255) not null, node blob, parent varchar(255), constraint jbosscache_pk primary key (fqn))^


        So this would explain why the DB is purged, because the table is dropped!! Why this gets executed, i dont know!!!

        • 16. Re: JDBCacheLoader & hot redeploy
          manik

          This smells like

           cache.jdbc.table.drop=true
          


          Could you explicitly force this NOT to happen, by adding:

           cache.jdbc.table.drop=false
          


          and see if it helps?



          • 17. Re: JDBCacheLoader & hot redeploy
            lovelyliatroim

             


            cache.jdbc.table.drop=false



            Does the job alright, the db doesnt get purged now after hot-redeploy!!

            Thanks Manik,
            LL

            1 2 Previous Next