4 Replies Latest reply on Oct 28, 2003 5:50 PM by nefilim

    Issues and Resolutions

    Raja Master

      I took a cut at installing nukes today with Branch_3_2 and the latest nukes-snapshot. It deployed mostly okay except for these issues.
      1) You need to run prepare.ddl before running setup.ddl. Prepare.ddl is the one used to create the nukes database and the nukes user
      2) When trying to create a new user, it threw me an exception as it was trying to locate a "pn_last_visit" field in the nukes-user table. This is not in setup.ddl . This column also has to be made not null.
      3) I had to change the local.properties file to point the app to use MySQL instead of Hypersonic. This threw me a few "call IDENTITY()" exceptions as this function is not defined for MySQL(I think!!). The jbosscmp-jdbc.xml was having a data-mapping for hypersonic .

      Can someone update the install instructions?

      Thanks
      Raj

        • 1. Re: Issues and Resolutions
          lphipps Newbie

          Yup I found with the snapshot download I got on October 27th that I had to run the MySQL command,

          ALTER TABLE nuke_users ADD COLUMN pn_last_visit DATETIME NOT NULL DEFAULT '0';

          after I had loaded the setup.ddl as that particular line was commented out of the setup.ddl but is required else you can't logon.

          I also had to edit prepare.ddl to remove the ' ' tics from the line,

          ON nukes.* TO nukes@localhost WITH GRANT OPTION;

          And for my system I had to edit the,

          $NUKES_HOME/nukes/src/resources/mysql/nukes-ds.xml

          as follows: Change line 7 and replace,
          <driver-class>org.gjt.mm.mysql.Driver</driver-class>

          with,

          <driver-class>com.mysql.jdbc.Driver</driver-class>

          Is there a reason to be using the Giant Java Tree definition as opposed to the MySQL.com one ?. Is GJT more future-proof or flexible over the MySQL one ?.


          • 2. Re: Issues and Resolutions
            nefilim Newbie

            Same here, also, I had to add an entry into the MySQL user table for localhost.localdomain, which appears to be the target host when using jdbc on a redhat box with the localhost.localdomain /etc/hosts entry.

            • 3. Re: Issues and Resolutions
              Viet Master

              > Same here, also, I had to add an entry into the MySQL
              > user table for localhost.localdomain, which appears
              > to be the target host when using jdbc on a redhat box
              > with the localhost.localdomain /etc/hosts entry.


              yes it suxx sometimes on redhat for that.

              • 4. Re: Issues and Resolutions
                nefilim Newbie

                oh also, according to the mysql documentation the use of single ticks (') is valid and recommended for hostnames and usernames with non alphanumeric characters such as '-'.

                i modified the statement to the following to make it work (dropped some privileges):

                grant select,insert,update,delete,create,drop,references,index,alter on nukes.* to nukes@'localhost' with grant option;

                and

                grant select,insert,update,delete,create,drop,references,index,alter on nukes.* to nukes@'localhost.localdomain' with grant option;