Bug #28031 Falcon Difference from InnoDB autocommit behaviour

Description:
The "How to repeat", below, shows that JStar and InnoDB have a different
rule for AUTOCOMMIT, as discussed in emails with
subect = "Concurrency with JStar/Falcon"
participants = peterg, hakan, aharrison@ibphoenix, andrey

How to repeat:
mysql> select @@autocommit;
+--------------+
| @@autocommit |
+--------------+
| 1 |
+--------------+
1 row in set (0.00 sec)

mysql> create table ti (s1 int) engine=innodb;
Query OK, 0 rows affected (0.01 sec)

mysql> start transaction;
Query OK, 0 rows affected (0.00 sec)

mysql> insert into ti values (0);
Query OK, 1 row affected (0.00 sec)

mysql> rollback;
Query OK, 0 rows affected (0.00 sec)

mysql> select count(*) from ti;
+----------+
| count(*) |
+----------+
| 0 |
+----------+
1 row in set (0.01 sec)

mysql> create table tj (s1 int) engine=jstar;
Query OK, 0 rows affected (0.01 sec)

mysql> start transaction;
Query OK, 0 rows affected (0.00 sec)

mysql> insert into tj values (0);
Query OK, 1 row affected (0.27 sec)

mysql> rollback;
Query OK, 0 rows affected (0.00 sec)

mysql> select count(*) from tj;
+----------+
| count(*) |
+----------+
| 1 |
+----------+
1 row in set (0.00 sec)

Test case is falcon_bug_28031.test.