Page 1 of 1

After installing and upgrading to the latest Servoy Version

PostPosted: Sat Jan 08, 2022 5:47 pm
by dlclark
Installed Servoy Version: 2021.12.0.3722 Windows 64 bit
Servoy cannot load tables from previous database connection defined in Resources. Running MYSQL 8,0 on Windows 10 also.

I have tried recreating the server: e.g. delete old spec and create a new one. Get the same error.

I have also tried creating a new solution , then defining a connection with a different name, same issue.

I have also tried uninstalling, reinstalling - cannot go back to previous version because workspace is now corrupted by updated version.

Any ideas?

Thanks,

Daryl

Re: After installing and upgrading to the latest Servoy Vers

PostPosted: Sat Jan 08, 2022 5:59 pm
by dlclark
Also, I did uninstall the 2021.12.0.3722 Windows 64 bit ; then reinstall Servoy Version: 2021.9.0.3703

and created a new workspace; I can create database connections just fine in this version.

Re: After installing and upgrading to the latest Servoy Vers

PostPosted: Sat Jan 08, 2022 6:26 pm
by pitc
Have you checked the MySql driver is installed or up to date for the latest Servoy version?

Re: After installing and upgrading to the latest Servoy Vers

PostPosted: Mon Jan 10, 2022 2:50 am
by dlclark
I am running version J Connector version 8.0.27

Re: After installing and upgrading to the latest Servoy Vers

PostPosted: Mon Jan 10, 2022 10:05 am
by jcompagner
do you get any exceptions in the various log files?
We test against mysql continuously so that should work fine.
What does the server editor say when you test a connection? is de driver correctly loaded?

Re: After installing and upgrading to the latest Servoy Vers

PostPosted: Mon Jan 10, 2022 3:43 pm
by dlclark
I re-installed the latest Servoy upgrade and here is the error message I am getting:

An internal error occurred during: "Loading servers/tables needed by current solution".
Could not initialize class org.hibernate.cfg.Environment

Re: After installing and upgrading to the latest Servoy Vers

PostPosted: Mon Jan 10, 2022 3:56 pm
by dlclark
Another bit of strangeness:

if I disable the server definition and delete it; then re-create the connection - the connection tests OK, but when I try to save it the screen appears to freeze a bit, then I get a error message indicating the server already exists.

Re: After installing and upgrading to the latest Servoy Vers

PostPosted: Mon Jan 10, 2022 4:19 pm
by dlclark
This stime after I tried to recreate the server connection, I exited Servoy; upon restarting servoy developer, the connection is stored and since the form for testing the connection is still visible, the test connection is also successful, but still get the error message about hibernate.

Re: After installing and upgrading to the latest Servoy Vers

PostPosted: Mon Jan 10, 2022 4:59 pm
by jcompagner
that class should just be there
do you have full stacktrace/error information in the workspace and/or servoy log?

Re: After installing and upgrading to the latest Servoy Vers

PostPosted: Wed Jan 12, 2022 4:13 pm
by dlclark
An internal error occurred during: "Loading servers/tables needed by current solution".
Could not initialize class org.hibernate.cfg.Environment

This is the error message I receive. I do not get a stack trace...

I do find a hibernate jar in the configuration directory under developer? Also in application_server/lib directory

Re: After installing and upgrading to the latest Servoy Vers

PostPosted: Wed Jan 12, 2022 4:42 pm
by jcompagner
are you sure you don't get any logging?
not in he servoy_log.txt file in the appliation_server dir
or in the workspace\.metadata\.log file?

Re: After installing and upgrading to the latest Servoy Vers

PostPosted: Thu Jan 13, 2022 11:51 pm
by dlclark
AH, I do find a stack trace in the workspace/.metadata/.log

!ENTRY org.eclipse.jface 4 2 2022-01-12 08:47:02.738
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
!STACK 0
java.lang.NoClassDefFoundError: Could not initialize class org.hibernate.cfg.Environment
at org.hibernate.dialect.MySQLDialect.<init>(MySQLDialect.java:83)
at org.hibernate.dialect.MySQL5Dialect.<init>(MySQL5Dialect.java:22)
at org.hibernate.dialect.MySQL55Dialect.<init>(MySQL55Dialect.java:14)
at org.hibernate.dialect.MySQL57Dialect.<init>(MySQL57Dialect.java:21)
at org.hibernate.dialect.MySQL8Dialect.<init>(MySQL8Dialect.java:18)
at org.hibernate.dialect.Database$18.resolveDialect(Database.java:373)
at org.hibernate.engine.jdbc.dialect.internal.StandardDialectResolver.resolveDialect(StandardDialectResolver.java:25)
at com.servoy.j2db.dblayer.Zb.<init>(Zb.java:379)
at com.servoy.j2db.server.persistence.Zn.Za(Zn.java:374)
at com.servoy.j2db.server.persistence.Zn.Za(Zn.java:1117)
at com.servoy.j2db.datasource.Zp.initializeConnection(Zp.java:1)
at org.apache.commons.dbcp2.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:379)
at org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:571)
at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:298)
at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:223)
at org.apache.commons.dbcp2.PoolingDataSource.getConnection(PoolingDataSource.java:141)
at com.servoy.j2db.datasource.Za.getConnection(Za.java:176)
at com.servoy.j2db.datasource.jmx.ManagedBasicPoolingDataSource.getConnection(ManagedBasicPoolingDataSource.java:24)
at com.servoy.j2db.server.persistence.Zn.Za(Zn.java:212)
at com.servoy.j2db.server.persistence.Zn.Zc(Zn.java:1992)
at com.servoy.j2db.server.persistence.Zn.Za(Zn.java:663)
at com.servoy.j2db.server.persistence.Zn.Zf(Zn.java:1570)
at com.servoy.j2db.server.persistence.Zn.Zk(Zn.java:750)
at com.servoy.j2db.server.persistence.Zn.Za(Zn.java:1571)
at com.servoy.j2db.server.persistence.Zn.getTableNames(Zn.java:1940)
at com.servoy.eclipse.ui.views.solutionexplorer.SolutionExplorerTreeContentProvider.hasChildren(SolutionExplorerTreeContentProvider.java:1656)
at org.eclipse.jface.viewers.AbstractTreeViewer.isExpandable(AbstractTreeViewer.java:2171)
at org.eclipse.jface.viewers.TreeViewer.isExpandable(TreeViewer.java:546)
at org.eclipse.ui.part.DrillDownAdapter.canExpand(DrillDownAdapter.java:108)
at org.eclipse.ui.part.DrillDownAdapter.canGoInto(DrillDownAdapter.java:146)
at org.eclipse.ui.part.DrillDownAdapter.updateNavigationButtons(DrillDownAdapter.java:338)
at org.eclipse.ui.part.DrillDownAdapter.selectionChanged(DrillDownAdapter.java:328)
at org.eclipse.jface.viewers.Viewer$1.run(Viewer.java:151)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:174)
at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:148)
at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2130)
at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1176)
at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1205)
at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:400)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4237)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1060)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4054)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3626)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1041)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:551)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:156)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:152)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:136)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:596)
at org.eclipse.equinox.launcher.Main.run(Main.java:1467)

Re: After installing and upgrading to the latest Servoy Vers

PostPosted: Fri Jan 14, 2022 10:20 am
by jcompagner
don't you get any other exception around that?
(so before or after that)

Re: After installing and upgrading to the latest Servoy Vers

PostPosted: Fri Jan 14, 2022 2:58 pm
by jcompagner
we found the cause, created a case for this: https://support.servoy.com/browse/SVY-16806