@Dumitru Boldureanu: I updated from 4.2.7 directly to 4.3.0 Final. So This problem can be also in 4.2.8 as you described.