haven't seen this at all and all tests we have would complain about it I think. Anyway what hibernate version do you use? Do you have it in custom application or you use with jbpm-console? And last question how do you load that logs?
Sorry just saw that, it seems the notification skipped my inbox.
I use hibernate 4.1.7, not through jbpm-console.
Are you saying that those two new fields are never supposed to be null? If that's the case, then I might have to track down the problem. If not, then there is definitely a mapping problem as you wouldn't be able to persist a null primitive type with this mapping.
in general, since they are primitives they will never be null as they get the default value for it's type. Nevertheless the idea behind it was to support null so please file a jira issue for it to make them as objects instead of primitives. I think the case where you would encounter it is when you have existing db will data and you upgrade that table and these values are null then by default. In that case it fails, is that what you ran into?