3.1 solution open problem

Classic Servoy
1

I attempted to update to version 3.1, but am unable to open several of my solutions after the upgrade. The simplest solutions do open, but complicated ones stay on the spinning Servoy logo forever (20 minutes + before force quitting).

I see several warnings in the log file about long column names like this:

2007-01-08 15:01:57,876 WARN [TaskExecuter[0]] com.servoy.j2db.persistence.Server - Column name 'pk_inventory_price_table_join_id' from table 'inventory_price_table_join' is too long (>30 chars) -- this is not supported by all databases

These happen in the first 20 seconds of the solution opening and then when I quit, this appears in the log:

2007-01-08 15:09:44,338 ERROR [TaskExecuter[0]] com.servoy.j2db.util.Debug - Throwable
com.servoy.j2db.persistence.RepositoryException: com.servoy.j2db.persistence.RepositoryException: java.lang.IllegalStateException: Pool not open
	at com.servoy.j2db.persistence.Repository$f.loadColumnInfo(Unknown Source)
	at com.servoy.j2db.persistence.Repository.loadColumnInfo(Unknown Source)
	at com.servoy.j2db.persistence.Server.char(Unknown Source)
	at com.servoy.j2db.persistence.Server.getTable(Unknown Source)
	at com.servoy.j2db.persistence.ah.getTable(Unknown Source)
	at com.servoy.j2db.persistence.ah.<init>(Unknown Source)
	at com.servoy.j2db.persistence.Repository.a(Unknown Source)
	at com.servoy.j2db.persistence.Repository.a(Unknown Source)
	at com.servoy.j2db.persistence.r.a(Unknown Source)
	at com.servoy.j2db.persistence.r.if(Unknown Source)
	at com.servoy.j2db.persistence.Repository.getActiveRootObject(Unknown Source)
	at com.servoy.j2db.persistence.Repository.getActiveSolution(Unknown Source)
	at com.servoy.j2db.ActiveSolutionHandler.loadActiveSolution(Unknown Source)
	at com.servoy.j2db.J2DBClient$12.run(Unknown Source)
	at com.servoy.j2db.util.am.run(Unknown Source)
	at java.lang.Thread.run(Thread.java:613)
Caused by: com.servoy.j2db.persistence.RepositoryException: java.lang.IllegalStateException: Pool not open
	at com.servoy.j2db.persistence.Repository.createNewColumnInfo(Unknown Source)
	... 16 more
Caused by: java.lang.IllegalStateException: Pool not open
	at org.apache.commons.pool.BaseObjectPool.assertOpen(BaseObjectPool.java:123)
	at org.apache.commons.pool.impl.GenericObjectPool.returnObject(GenericObjectPool.java:898)
	at org.apache.commons.dbcp.PoolableConnection.close(PoolableConnection.java:110)
	at org.apache.commons.dbcp.DelegatingConnection.close(DelegatingConnection.java:166)
	at com.servoy.j2db.persistence.datasource.TransactionConnection.close(Unknown Source)
	at com.servoy.j2db.util.Utils.closeConnection(Unknown Source)
	at com.servoy.j2db.persistence.Repository.getSequence(Unknown Source)
	... 17 more
2007-01-08 15:09:44,345 ERROR [TaskExecuter[0]] com.servoy.j2db.util.Debug - Throwable
java.lang.IllegalStateException: Pool not open
	at org.apache.commons.pool.BaseObjectPool.assertOpen(BaseObjectPool.java:123)
	at org.apache.commons.pool.impl.GenericObjectPool.returnObject(GenericObjectPool.java:898)
	at org.apache.commons.dbcp.PoolableConnection.close(PoolableConnection.java:110)
	at org.apache.commons.dbcp.DelegatingConnection.close(DelegatingConnection.java:166)
	at com.servoy.j2db.persistence.datasource.TransactionConnection.close(Unknown Source)
	at com.servoy.j2db.util.Utils.closeConnection(Unknown Source)
	at com.servoy.j2db.persistence.Repository.a(Unknown Source)
	at com.servoy.j2db.persistence.Repository.a(Unknown Source)
	at com.servoy.j2db.persistence.r.a(Unknown Source)
	at com.servoy.j2db.persistence.r.if(Unknown Source)
	at com.servoy.j2db.persistence.Repository.getActiveRootObject(Unknown Source)
	at com.servoy.j2db.persistence.Repository.getActiveSolution(Unknown Source)
	at com.servoy.j2db.ActiveSolutionHandler.loadActiveSolution(Unknown Source)
	at com.servoy.j2db.J2DBClient$12.run(Unknown Source)
	at com.servoy.j2db.util.am.run(Unknown Source)
	at java.lang.Thread.run(Thread.java:613)

