2 Replies Latest reply on Apr 30, 2007 2:03 PM by Mark Spritzler

    Strange bug. deleting datasource through ProfileService

    Mark Spritzler Apprentice

      I hope this is reproducible for you guys.

      But here is what is happening. I deleted a datasource through the ProfileService. The name of the datasource file was delete-ds.xml. It removed the file from the deploy directory. But now if I ever try to deploy a file called delete-ds.xml the AS throws an exception when booting up and trying to deploy the hsqldb-ds.xml.

      If I rename the delete-ds.xml file to any other name, then the Server boots up with no exception.

      here is the exception. Must be in the VPN to see this
      http://wwwapps.rdu.redhat.com/w3xpastebin/pastebin.php?show=1410

      Thanks

      Mark

        • 1. Re: Strange bug. deleting datasource through ProfileService
          Mark Spritzler Apprentice

          I wasn't able to reproduce this. I tried with a new file called deleteme-ds.xml. Deleted it through the ProfileService and recopied a deleteme-ds.xml into the deploy directory and it booted up.

          My next test is to take that copied deleteme-ds.xml and change its jndi-name in the file and reboot to see if that reproduces the problem

          Nope, that didn't reproduce the problem. If I get it again and remember something specific that can make it reproducible, I will post it.

          Mark

          • 2. Re: Strange bug. deleting datasource through ProfileService
            Mark Spritzler Apprentice

            Well, while I wasn't able to reproduce the error with other datasources. I was able to fix the problem, by deleting the deleteme-ds.xml.attachments file from the server\default\attachments\ServiceXSLDeployer directory.

            So that file must have still had the jndi-name as DefaultDS (hence the conflicyt with the Hypersonic datasource), and was not updated when I made the change to the actual deleteme-ds.xml.

            Mark