Cannot import a solution: com.servoy.j2db.persistence.Repo..

Classic Servoy
1

Hi,

I’m trying to make a local copy of our production solution, but when importing as “Import as” on my test repository, I get the following error and the solution cannot be imported:

com.servoy.j2db.persistence.RepositoryException: com.servoy.j2db.persistence.RepositoryException: java.sql.SQLException: connection already closed or transaction in progress
Reserved words used as table or column names: columns: segment;

I specified “Yes” to the question of continue importing allthough reserved keywords found.

Both the local Db and the Production DB are Oracle 9i.

From my local environment, I connected my Developer to the production repository and exported the solution. These are the details of the local environment:
Servoy Developer
Version R2 2.2-build 328
Java version 1.4.1_05-b01 (Windows 2000)

Then I connected the local environment to the test repository and tried to import the solution and got the error.

The production environment has the following specification:

Server Information
Servoy version R2 2.2b3-build 318, repository version 25
Uptime: 40 days 23 hours 5 minutes 36 seconds

JDK Information
java.vm.name=Java HotSpot™ Client VM
java.vm.version=1.5.0_02-b09
java.vm.info=mixed mode, sharing
java.vm.vendor=Sun Microsystems Inc.

Operating System Information
os.name=Linux
os.version=2.4.20-8smp
os.arch=i386

Yes, I know we are still on a beta on production… DOn’t ask :roll: , but that is working fine for us at the moment.

Anyone got a clue? Tried searching the forum, becaus eI think this has been noticed before, but couldn’t fuind any reference.

Any thoughts appreciated.

Paul

2

I remember having similar problems with some 2.2 beta. What happens if you try with 2.2 final (you can go back later to your beta, if you wish)?

3

The test environment I’m importing to is a 2.2 final.

The developer I’m exporting with and imporing with is also a 2.2 final.

The only thing that is not a 2.2 final is the production repository I’m exporting from.

so, the only thing I could try is update the production repository to 2.2 final, but that is not something that can be undertaken right now, I’m afraid.

To my knowledge, it should be possible to export from an older version into a newer version. Only vise versa is not possible, right?

Paul

4

This should indeed work. Can you run with -DSTACKTRACE=true and email me the log? That way I have more context information. Looks like the db connections is dying somewhere, for some reason.

5

Send it to you by email.

Paul