I think I have a corrupt repository and don’t know how to fix it.
I open a solution in developer and make some edits to a form method.
I verify and close the method without error.
I close the solution without error.
When I re-open the solution the edits are not there. Correct solution, correct form, correct method, but no edits. I’ve checked this several times.
In the Admin log I see
2007-08-03 09:09 AWT-EventQueue-0 ERROR com.servoy.j2db.util.Debug Throwable
java.lang.Exception: Root object ‘CuttingEdge’ transaction not closed on flush!
at com.servoy.j2db.persistence.ConnectionHandler.if(Unknown Source)
at com.servoy.j2db.persistence.r.a(Unknown Source)
at com.servoy.j2db.persistence.r.a(Unknown Source)
at com.servoy.j2db.persistence.Repository.flushAllCachedData(Unknown Source)
at com.servoy.j2db.develop.at.cy(Unknown Source)
at com.servoy.j2db.develop.J2DBDeveloper.showRespositoryDialog(Unknown Source)
at com.servoy.j2db.develop.c.aq.doIt(Unknown Source)
at com.servoy.j2db.cmd.c$2.run(Unknown Source)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
2007-08-03 09:09 AWT-EventQueue-0 ERROR com.servoy.j2db.util.Debug Deleting unreferenced blobs
I tried deleting the entire solution (ie all releases) from the repository and then importing the last saved export (presumed good). It didn’t fix the problem.
If I flush from the admin pages, it saves. I’ve never done or needed to do this before. Any idea what’s going on?
Tony,
I have run into this before. Do you happen to be:
-
Running the Servoy Developer where you are sharing the development repository with your production server repository?
-
Sharing production data with development data?
Let me know if you have something like this going on … if so I will respond further.
Michael
Hi Michael,
I’m not running Servoy Server. I’m not sharing the data.
I do have Servoy Developer running on another machine on the same LAN (one Mac, one Windows) but they aren’t sharing the same repository, at least they’re not meant to be.
I just opened Sybase Central, I can see both servoy_repository on different IPs, using the same port 2638.
Since flushing in the admin pages, it seems to have righted itself. I’m still curious to know what might’ve happened so I can avaoid it in future.
Thanks for your thoughts.
If you flushed in the “Admin pages” you have an instance of Server running? Yes/no?
The symptoms you describe are very much like what occured at our site when we had an overlap between production and development (dev work wouldn’t save consistently … sometimes it did, other times it didn’t … I was always left nervous to whether it was going to behave or not). When I keep development and deployment (ie - server) repositories separate, it has been rock solid (other than a bad JDBC driver against our Postgres backend and repository). Sorry, while a bit familiar with Sybase we aren’t using it here.
Michael
Antonio,
We discovered (and fixed already for 3.1.7) a problem when editing a solution immediately after importing.
The changes would not always save until you restart developer because the old solution was not correctly flushed.
Until the new release is there, a workaround is to restart developer or flush the solution before editing a newly imported solution.
Rob
Thanks Rob, my faith is restored! (Having said that - I saw this problem BEFORE doing the import…)
Michael, when running developer it’s still possible to open the admin pages on localhost:8080/servoy-admin to see what’s going on.
Tony,
Yes, I thought about that after I did my post … you probably were looking at the local instance.
Glad you are away again!
Best,
Michael
antonio:
Rob, any ETA for 3.1.7?
That will be sometime later this month. Next week, with any luck. Don’t hold your breath though.