- This topic has 4 replies, 3 voices, and was last updated 12 years, 11 months ago by
.
-
Posts
-
Hello,
I had a large list of databases configured in the DB Browser and I logged in today to find they are all gone. This configuration has existed for almost a year now with no issue. I was away for a week and this box was not used. The only change I made was attempting to add the GWT plugin. I can’t seem to find where these database entries are stored in the file system to attempt to recover it. Why did this disappear? Can I recover it? Where is the file even stored to recover? My backup export is months old now so I’d rather try to recover this. Also, there would be little point in recovering without fixing the issue or they will just be deleted once again.
Thanks for the response,
/Chipcdebergh,
Sorry that you ran into this issue.
Can you give some more information for me to understand the issue better?
1) Share your build id from Help > About MyEclipse Enterprise Workbench. Paste it here.
2) Which version of GWT plugin did you install and how? Is it through an update site?
3) Do you have any third party plugins installed ?
4) Do you see any errors of interest logged in the .log file which is located at <workspace dir>/.metadata/.log ? If yes then paste them here
5) Can you try uninstalling the GWT plugin from the MyEclipse Configuration Center, restart the IDE and check if it recovers the DB Browser entries?
6) Also send me the detail steps on how you tried to install the plugin for me to be able to replicate it at my end.
MyEclipse Enterprise Workbench in Ubuntu 10.04
Version: 8.6.1
Build id: 8.6.1-20101117GWT plugin update site: http://dl.google.com/eclipse/plugin/3.5
also installed subclipse 1.6 months ago
error:
!ENTRY org.eclipse.osgi 2 0 2011-05-10 21:55:45.899
!MESSAGE While loading class “org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer$LastUpdate”, thread “Thread[Worker-5,5,main]” timed out waiting (5000ms) for thread “Thread[Worker-2,5,main]” to finish starting bundle “org.eclipse.jst.j2ee_1.1.302.me201005202301 [1238]”. To avoid deadlock, thread “Thread[Worker-5,5,main]” is proceeding but “org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer$LastUpdate” may not be fully initialized.
!STACK 0
org.osgi.framework.BundleException: State change in progress for bundle “reference:file:/home/cdebergh/Genuitec/Common/plugins/org.eclipse.jst.j2ee_1.1.302.me201005202301.jar” by thread “Worker-2”.
at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1073)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:278)
at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:408)
at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:449)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:211)
at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:381)
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:457)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:398)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.<init>(J2EEComponentClasspathContainer.java:105)
at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.install(J2EEComponentClasspathContainer.java:350)
at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathInitializer.initialize(J2EEComponentClasspathInitializer.java:47)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2642)
at org.eclipse.jdt.internal.core.JavaModelManager$11.run(JavaModelManager.java:2548)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2588)
at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1808)
at org.eclipse.jdt.core.JavaCore.initializeAfterLoad(JavaCore.java:3410)
at org.eclipse.jdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:35)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException
… 24 more
Root exception:
org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException
at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1073)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:278)
at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:408)
at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:449)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:211)
at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:381)
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:457)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:398)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.<init>(J2EEComponentClasspathContainer.java:105)
at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.install(J2EEComponentClasspathContainer.java:350)
at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathInitializer.initialize(J2EEComponentClasspathInitializer.java:47)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2642)
at org.eclipse.jdt.internal.core.JavaModelManager$11.run(JavaModelManager.java:2548)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2588)
at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1808)
at org.eclipse.jdt.core.JavaCore.initializeAfterLoad(JavaCore.java:3410)
at org.eclipse.jdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:35)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)I tried removing GWT and restating. Still not there. What file are they stored in?
http://code.google.com/eclipse/docs/install-eclipse-3.5.html
cdebergh,
Thank you for the details. I have escalated this issue to the dev team for further investigation.
cdebergh,
I don’t know how this could have happened unless you accidentally switched workspaces, which you should have noticed. Installing GWT should not affect the DB Browser in anyway either and to be sure, we explicitly tested this as well.
If you create a new profile, does it persist when you restart MyEclipse or does it disappear?
The file responsible for your drivers is at <workspace folder>\.metadata\com.genuitec.eclipse.sqlexplorer\ConnectionProfiles.xml. If you find this file in your backups, you can use the File > Import > Database > JDBC Driver (MyEclipse) and point to this file to import the driver configurations into MyEclipse.
You can also export the profiles by using File > Export > Database > JDBC Driver to keep a backup of your configuration.
Hope this helps, sorry for the inconvenience caused, I’m afraid this is the first time this sort of issue has been reported and I cannot explain what would have caused this problem.