Tested on both OS X and Windows (Java 1.5.0_06) with the same results. I’m using MSSQL 2000.

2

There is another thread dealing with the 30+ char column names if I am correct…

3

The log messages about long column names are only warnings, the import should still succeed.
Are there no other log messages before you quit?

Rob

4

Nope, those are the only messages in the log. This is not during a solution import but when I’m trying to open a solution in 3.1 Developer that opened correctly in 3.02.

5

We cannot reproduce this.
Please create a support case at: http://crm.servoy.com/servoy-webclient/ … oy_support , include supply a test solution that shows the problem

6

Hi,

I seem to have a similar problem on upgrading to 3.1.3. All solutions worked fine in the developer when I was using 3.0 beta, but now only some work. When I try to open one that doesn’t work I get an error dialog saying ‘java.lang.NullPointerException’.

I’ve looked in the servoy_log fie, but all that I get when I try to open this solution is :
2007-02-16 18:01:07,171 ERROR [TaskExecuter[0]] com.servoy.j2db.util.Debug - Throwable
java.lang.NullPointerException
at com.servoy.j2db.develop.ScriptNameValidator.findDuplicate(Unknown Source)
at com.servoy.j2db.develop.J2DBDeveloper.a(Unknown Source)
at com.servoy.j2db.ClientState.handleLoadedSolution(Unknown Source)
at com.servoy.j2db.J2DBClient$11.run(Unknown Source)
at com.servoy.j2db.util.al.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)

Also, I I can load all the solutions fine in a client, so it is only the developer that won’t load…

Does anyone know why this solution won’t load anymore?

Thanks,

Nick

7

I’m curious to hear exactly the flow of actions prior to having trouble opening some solutions with more recent versions. I ask because I noticed a similar problem with some build I was playing with recently and found a workaround that gets any solution open and also might provide a clue to engineering if this workaround helps others who have posted here:

My observations:

– Any solution would open upon a fresh launch of Developer.

– If I’d already been working with an open solution and wished to close it and open a different solution, I saw the enternal spinning “cog” logo if I took this sequence of actions:

1: Cmd(orCtrl)-W (or File/Close), causing the Select Solution dialog (list of available solutions) to open up
2: Immediately select the next solution I wish to open from the dialog

– If I instead followed this sequence I could open any other solution just fine:

1: Cmd-W
2: Escape (or click Cancel) to close the Select Solution window
3: Cmd-O
4: Now select the desired solution from the list

???

kazar

8

No it doesn’t matter what order I open close solutions etc. some ( smaller ) solutions will open in developer but the main ( larger ) solution doesn’t open and produces the above error. Bizarrely it does open using a client.

Any help would be appreciated.

Nick

9

nick: somehow your main solution has some error in it that causes this problem
Can you export it and sent the solution (including modules) to us?
Or what you can try is export the solution and modules and re import it in a clean repository

What goes wrong in the developer code that checks your solution and modules if they are valid (no duplicate names or other clashes in the code)

10

kazar: in what version do you get that behavior?
I haven’t seen that before so if you first close the dialog and then open it again it always works. And if you don’t do that it never? works?
Is this the case for all your solutions?

11

Hi Johan – I regret to say I cannot remember exactly what flavor of Servoy I encountered this problem in. Yes, it was all solutions, including the sample crm.

kazar