My copy of developer has suddenly stopped showing the login dialogue - for ANY solution. My current project runs a method to confirm login details at startup and quits if it cannot confirm validity of the login - the result is that I cannot open my solution because it does not show the login dialogue and therefore the startup method cannot validate!
Any ideas how I can re-enable login and get back into my solution?
Have you moved/changed anything with your security settings?
David,
There is a checkbox in developer Edit → Preferences → Designer → Allow developer frame related actions.
If this is unchecked, application.exit() does not quit developer.
Hope this helps.
Rob
Hi Marcel
I didn’t make any changes to security settings - haven’t even accessed them recently! In the meantime I have managed to export the solution and import it to a different Servoy installation on another computer. On this copy of Servoy the login dialogue was working for another solution and by logging in to that one and then switching solutions I have been able to get back into the solution to check the security settings - the require login box had become unchecked though I have definitely not done that myself. Having reset it I can now access the solution again on the second computer.
However, my main developer copy of Servoy is still not showing the login dialog for any solutions, even ones where I can get in and check the security set up and where the solution login required box is still checked! It looks like something fundamental has happened to this installation and the only solution may be to trash it and reinstall
Rob - by unchecking the box I can get back into the solution - thanks for that!
BUT the issue of not showing the login dialog remains, or at least remains unreliable - the first few times after resetting the pref, it was the same as before - no login dialogue, but I could at least get in. THEN the dialogue came back for one solution but not for a different one where login is also required. Definitely something flakey going on!
There are some references in the log to an open transaction and then errors relating to trigger element names being empty even though no elements have been touched at this point!
com.servoy.j2db.persistence.RepositoryException: com.servoy.j2db.persistence.RepositoryException: Root object 5f6b33f7-3f47-4e25-bbd0-6050bc38f436 commit not possible: transaction still in use, count: 2; thread AWT-EventQueue-0
at com.servoy.j2db.persistence.ConnectionHandler.a(Unknown Source)
at com.servoy.j2db.persistence.ConnectionHandler.a(Unknown Source)
at com.servoy.j2db.persistence.Repository.a(Unknown Source)
at com.servoy.j2db.persistence.AbstractRootObject.update(Unknown Source)
at com.servoy.j2db.develop.debugger.j.aT(Unknown Source)
at com.servoy.j2db.develop.debugger.b$a.actionPerformed(Unknown Source)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1882)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2202)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:234)
at java.awt.Component.processMouseEvent(Component.java:5554)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3126)
at java.awt.Component.processEvent(Component.java:5319)
at java.awt.Container.processEvent(Container.java:2010)
at java.awt.Component.dispatchEventImpl(Component.java:4021)
at java.awt.Container.dispatchEventImpl(Container.java:2068)
at java.awt.Component.dispatchEvent(Component.java:3869)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4256)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3936)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3866)
at java.awt.Container.dispatchEventImpl(Container.java:2054)
at java.awt.Window.dispatchEventImpl(Window.java:1774)
at java.awt.Component.dispatchEvent(Component.java:3869)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:176)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
Caused by: com.servoy.j2db.persistence.RepositoryException: Root object 5f6b33f7-3f47-4e25-bbd0-6050bc38f436 commit not possible: transaction still in use, count: 2; thread AWT-EventQueue-0
at com.servoy.j2db.persistence.ConnectionHandler.int(Unknown Source)
... 28 more
2007-03-28 12:38:57,384 ERROR [AWT-EventQueue-0] com.servoy.j2db.util.Debug - Deleting unreferenced blobs
2007-03-28 15:08:35,907 ERROR [AWT-EventQueue-0] com.servoy.j2db.util.Debug - Shouldn't happen that the trigger element names are empty, is this called in a script that is triggered by solution startup?
2007-03-28 15:08:35,920 ERROR [AWT-EventQueue-0] com.servoy.j2db.util.Debug - Shouldn't happen that the trigger element names are empty, is this called in a script that is triggered by solution startup?
2007-03-28 15:09:00,525 ERROR [AWT-EventQueue-0] com.servoy.j2db.util.Debug - Shouldn't happen that the trigger element names are empty, is this called in a script that is triggered by solution startup?
I don’t know how this relates to security settings being changed though!
It looks like either somethings is wrong with your repository database or with your startup method. What do you do in your startup method?
Patrick,
The startup method goes through a number of routines to set window size, set graphics on buttons on startup form, test for demo solution settings etc - I will trawl through it now to see if I can spot anything!
I had suspicions also about the repository having issues - is this fixable or is a clean install and import the better route?
To “clean” the repository it could help to create a new repository and import the solution into that.
If the repository has been damaged, how does this occur? I am keen to avoid this situation in the future!