i18n data import failed

Classic Servoy
1

Hello,

for quite a while we have the problem that i18n keys cannot be updated when a new version of a solution is uploaded to the Server with the setting to update only new keys. The error we get is this:

i18n data import failed com.servoy.j2db.persistence.RepositoryException: com.servoy.j2db.persistence.RepositoryException: No transaction active for id= No transaction active for id=

Note: we have more than 20.000 keys in the messages table.

Thanks for looking at this

Patrick

2

Anyone? I have this problem any time now and have to import the messages table manually. not nice.

3

We have the same issue here, too

4

Me too…
I unload Sybase messages table and load them, thru sybase

5

Does this only happen if you choose to update only new keys or does it always happen?

I will file a case then. This make deployment a hassle if you frequently deploy things.

6

patrick:
Does this only happen if you choose to update only new keys or does it always happen?

I will file a case then. This make deployment a hassle if you frequently deploy things.

Always

7

Case created.

8

Has this issue been resolved or commented on by Servoy as yet?

9

I saw somewhere else, that this issue has been fixed in 3.5.2

10

Thanks Harjo

Looks like 3.5.2 is gona be a ‘belly-buster’ of changes then!

11

I think not changes, but fixes! :wink:

12

HJK:
I think not changes, but fixes! :wink:

I thought Servoy only did enhancements? :lol:

13

enhancements… fixes… whatever! :lol:
if it just works, it is fine with me! :D