[JBoss JIRA] (JBIDE-26569) Cannot create hibernate config file for hibernate 5.3 and 5.4
by Koen Aers (Jira)
[ https://issues.jboss.org/browse/JBIDE-26569?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-26569:
-----------------------------------
I am not sure how you import the above project. On my platform the import does not work and results in a stack trace (see the attached movie JBIDE-26569-import.mov). As a result, it is not recognized as a Java project and I cannot even start to create the cfg.xml files nor the console.
However, when I create the project from scratch and I copy all the elements, I get the same stack trace while copying the pom.xml but the project maintains the Java nature (see JBIDE-26569-copy-1.mov and JBIDE-26569-copy-2.mov).
But in this case, creating the hibernate.cfg.xml file and the hibernate console just works on my box! (see JBIDE-26569-console.mov).
[^JBIDE-26569-console.mov] [^JBIDE-26569-copy-1.mov] [^JBIDE-26569-copy-2.mov] [^JBIDE-26569-import.mov]
> Cannot create hibernate config file for hibernate 5.3 and 5.4
> -------------------------------------------------------------
>
> Key: JBIDE-26569
> URL: https://issues.jboss.org/browse/JBIDE-26569
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.11.0.Final
> Reporter: Josef Kopriva
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.12.0.Final
>
> Attachments: JBIDE-26569-console.mov, JBIDE-26569-copy-1.mov, JBIDE-26569-copy-2.mov, JBIDE-26569-import.mov, Screenshot 2019-04-11 15.26.00.png, image-2019-03-08-10-38-30-318.png
>
>
> This workflow works for Hibernate 5.2
> Error from error log:
> {code:java}
> eclipse.buildId=12.11.0.AM1-v20190221-1020-B4114
> java.version=11.0.2
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.ui
> Error
> Fri Mar 08 10:30:50 CET 2019
> Unhandled event loop exception
> org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:275)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:237)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
> at org.hibernate.id.factory.internal.DefaultIdentifierGeneratorFactory.injectServices(DefaultIdentifierGeneratorFactory.java:152)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.injectDependencies(AbstractServiceRegistryImpl.java:286)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:243)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
> at org.hibernate.boot.internal.InFlightMetadataCollectorImpl.<init>(InFlightMetadataCollectorImpl.java:179)
> at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:119)
> at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.build(MetadataBuildingProcess.java:84)
> at org.hibernate.boot.internal.MetadataBuilderImpl.build(MetadataBuilderImpl.java:474)
> at org.hibernate.boot.internal.MetadataBuilderImpl.build(MetadataBuilderImpl.java:85)
> at org.hibernate.boot.MetadataSources.buildMetadata(MetadataSources.java:184)
> at org.jboss.tools.hibernate.runtime.v_5_3.internal.util.MetadataHelper.buildFromMetadataSources(MetadataHelper.java:49)
> at org.jboss.tools.hibernate.runtime.v_5_3.internal.util.MetadataHelper.getMetadata(MetadataHelper.java:21)
> at org.jboss.tools.hibernate.runtime.v_5_3.internal.ConfigurationFacadeImpl.getMetadata(ConfigurationFacadeImpl.java:174)
> at org.jboss.tools.hibernate.runtime.v_5_3.internal.util.ConfigurationMetadataDescriptor.createMetadata(ConfigurationMetadataDescriptor.java:20)
> at org.hibernate.tool.hbm2x.AbstractExporter.buildMetadata(AbstractExporter.java:207)
> at org.hibernate.tool.hbm2x.AbstractExporter.getMetadata(AbstractExporter.java:57)
> at org.hibernate.tool.hbm2x.AbstractExporter.setupContext(AbstractExporter.java:178)
> at org.hibernate.tool.hbm2x.AbstractExporter.start(AbstractExporter.java:105)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.tools.hibernate.runtime.common.Util.invokeMethod(Util.java:43)
> at org.jboss.tools.hibernate.runtime.common.AbstractExporterFacade.start(AbstractExporterFacade.java:72)
> at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.openContentStream(NewConfigurationWizard.java:301)
> at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.access$2(NewConfigurationWizard.java:295)
> at org.hibernate.eclipse.console.wizards.NewConfigurationWizard$1.getInitialContents(NewConfigurationWizard.java:163)
> at org.eclipse.ui.dialogs.WizardNewFileCreationPage.createNewFile(WizardNewFileCreationPage.java:383)
> at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.performFinish(NewConfigurationWizard.java:198)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:775)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:414)
> at org.eclipse.jface.dialogs.Dialog.lambda$0(Dialog.java:622)
> at org.eclipse.swt.events.SelectionListener$1.widgetSelected(SelectionListener.java:84)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:252)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5663)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1386)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4931)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4472)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:822)
> at org.eclipse.jface.window.Window.open(Window.java:798)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:272)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:293)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:96)
> at jdk.internal.reflect.GeneratedMethodAccessor128.invoke(Unknown Source)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:320)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:254)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:164)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:156)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:497)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:490)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:403)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:154)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:568)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:400)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5663)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1386)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4931)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4472)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> 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(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1474)
> Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when 'hibernate.dialect' not set
> at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.determineDialect(DialectFactoryImpl.java:100)
> at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:54)
> at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:137)
> at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35)
> at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:94)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:263)
> ... 89 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26697) Possible memory leak during Loading projects job when using CRC
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26697?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-26697:
------------------------------------------
Given that steps say to repeatedly open the new application wizard, this could be a problem of keeping references to the templates.
> Possible memory leak during Loading projects job when using CRC
> ---------------------------------------------------------------
>
> Key: JBIDE-26697
> URL: https://issues.jboss.org/browse/JBIDE-26697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.12.0.Final
> Environment: Mac 10.14.5 (18F203), Fedora 29, crstudio GA-v20190626-0604-B4591
> Reporter: Josef Kopriva
> Priority: Blocker
>
> Exception in error log:
> {code:java}
> eclipse.buildId=12.12.0.GA-v20190626-0604-B4591
> java.version=11.0.2
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_GB
> Framework arguments: -product com.jboss.devstudio.core.product -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.devstudio.core.product -data file:/Users/jkopriva/workspace_B4591_3/ -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> org.eclipse.core.jobs
> Error
> Wed Jun 26 14:36:11 CEST 2019
> An internal error occurred during: "Loading projects...".
> java.lang.OutOfMemoryError: Java heap space
> at org.jboss.dmr.JSONParser.yyParse(JSONParser.java:877)
> at org.jboss.dmr.ModelNode.fromJSONString(ModelNode.java:1472)
> at com.openshift.internal.restclient.ResourceFactory.create(ResourceFactory.java:100)
> at com.openshift.internal.restclient.ResourceFactory.createInstanceFrom(ResourceFactory.java:149)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:304)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:275)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:264)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:171)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:160)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:151)
> at com.openshift.internal.restclient.capability.resources.ProjectTemplateListCapability.getCommonTemplates(ProjectTemplateListCapability.java:53)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceTreeItems$1.visit(ApplicationSourceTreeItems.java:121)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceTreeItems$1.visit(ApplicationSourceTreeItems.java:1)
> at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:94)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceTreeItems.loadTemplates(ApplicationSourceTreeItems.java:113)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceTreeItems.createChildren(ApplicationSourceTreeItems.java:61)
> at org.jboss.tools.openshift.internal.ui.treeitem.ObservableTreeItem.loadChildren(ObservableTreeItem.java:69)
> at org.jboss.tools.openshift.internal.ui.treeitem.ObservableTreeItem.load(ObservableTreeItem.java:56)
> at org.jboss.tools.openshift.internal.ui.treeitem.ObservableTreeItem.load(ObservableTreeItem.java:59)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.loadResources(NewApplicationWizardModel.java:247)
> at org.jboss.tools.openshift.internal.ui.wizard.common.AbstractProjectPage$3.doRun(AbstractProjectPage.java:255)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26697) Possible memory leak during Loading projects job when using CRC
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26697?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26697:
-------------------------------------
Comment: was deleted
(was: [~jkopriva] Looking at the stacktrace this seems to happen when the available templates are loaded. You seem to say that it can also happen when listing the projects?)
> Possible memory leak during Loading projects job when using CRC
> ---------------------------------------------------------------
>
> Key: JBIDE-26697
> URL: https://issues.jboss.org/browse/JBIDE-26697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.12.0.Final
> Environment: Mac 10.14.5 (18F203), Fedora 29, crstudio GA-v20190626-0604-B4591
> Reporter: Josef Kopriva
> Priority: Blocker
>
> Exception in error log:
> {code:java}
> eclipse.buildId=12.12.0.GA-v20190626-0604-B4591
> java.version=11.0.2
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_GB
> Framework arguments: -product com.jboss.devstudio.core.product -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.devstudio.core.product -data file:/Users/jkopriva/workspace_B4591_3/ -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> org.eclipse.core.jobs
> Error
> Wed Jun 26 14:36:11 CEST 2019
> An internal error occurred during: "Loading projects...".
> java.lang.OutOfMemoryError: Java heap space
> at org.jboss.dmr.JSONParser.yyParse(JSONParser.java:877)
> at org.jboss.dmr.ModelNode.fromJSONString(ModelNode.java:1472)
> at com.openshift.internal.restclient.ResourceFactory.create(ResourceFactory.java:100)
> at com.openshift.internal.restclient.ResourceFactory.createInstanceFrom(ResourceFactory.java:149)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:304)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:275)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:264)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:171)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:160)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:151)
> at com.openshift.internal.restclient.capability.resources.ProjectTemplateListCapability.getCommonTemplates(ProjectTemplateListCapability.java:53)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceTreeItems$1.visit(ApplicationSourceTreeItems.java:121)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceTreeItems$1.visit(ApplicationSourceTreeItems.java:1)
> at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:94)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceTreeItems.loadTemplates(ApplicationSourceTreeItems.java:113)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceTreeItems.createChildren(ApplicationSourceTreeItems.java:61)
> at org.jboss.tools.openshift.internal.ui.treeitem.ObservableTreeItem.loadChildren(ObservableTreeItem.java:69)
> at org.jboss.tools.openshift.internal.ui.treeitem.ObservableTreeItem.load(ObservableTreeItem.java:56)
> at org.jboss.tools.openshift.internal.ui.treeitem.ObservableTreeItem.load(ObservableTreeItem.java:59)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.loadResources(NewApplicationWizardModel.java:247)
> at org.jboss.tools.openshift.internal.ui.wizard.common.AbstractProjectPage$3.doRun(AbstractProjectPage.java:255)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26697) Possible memory leak during Loading projects job when using CRC
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26697?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-26697:
------------------------------------------
[~jkopriva] Looking at the stacktrace this seems to happen when the available templates are loaded. You seem to say that it can also happen when listing the projects?
> Possible memory leak during Loading projects job when using CRC
> ---------------------------------------------------------------
>
> Key: JBIDE-26697
> URL: https://issues.jboss.org/browse/JBIDE-26697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.12.0.Final
> Environment: Mac 10.14.5 (18F203), Fedora 29, crstudio GA-v20190626-0604-B4591
> Reporter: Josef Kopriva
> Priority: Blocker
>
> Exception in error log:
> {code:java}
> eclipse.buildId=12.12.0.GA-v20190626-0604-B4591
> java.version=11.0.2
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_GB
> Framework arguments: -product com.jboss.devstudio.core.product -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.devstudio.core.product -data file:/Users/jkopriva/workspace_B4591_3/ -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> org.eclipse.core.jobs
> Error
> Wed Jun 26 14:36:11 CEST 2019
> An internal error occurred during: "Loading projects...".
> java.lang.OutOfMemoryError: Java heap space
> at org.jboss.dmr.JSONParser.yyParse(JSONParser.java:877)
> at org.jboss.dmr.ModelNode.fromJSONString(ModelNode.java:1472)
> at com.openshift.internal.restclient.ResourceFactory.create(ResourceFactory.java:100)
> at com.openshift.internal.restclient.ResourceFactory.createInstanceFrom(ResourceFactory.java:149)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:304)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:275)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:264)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:171)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:160)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:151)
> at com.openshift.internal.restclient.capability.resources.ProjectTemplateListCapability.getCommonTemplates(ProjectTemplateListCapability.java:53)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceTreeItems$1.visit(ApplicationSourceTreeItems.java:121)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceTreeItems$1.visit(ApplicationSourceTreeItems.java:1)
> at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:94)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceTreeItems.loadTemplates(ApplicationSourceTreeItems.java:113)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceTreeItems.createChildren(ApplicationSourceTreeItems.java:61)
> at org.jboss.tools.openshift.internal.ui.treeitem.ObservableTreeItem.loadChildren(ObservableTreeItem.java:69)
> at org.jboss.tools.openshift.internal.ui.treeitem.ObservableTreeItem.load(ObservableTreeItem.java:56)
> at org.jboss.tools.openshift.internal.ui.treeitem.ObservableTreeItem.load(ObservableTreeItem.java:59)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.loadResources(NewApplicationWizardModel.java:247)
> at org.jboss.tools.openshift.internal.ui.wizard.common.AbstractProjectPage$3.doRun(AbstractProjectPage.java:255)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26697) Possible memory leak during Loading projects job when using CRC
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26697?page=com.atlassian.jira.plugi... ]
Josef Kopriva commented on JBIDE-26697:
---------------------------------------
[~adietish] I was able to reproduce it with CRC and OpenShift4 cluster. I suppose other way to verify it is to create a lot namespaces with application in openshift cluster.
> Possible memory leak during Loading projects job when using CRC
> ---------------------------------------------------------------
>
> Key: JBIDE-26697
> URL: https://issues.jboss.org/browse/JBIDE-26697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.12.0.Final
> Environment: Mac 10.14.5 (18F203), Fedora 29, crstudio GA-v20190626-0604-B4591
> Reporter: Josef Kopriva
> Priority: Blocker
>
> Exception in error log:
> {code:java}
> eclipse.buildId=12.12.0.GA-v20190626-0604-B4591
> java.version=11.0.2
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_GB
> Framework arguments: -product com.jboss.devstudio.core.product -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.devstudio.core.product -data file:/Users/jkopriva/workspace_B4591_3/ -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> org.eclipse.core.jobs
> Error
> Wed Jun 26 14:36:11 CEST 2019
> An internal error occurred during: "Loading projects...".
> java.lang.OutOfMemoryError: Java heap space
> at org.jboss.dmr.JSONParser.yyParse(JSONParser.java:877)
> at org.jboss.dmr.ModelNode.fromJSONString(ModelNode.java:1472)
> at com.openshift.internal.restclient.ResourceFactory.create(ResourceFactory.java:100)
> at com.openshift.internal.restclient.ResourceFactory.createInstanceFrom(ResourceFactory.java:149)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:304)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:275)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:264)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:171)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:160)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:151)
> at com.openshift.internal.restclient.capability.resources.ProjectTemplateListCapability.getCommonTemplates(ProjectTemplateListCapability.java:53)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceTreeItems$1.visit(ApplicationSourceTreeItems.java:121)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceTreeItems$1.visit(ApplicationSourceTreeItems.java:1)
> at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:94)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceTreeItems.loadTemplates(ApplicationSourceTreeItems.java:113)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceTreeItems.createChildren(ApplicationSourceTreeItems.java:61)
> at org.jboss.tools.openshift.internal.ui.treeitem.ObservableTreeItem.loadChildren(ObservableTreeItem.java:69)
> at org.jboss.tools.openshift.internal.ui.treeitem.ObservableTreeItem.load(ObservableTreeItem.java:56)
> at org.jboss.tools.openshift.internal.ui.treeitem.ObservableTreeItem.load(ObservableTreeItem.java:59)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.loadResources(NewApplicationWizardModel.java:247)
> at org.jboss.tools.openshift.internal.ui.wizard.common.AbstractProjectPage$3.doRun(AbstractProjectPage.java:255)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26569) Cannot create hibernate config file for hibernate 5.3 and 5.4
by Koen Aers (Jira)
[ https://issues.jboss.org/browse/JBIDE-26569?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-26569:
------------------------------
Attachment: (was: JBIDE-26569-import.mov)
> Cannot create hibernate config file for hibernate 5.3 and 5.4
> -------------------------------------------------------------
>
> Key: JBIDE-26569
> URL: https://issues.jboss.org/browse/JBIDE-26569
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.11.0.Final
> Reporter: Josef Kopriva
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.12.0.Final
>
> Attachments: Screenshot 2019-04-11 15.26.00.png, image-2019-03-08-10-38-30-318.png
>
>
> This workflow works for Hibernate 5.2
> Error from error log:
> {code:java}
> eclipse.buildId=12.11.0.AM1-v20190221-1020-B4114
> java.version=11.0.2
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.ui
> Error
> Fri Mar 08 10:30:50 CET 2019
> Unhandled event loop exception
> org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:275)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:237)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
> at org.hibernate.id.factory.internal.DefaultIdentifierGeneratorFactory.injectServices(DefaultIdentifierGeneratorFactory.java:152)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.injectDependencies(AbstractServiceRegistryImpl.java:286)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:243)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
> at org.hibernate.boot.internal.InFlightMetadataCollectorImpl.<init>(InFlightMetadataCollectorImpl.java:179)
> at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:119)
> at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.build(MetadataBuildingProcess.java:84)
> at org.hibernate.boot.internal.MetadataBuilderImpl.build(MetadataBuilderImpl.java:474)
> at org.hibernate.boot.internal.MetadataBuilderImpl.build(MetadataBuilderImpl.java:85)
> at org.hibernate.boot.MetadataSources.buildMetadata(MetadataSources.java:184)
> at org.jboss.tools.hibernate.runtime.v_5_3.internal.util.MetadataHelper.buildFromMetadataSources(MetadataHelper.java:49)
> at org.jboss.tools.hibernate.runtime.v_5_3.internal.util.MetadataHelper.getMetadata(MetadataHelper.java:21)
> at org.jboss.tools.hibernate.runtime.v_5_3.internal.ConfigurationFacadeImpl.getMetadata(ConfigurationFacadeImpl.java:174)
> at org.jboss.tools.hibernate.runtime.v_5_3.internal.util.ConfigurationMetadataDescriptor.createMetadata(ConfigurationMetadataDescriptor.java:20)
> at org.hibernate.tool.hbm2x.AbstractExporter.buildMetadata(AbstractExporter.java:207)
> at org.hibernate.tool.hbm2x.AbstractExporter.getMetadata(AbstractExporter.java:57)
> at org.hibernate.tool.hbm2x.AbstractExporter.setupContext(AbstractExporter.java:178)
> at org.hibernate.tool.hbm2x.AbstractExporter.start(AbstractExporter.java:105)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.tools.hibernate.runtime.common.Util.invokeMethod(Util.java:43)
> at org.jboss.tools.hibernate.runtime.common.AbstractExporterFacade.start(AbstractExporterFacade.java:72)
> at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.openContentStream(NewConfigurationWizard.java:301)
> at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.access$2(NewConfigurationWizard.java:295)
> at org.hibernate.eclipse.console.wizards.NewConfigurationWizard$1.getInitialContents(NewConfigurationWizard.java:163)
> at org.eclipse.ui.dialogs.WizardNewFileCreationPage.createNewFile(WizardNewFileCreationPage.java:383)
> at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.performFinish(NewConfigurationWizard.java:198)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:775)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:414)
> at org.eclipse.jface.dialogs.Dialog.lambda$0(Dialog.java:622)
> at org.eclipse.swt.events.SelectionListener$1.widgetSelected(SelectionListener.java:84)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:252)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5663)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1386)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4931)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4472)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:822)
> at org.eclipse.jface.window.Window.open(Window.java:798)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:272)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:293)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:96)
> at jdk.internal.reflect.GeneratedMethodAccessor128.invoke(Unknown Source)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:320)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:254)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:164)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:156)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:497)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:490)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:403)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:154)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:568)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:400)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5663)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1386)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4931)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4472)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> 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(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1474)
> Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when 'hibernate.dialect' not set
> at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.determineDialect(DialectFactoryImpl.java:100)
> at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:54)
> at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:137)
> at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35)
> at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:94)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:263)
> ... 89 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26699) Server adapter: should error if port forwarding fails
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26699?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26699:
-------------------------------------
Fix Version/s: 4.12.x
> Server adapter: should error if port forwarding fails
> -----------------------------------------------------
>
> Key: JBIDE-26699
> URL: https://issues.jboss.org/browse/JBIDE-26699
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.12.0.AM1
> Reporter: André Dietisheim
> Priority: Major
> Labels: port_forwarding, server_adapter
> Fix For: 4.12.x
>
>
> *Steps:*
> # ASSERT: have a crc cluster installed where you didnt approve the certificates: https://github.com/code-ready/crc/issues/218#issuecomment-501099558
> # ASSERT: have an app (with a pod) running
> # EXEC: create a server adapter for it and start it
> # ASSERT: syncing fails
> {code}
> OpenShiftBinaryCapability process exited: WARNING: cannot use rsync: rsync not available in container
> WARNING: cannot use tar: tar not available in container
> error: No available strategies to copy.
> {code}
> {code}
> Could not sync folder /Users/jkopriva/workspace_4589/.metadata/.plugins/org.jboss.ide.eclipse.as.core/123@eap-app/deploy to all pods.
> {code}
> # EXEC: check if the port forwarding for the pod (of your app) is "Started"
> *Result*:
> The port forwarding for your pod is "Stopped". If you try to start it it'll fail with the error
> {code}
> OpenShiftBinaryCapability process exited: error: error upgrading connection: error dialing backend: remote error: tls: internal error
> {code}
> *Expected result*:
> Starting the server adapter should fail and notify that the port forwarding failed. Currently only the next step where syncing is attempted fails.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26699) Server adapter: should error if port forwarding fails
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26699?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26699:
-------------------------------------
Description:
steps:
# ASSERT: have a crc cluster installed where you didnt approve the certificates: https://github.com/code-ready/crc/issues/218#issuecomment-501099558
# ASSERT: have an app (with a pod) running
# EXEC: create a server adapter for it and start it
# ASSERT: syncing fails
{code}
OpenShiftBinaryCapability process exited: WARNING: cannot use rsync: rsync not available in container
WARNING: cannot use tar: tar not available in container
error: No available strategies to copy.
{code}
{code}
Could not sync folder /Users/jkopriva/workspace_4589/.metadata/.plugins/org.jboss.ide.eclipse.as.core/123@eap-app/deploy to all pods.
{code}
# EXEC: check if the port forwarding for the pod (of your app) is "Started"
*Result*:
The port forwarding for your pod is "Stopped". If you try to start it it'll fail with the error
{code}
OpenShiftBinaryCapability process exited: error: error upgrading connection: error dialing backend: remote error: tls: internal error
{code}
*Expected result*:
Starting the server adapter should fail and notify that the port forwarding failed. Currently only the next step where syncing is attempted fails.
was:
steps:
# ASSERT: have a crc cluster installed where you didnt approve the certificates: https://github.com/code-ready/crc/issues/218#issuecomment-501099558
# ASSERT: have an app (with a pod) running
# EXEC: create a server adapter for it and start it
# ASSERT: syncing fails
{code}
OpenShiftBinaryCapability process exited: WARNING: cannot use rsync: rsync not available in container
WARNING: cannot use tar: tar not available in container
error: No available strategies to copy.
{code}
{code}
Could not sync folder /Users/jkopriva/workspace_4589/.metadata/.plugins/org.jboss.ide.eclipse.as.core/123@eap-app/deploy to all pods.
{code}
# EXEC: check if the port forwarding for the pod (of your app) is "Started"
Result:
The port forwarding for your pod is "Stopped". If you try to start it it'll fail with the error
{code}
OpenShiftBinaryCapability process exited: error: error upgrading connection: error dialing backend: remote error: tls: internal error
{code}
Expected result:
Starting the server adapter should fail and notify that the port forwarding failed. Currently only the next step where syncing is attempted fails.
> Server adapter: should error if port forwarding fails
> -----------------------------------------------------
>
> Key: JBIDE-26699
> URL: https://issues.jboss.org/browse/JBIDE-26699
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.12.0.AM1
> Reporter: André Dietisheim
> Priority: Major
> Labels: port_forwarding, server_adapter
>
> steps:
> # ASSERT: have a crc cluster installed where you didnt approve the certificates: https://github.com/code-ready/crc/issues/218#issuecomment-501099558
> # ASSERT: have an app (with a pod) running
> # EXEC: create a server adapter for it and start it
> # ASSERT: syncing fails
> {code}
> OpenShiftBinaryCapability process exited: WARNING: cannot use rsync: rsync not available in container
> WARNING: cannot use tar: tar not available in container
> error: No available strategies to copy.
> {code}
> {code}
> Could not sync folder /Users/jkopriva/workspace_4589/.metadata/.plugins/org.jboss.ide.eclipse.as.core/123@eap-app/deploy to all pods.
> {code}
> # EXEC: check if the port forwarding for the pod (of your app) is "Started"
> *Result*:
> The port forwarding for your pod is "Stopped". If you try to start it it'll fail with the error
> {code}
> OpenShiftBinaryCapability process exited: error: error upgrading connection: error dialing backend: remote error: tls: internal error
> {code}
> *Expected result*:
> Starting the server adapter should fail and notify that the port forwarding failed. Currently only the next step where syncing is attempted fails.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26699) Server adapter: should error if port forwarding fails
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26699?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26699:
-------------------------------------
Description:
*Steps:*
# ASSERT: have a crc cluster installed where you didnt approve the certificates: https://github.com/code-ready/crc/issues/218#issuecomment-501099558
# ASSERT: have an app (with a pod) running
# EXEC: create a server adapter for it and start it
# ASSERT: syncing fails
{code}
OpenShiftBinaryCapability process exited: WARNING: cannot use rsync: rsync not available in container
WARNING: cannot use tar: tar not available in container
error: No available strategies to copy.
{code}
{code}
Could not sync folder /Users/jkopriva/workspace_4589/.metadata/.plugins/org.jboss.ide.eclipse.as.core/123@eap-app/deploy to all pods.
{code}
# EXEC: check if the port forwarding for the pod (of your app) is "Started"
*Result*:
The port forwarding for your pod is "Stopped". If you try to start it it'll fail with the error
{code}
OpenShiftBinaryCapability process exited: error: error upgrading connection: error dialing backend: remote error: tls: internal error
{code}
*Expected result*:
Starting the server adapter should fail and notify that the port forwarding failed. Currently only the next step where syncing is attempted fails.
was:
steps:
# ASSERT: have a crc cluster installed where you didnt approve the certificates: https://github.com/code-ready/crc/issues/218#issuecomment-501099558
# ASSERT: have an app (with a pod) running
# EXEC: create a server adapter for it and start it
# ASSERT: syncing fails
{code}
OpenShiftBinaryCapability process exited: WARNING: cannot use rsync: rsync not available in container
WARNING: cannot use tar: tar not available in container
error: No available strategies to copy.
{code}
{code}
Could not sync folder /Users/jkopriva/workspace_4589/.metadata/.plugins/org.jboss.ide.eclipse.as.core/123@eap-app/deploy to all pods.
{code}
# EXEC: check if the port forwarding for the pod (of your app) is "Started"
*Result*:
The port forwarding for your pod is "Stopped". If you try to start it it'll fail with the error
{code}
OpenShiftBinaryCapability process exited: error: error upgrading connection: error dialing backend: remote error: tls: internal error
{code}
*Expected result*:
Starting the server adapter should fail and notify that the port forwarding failed. Currently only the next step where syncing is attempted fails.
> Server adapter: should error if port forwarding fails
> -----------------------------------------------------
>
> Key: JBIDE-26699
> URL: https://issues.jboss.org/browse/JBIDE-26699
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.12.0.AM1
> Reporter: André Dietisheim
> Priority: Major
> Labels: port_forwarding, server_adapter
>
> *Steps:*
> # ASSERT: have a crc cluster installed where you didnt approve the certificates: https://github.com/code-ready/crc/issues/218#issuecomment-501099558
> # ASSERT: have an app (with a pod) running
> # EXEC: create a server adapter for it and start it
> # ASSERT: syncing fails
> {code}
> OpenShiftBinaryCapability process exited: WARNING: cannot use rsync: rsync not available in container
> WARNING: cannot use tar: tar not available in container
> error: No available strategies to copy.
> {code}
> {code}
> Could not sync folder /Users/jkopriva/workspace_4589/.metadata/.plugins/org.jboss.ide.eclipse.as.core/123@eap-app/deploy to all pods.
> {code}
> # EXEC: check if the port forwarding for the pod (of your app) is "Started"
> *Result*:
> The port forwarding for your pod is "Stopped". If you try to start it it'll fail with the error
> {code}
> OpenShiftBinaryCapability process exited: error: error upgrading connection: error dialing backend: remote error: tls: internal error
> {code}
> *Expected result*:
> Starting the server adapter should fail and notify that the port forwarding failed. Currently only the next step where syncing is attempted fails.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26699) Server adapter: should error if port forwarding fails
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26699?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26699:
-------------------------------------
Description:
steps:
# ASSERT: have a crc cluster installed where you didnt approve the certificates: https://github.com/code-ready/crc/issues/218#issuecomment-501099558
# ASSERT: have an app (with a pod) running
# EXEC: create a server adapter for it and start it
# ASSERT: syncing fails
{code}
OpenShiftBinaryCapability process exited: WARNING: cannot use rsync: rsync not available in container
WARNING: cannot use tar: tar not available in container
error: No available strategies to copy.
{code}
{code}
Could not sync folder /Users/jkopriva/workspace_4589/.metadata/.plugins/org.jboss.ide.eclipse.as.core/123@eap-app/deploy to all pods.
{code}
# EXEC: check if the port forwarding for the pod (of your app) is "Started"
Result:
The port forwarding for your pod is "Stopped". If you try to start it it'll fail with the error
{code}
OpenShiftBinaryCapability process exited: error: error upgrading connection: error dialing backend: remote error: tls: internal error
{code}
Expected result:
Starting the server adapter should fail and notify that the port forwarding failed. Currently only the next step where syncing is attempted fails.
was:
steps:
# ASSERT: have a crc cluster installed where you didnt approve the certificates: https://github.com/code-ready/crc/issues/218#issuecomment-501099558
# ASSERT: have an app (with a pod) running
# EXEC: create a server adapter for it and start it
# ASSERT: syncing fails
{code}
Could not sync folder /Users/jkopriva/workspace_4589/.metadata/.plugins/org.jboss.ide.eclipse.as.core/123@eap-app/deploy to all pods.
{code}
# EXEC: check if the port forwarding for the pod (of your app) is "Started"
Result:
The port forwarding for your pod is "Stopped". If you try to start it it'll fail with the error
{code}
OpenShiftBinaryCapability process exited: error: error upgrading connection: error dialing backend: remote error: tls: internal error
{code}
Expected result:
Starting the server adapter should fail and notify that the port forwarding failed. Currently only the next step where syncing is attempted fails.
> Server adapter: should error if port forwarding fails
> -----------------------------------------------------
>
> Key: JBIDE-26699
> URL: https://issues.jboss.org/browse/JBIDE-26699
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.12.0.AM1
> Reporter: André Dietisheim
> Priority: Major
> Labels: port_forwarding, server_adapter
>
> steps:
> # ASSERT: have a crc cluster installed where you didnt approve the certificates: https://github.com/code-ready/crc/issues/218#issuecomment-501099558
> # ASSERT: have an app (with a pod) running
> # EXEC: create a server adapter for it and start it
> # ASSERT: syncing fails
> {code}
> OpenShiftBinaryCapability process exited: WARNING: cannot use rsync: rsync not available in container
> WARNING: cannot use tar: tar not available in container
> error: No available strategies to copy.
> {code}
> {code}
> Could not sync folder /Users/jkopriva/workspace_4589/.metadata/.plugins/org.jboss.ide.eclipse.as.core/123@eap-app/deploy to all pods.
> {code}
> # EXEC: check if the port forwarding for the pod (of your app) is "Started"
> Result:
> The port forwarding for your pod is "Stopped". If you try to start it it'll fail with the error
> {code}
> OpenShiftBinaryCapability process exited: error: error upgrading connection: error dialing backend: remote error: tls: internal error
> {code}
> Expected result:
> Starting the server adapter should fail and notify that the port forwarding failed. Currently only the next step where syncing is attempted fails.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months