[supertaz]

Right back to the null interceptor exception. It definitely seems to be related to MySQL.

Stopped JBoss.
Deleted tmp, work, and data directories.
Restarted JBoss.

Once again working as a default installation.

What can I do to help diagnose/fix the null interceptor exception?

[roy.russo]

I dont understand how you are getting CR3 to run at all without the code fix to the cms I added today. Did you add that yourself? Also, you need to restart mysql after you do the changes to the truncation issue.

I am running on 4.0.4GA with mysql 5. Subsequent restarts work fine as well.

[supertaz]

Hey Roy,

I didn't add the changes that you made, but it seems to run just fine with hsqldb. I did restart after making the changes to the DS, and I did restart mysql with the new my.cnf (although it should be noted that the my.cnf doesn't specify the sql_mode at all, as it's a fresh one pulled out of /usr/share/mysql/, so that could be the problem with using MySQL 5).

As you can see below, MySQL is running in its default (relaxed) state:

mysql> select @@SQL_MODE;
+------------+
| @@SQL_MODE |
+------------+
| |
+------------+
1 row in set (0.00 sec)

mysql> select @@global.SQL_MODE;
+-------------------+
| @@global.SQL_MODE |
+-------------------+
| |
+-------------------+
1 row in set (0.00 sec)

mysql> select @@session.SQL_MODE;
+--------------------+
| @@session.SQL_MODE |
+--------------------+
| |
+--------------------+
1 row in set (0.00 sec)

[rali.genova]

Roy, the CMS problem doesn't show up at deploy/start up time, this is why he is not experiencing it, and CMS is fully functional with HSQLDB.