[JBoss JIRA] (JBIDE-26869) CRC server adapter: OpenShift connection that is created is unusable at times
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26869?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-26869 at 10/22/19 6:30 PM:
--------------------------------------------------------------------
PR https://github.com/jbosstools/jbosstools-openshift/pull/1884 fixes this issue and also JBIDE-26899
was (Author: adietish):
PR https://github.com/jbosstools/jbosstools-openshift/pull/1884 seems to fix this issue and also JBIDE-26899
> CRC server adapter: OpenShift connection that is created is unusable at times
> -----------------------------------------------------------------------------
>
> Key: JBIDE-26869
> URL: https://issues.jboss.org/browse/JBIDE-26869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Environment: CRC Beta5
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Critical
> Fix For: 4.13.0.Final
>
> Attachments: crc-connection-error.mp4, start-crc-error-openshift-conn.mp4
>
>
> *Steps* - not reproducibe at 100%, happens from time to time:
> # ASSERT: have ~/.crc folder killed
> # EXEC: create new CRC server adapter & Start it
> # ASSERT: OpenShift connection is created
> *Result:*
> Connection fails to authorize, reports that it cannot access resources using system:anonymous. Refreshing the connection doesn't help, so it's apparently not a timing issue (ex. creating the connection before the cluster is fully up and running)
> {code}
> com.openshift.restclient.authorization.ResourceForbiddenException: forbidden: User "system:anonymous" cannot get path "/oauth/authorize" forbidden: User "system:anonymous" cannot get path "/oauth/authorize"
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:111)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:66)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.kt:184)
> at okhttp3.RealCall.execute(RealCall.kt:66)
> at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator.tryAuth(OpenShiftAuthenticator.java:109)
> at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator.authenticate(OpenShiftAuthenticator.java:62)
> at okhttp3.internal.http.RetryAndFollowUpInterceptor.followUpRequest(RetryAndFollowUpInterceptor.kt:213)
> at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:102)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:55)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.kt:184)
> at okhttp3.RealCall.execute(RealCall.kt:66)
> at com.openshift.internal.restclient.DefaultClient.request(DefaultClient.java:315)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:307)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:275)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:243)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:226)
> at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:423)
> at com.openshift.internal.restclient.authorization.AuthorizationContext.isAuthorized(AuthorizationContext.java:63)
> at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:237)
> at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226)
> at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener.configureOpenshift(ConfigureCRCFrameworksListener.java:102)
> at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener.configureFrameworks(ConfigureCRCFrameworksListener.java:73)
> at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener$1.run(ConfigureCRCFrameworksListener.java:66)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (JBIDE-26869) CRC server adapter: OpenShift connection that is created is unusable at times
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26869?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26869:
-------------------------------------
Comment: was deleted
(was: PR https://github.com/jbosstools/jbosstools-openshift/pull/1884 fixes this issue and also JBIDE-26899)
> CRC server adapter: OpenShift connection that is created is unusable at times
> -----------------------------------------------------------------------------
>
> Key: JBIDE-26869
> URL: https://issues.jboss.org/browse/JBIDE-26869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Environment: CRC Beta5
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Critical
> Fix For: 4.13.0.Final
>
> Attachments: crc-connection-error.mp4, start-crc-error-openshift-conn.mp4
>
>
> *Steps* - not reproducibe at 100%, happens from time to time:
> # ASSERT: have ~/.crc folder killed
> # EXEC: create new CRC server adapter & Start it
> # ASSERT: OpenShift connection is created
> *Result:*
> Connection fails to authorize, reports that it cannot access resources using system:anonymous. Refreshing the connection doesn't help, so it's apparently not a timing issue (ex. creating the connection before the cluster is fully up and running)
> {code}
> com.openshift.restclient.authorization.ResourceForbiddenException: forbidden: User "system:anonymous" cannot get path "/oauth/authorize" forbidden: User "system:anonymous" cannot get path "/oauth/authorize"
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:111)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:66)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.kt:184)
> at okhttp3.RealCall.execute(RealCall.kt:66)
> at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator.tryAuth(OpenShiftAuthenticator.java:109)
> at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator.authenticate(OpenShiftAuthenticator.java:62)
> at okhttp3.internal.http.RetryAndFollowUpInterceptor.followUpRequest(RetryAndFollowUpInterceptor.kt:213)
> at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:102)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:55)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.kt:184)
> at okhttp3.RealCall.execute(RealCall.kt:66)
> at com.openshift.internal.restclient.DefaultClient.request(DefaultClient.java:315)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:307)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:275)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:243)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:226)
> at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:423)
> at com.openshift.internal.restclient.authorization.AuthorizationContext.isAuthorized(AuthorizationContext.java:63)
> at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:237)
> at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226)
> at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener.configureOpenshift(ConfigureCRCFrameworksListener.java:102)
> at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener.configureFrameworks(ConfigureCRCFrameworksListener.java:73)
> at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener$1.run(ConfigureCRCFrameworksListener.java:66)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (JBIDE-26899) Refreshing non-functional connection to CRC doesnt help (need to create new)
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26899?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26899:
-------------------------------------
Description:
*Steps* - not reproducibe at 100%, happens from time to time:
# ASSERT: have ~/.crc folder killed
# EXEC: create new CRC server adapter & Start it
# ASSERT: OpenShift connection is created
# ASSERT: Connection fails to authorize, reports that it cannot access resources using system:anonymous.
# EXEC: try to login with *oc login*. If oc reports *Error from server (InternalError): Internal error occurred: unexpected response: 400*, repeat until it succeeds (waiting required)
# EXEC: Once oc login succeeds: refresh the connection in Eclipse
Result:
Connecting still fails with the same error.
Expected result:
Refreshing the connection should succeed once the server is fully up and running and oc succeeds to log in.
# EXEC: edit the connection (ex. remove a character from username and add it back again)
Result:
Connecting succeeds
was:
*Steps* - not reproducibe at 100%, happens from time to time:
# ASSERT: have ~/.crc folder killed
# EXEC: create new CRC server adapter & Start it
# ASSERT: OpenShift connection is created
# ASSERT: Connection fails to authorize, reports that it cannot access resources using system:anonymous.
# EXEC: try to login with *oc login*. If oc reports *Error from server (InternalError): Internal error occurred: unexpected response: 400*, repeat until it succeeds (waiting required)
# EXEC: Once oc login succeeds: refresh the connection in Eclipse
Result:
Connecting still fails with the same error.
Expected result:
Refreshing the connection should succeed once the server is fully up and running and oc succeeds to log in.
# EXEC: edit the connection (ex. remove a character from username and add it back again)
Result:
Connecting succeeds
> Refreshing non-functional connection to CRC doesnt help (need to create new)
> ----------------------------------------------------------------------------
>
> Key: JBIDE-26899
> URL: https://issues.jboss.org/browse/JBIDE-26899
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.Final
> Environment: CRC
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Major
> Fix For: 4.13.0.Final
>
>
> *Steps* - not reproducibe at 100%, happens from time to time:
> # ASSERT: have ~/.crc folder killed
> # EXEC: create new CRC server adapter & Start it
> # ASSERT: OpenShift connection is created
> # ASSERT: Connection fails to authorize, reports that it cannot access resources using system:anonymous.
> # EXEC: try to login with *oc login*. If oc reports *Error from server (InternalError): Internal error occurred: unexpected response: 400*, repeat until it succeeds (waiting required)
> # EXEC: Once oc login succeeds: refresh the connection in Eclipse
> Result:
> Connecting still fails with the same error.
> Expected result:
> Refreshing the connection should succeed once the server is fully up and running and oc succeeds to log in.
> # EXEC: edit the connection (ex. remove a character from username and add it back again)
> Result:
> Connecting succeeds
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (JBIDE-26663) Error occured while running bean post processors after import Spring Starter Project
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26663?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka closed JBIDE-26663.
-----------------------------------
*Tested in the newest RHCRS, I am closing this JIRA.*
h2. Red Hat CodeReady Studio version:
Version: 12.13.0.GA
Build id: GA-v20191022-0239-B5197
Build date: 20191022-0239
> Error occured while running bean post processors after import Spring Starter Project
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-26663
> URL: https://issues.jboss.org/browse/JBIDE-26663
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.12.0.AM1
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 4.13.0.Final
>
>
> After import there is an error in error log:
> {code:java}
> null
> org.springframework.ide.eclipse.beans.core
> Warning
> Mon Jun 10 09:00:00 CEST 2019
> Error occured while running bean post processors
> java.lang.IllegalStateException: Error processing condition on org.springframework.boot.autoconfigure.cache.CacheAutoConfiguration
> at org.springframework.boot.autoconfigure.condition.SpringBootCondition.matches(SpringBootCondition.java:64)
> at org.springframework.context.annotation.ConditionEvaluator.shouldSkip(ConditionEvaluator.java:102)
> at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader$TrackedConditionEvaluator.shouldSkip(ConfigurationClassBeanDefinitionReader.java:444)
> at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader$TrackedConditionEvaluator.shouldSkip(ConfigurationClassBeanDefinitionReader.java:433)
> at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitionsForConfigurationClass(ConfigurationClassBeanDefinitionReader.java:127)
> at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitions(ConfigurationClassBeanDefinitionReader.java:116)
> at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:320)
> at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:88)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$3.run(BeansJavaConfig.java:332)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig.executePostProcessor(BeansJavaConfig.java:321)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig.access$5(BeansJavaConfig.java:319)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$2.call(BeansJavaConfig.java:233)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$2.call(BeansJavaConfig.java:1)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.boot.autoconfigure.condition.BeanTypeRegistry': Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.autoconfigure.condition.BeanTypeRegistry]: No default constructor found; nested exception is java.lang.NoSuchMethodException: org.springframework.boot.autoconfigure.condition.BeanTypeRegistry.<init>()
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1159)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1103)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:511)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:481)
> at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:312)
> at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
> at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:308)
> at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
> at org.springframework.boot.autoconfigure.condition.BeanTypeRegistry.get(BeanTypeRegistry.java:369)
> at org.springframework.boot.autoconfigure.condition.OnBeanCondition.collectBeanNamesForType(OnBeanCondition.java:297)
> at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getBeanNamesForType(OnBeanCondition.java:289)
> at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getBeanNamesForType(OnBeanCondition.java:278)
> at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getMatchingBeans(OnBeanCondition.java:189)
> at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getMatchOutcome(OnBeanCondition.java:125)
> at org.springframework.boot.autoconfigure.condition.SpringBootCondition.matches(SpringBootCondition.java:47)
> ... 19 more
> Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.autoconfigure.condition.BeanTypeRegistry]: No default constructor found; nested exception is java.lang.NoSuchMethodException: org.springframework.boot.autoconfigure.condition.BeanTypeRegistry.<init>()
> at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:85)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1151)
> ... 33 more
> Caused by: java.lang.NoSuchMethodException: org.springframework.boot.autoconfigure.condition.BeanTypeRegistry.<init>()
> at java.base/java.lang.Class.getConstructor0(Class.java:3350)
> at java.base/java.lang.Class.getDeclaredConstructor(Class.java:2554)
> at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:80)
> ... 34 more
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (JBIDE-26311) EAP 7.1 and 7.2 fails to stop when connected over ssh
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26311?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-26311:
----------------------------------
Summary: EAP 7.1 and 7.2 fails to stop when connected over ssh (was: EAP 7.1 fails to stop when connected over ssh)
> EAP 7.1 and 7.2 fails to stop when connected over ssh
> -----------------------------------------------------
>
> Key: JBIDE-26311
> URL: https://issues.jboss.org/browse/JBIDE-26311
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.9.0.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Major
> Labels: regression
> Fix For: 4.14.x
>
> Attachments: JBIDE-26311.local.ogv
>
>
> I have an EAP 7.1 setup up over ssh. It's running on my localhost, so it's the most basic test of an ssh server. When I click the stop button on the server, it says:
> Server Red Hat JBoss EAP 7.1 ssh failed to stop.
> An exception stack trace is not available.
> It will stop on second attempt. On a local server this would mean killing the server java process. I'm not sure exactly what happens on a remote server, but it works.
> I'm pretty sure this worked last time (previous milestone).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (JBIDE-23666) Update or remove quickstarts on Central Home Page
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-23666?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka closed JBIDE-23666.
-----------------------------------
> Update or remove quickstarts on Central Home Page
> -------------------------------------------------
>
> Key: JBIDE-23666
> URL: https://issues.jboss.org/browse/JBIDE-23666
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.4.3.AM1
> Environment: Red Hat JBoss Developer Studio
> Version: 10.3.0.AM1
> Build id: AM1-v20161225-1238-B6761
> Build date: 20161225-1238
> Reporter: Josef Kopriva
> Assignee: André Dietisheim
> Priority: Critical
> Fix For: 4.13.0.Final
>
> Attachments: central-wizards.png
>
>
> Quickstarts on Central home page are old(links: "HTML5 Project", "AngularJS Forge", "Java EE Web Project"), so when importing these quickstarts, multiple warnings occur:
> {code:java}
> Description Resource Path Location Type
> Build path specifies execution environment JavaSE-1.6. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-as-kitchensink-html5-mobile Build path JRE System Library Problem
> Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-forge-html5 Build path JRE System Library Problem
> Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-javaee-webapp Build path JRE System Library Problem
> No connection specified for project. No database-specific validation will be performed. jboss-as-kitchensink-html5-mobile JPA Problem
> No connection specified for project. No database-specific validation will be performed. jboss-forge-html5 JPA Problem
> No connection specified for project. No database-specific validation will be performed. jboss-javaee-webapp JPA Problem
> No grammar constraints (DTD or XML Schema) referenced in the document. cheatsheet.xml /jboss-forge-html5 line 1 XML Problem
> No grammar constraints (DTD or XML Schema) referenced in the document. wro.xml /jboss-as-kitchensink-html5-mobile/src/main/webapp/WEB-INF line 1 XML Problem
> {code}
> For example HTML5 Project is downloading quickstart "jboss-as-kitchensink-html5-mobile", which is probably https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/33c4600/kit... and this quickstart is requiring Java 1.6. This quickstart can be replaced with newer from https://github.com/jboss-developer/jboss-eap-quickstarts/tree/4aa3caa/kit...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (JBIDE-26697) Possible memory leak during Loading projects job when using cluster with lots of projects
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26697?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26697:
-------------------------------
Summary: Possible memory leak during Loading projects job when using cluster with lots of projects (was: Possible memory leak during Loading projects job when using OS4/CRC)
> Possible memory leak during Loading projects job when using cluster with lots of projects
> -----------------------------------------------------------------------------------------
>
> 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
> Assignee: André Dietisheim
> Priority: Major
> Fix For: 4.13.0.Final
>
>
> 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.13.8#713008)
6 years, 5 months
[JBoss JIRA] (JBIDE-26906) Update jboss-stacks crc bits for dl-rt after GA
by Ondrej Dockal (Jira)
Ondrej Dockal created JBIDE-26906:
-------------------------------------
Summary: Update jboss-stacks crc bits for dl-rt after GA
Key: JBIDE-26906
URL: https://issues.jboss.org/browse/JBIDE-26906
Project: Tools (JBoss Tools)
Issue Type: Task
Components: cdk
Affects Versions: 4.13.0.Final
Reporter: Ondrej Dockal
Assignee: Ondrej Dockal
Fix For: 4.13.0.Final
We need to update jboss-stacks yaml with released CRC bits. [~jeffmaury] [~rob.stryker] CCying you in order to have someone as a backup in case I wont make it tonight. First came, first served.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months