[JBoss JIRA] (JBIDE-21877) Make error message shown in OpenShift Explorer for outdated token more user friendly
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-21877:
--------------------------------------
Assignee: Viacheslav Kabanovich
[~scabanovich] can you please take care of it? Or assign to Fred otherwise.
> Make error message shown in OpenShift Explorer for outdated token more user friendly
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-21877
> URL: https://issues.jboss.org/browse/JBIDE-21877
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: connection, openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> When I am trying to connect to OpenShift connection with outdated token stored in secure storage, an error tree item is shown in OpenShift Explorer under the connection. Erro tree item is "java.lang.NullPointerException", but it could be something more user friendly such as "Expired credentials" or the one we are already using in other scenarious - You must obtain an API token by .... Following stack trace is in error log
> {code}
> There was an error retrieving children in the OpenShift explorer
> java.lang.NullPointerException
> at org.eclipse.epp.internal.mpc.core.util.ProxyHelper$ProxyAuthenticator.getPasswordAuthentication(ProxyHelper.java:124)
> at java.net.Authenticator.requestPasswordAuthentication(Authenticator.java:317)
> at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getSystemCreds(SystemDefaultCredentialsProvider.java:92)
> at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getCredentials(SystemDefaultCredentialsProvider.java:113)
> at com.openshift.internal.restclient.authorization.OpenShiftCredentialsProvider.getCredentials(OpenShiftCredentialsProvider.java:69)
> at org.apache.http.impl.client.AuthenticationStrategyImpl.select(AuthenticationStrategyImpl.java:184)
> at org.apache.http.impl.client.TargetAuthenticationStrategy.select(TargetAuthenticationStrategy.java:43)
> at org.apache.http.impl.auth.HttpAuthenticator.handleAuthChallenge(HttpAuthenticator.java:154)
> at org.apache.http.impl.execchain.MainClientExec.needAuthentication(MainClientExec.java:557)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:275)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:99)
> at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:504)
> at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:236)
> at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226)
> at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:445)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:389)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:376)
> at org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectCache.getProjectsFor(OpenShiftProjectCache.java:59)
> at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:93)
> at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:167)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21877) Make error message shown in OpenShift Explorer for outdated token more user friendly
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21877:
----------------------------------------
cc: [~jcantrill]
> Make error message shown in OpenShift Explorer for outdated token more user friendly
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-21877
> URL: https://issues.jboss.org/browse/JBIDE-21877
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: connection, openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> When I am trying to connect to OpenShift connection with outdated token stored in secure storage, an error tree item is shown in OpenShift Explorer under the connection. Erro tree item is "java.lang.NullPointerException", but it could be something more user friendly such as "Expired credentials" or the one we are already using in other scenarious - You must obtain an API token by .... Following stack trace is in error log
> {code}
> There was an error retrieving children in the OpenShift explorer
> java.lang.NullPointerException
> at org.eclipse.epp.internal.mpc.core.util.ProxyHelper$ProxyAuthenticator.getPasswordAuthentication(ProxyHelper.java:124)
> at java.net.Authenticator.requestPasswordAuthentication(Authenticator.java:317)
> at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getSystemCreds(SystemDefaultCredentialsProvider.java:92)
> at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getCredentials(SystemDefaultCredentialsProvider.java:113)
> at com.openshift.internal.restclient.authorization.OpenShiftCredentialsProvider.getCredentials(OpenShiftCredentialsProvider.java:69)
> at org.apache.http.impl.client.AuthenticationStrategyImpl.select(AuthenticationStrategyImpl.java:184)
> at org.apache.http.impl.client.TargetAuthenticationStrategy.select(TargetAuthenticationStrategy.java:43)
> at org.apache.http.impl.auth.HttpAuthenticator.handleAuthChallenge(HttpAuthenticator.java:154)
> at org.apache.http.impl.execchain.MainClientExec.needAuthentication(MainClientExec.java:557)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:275)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:99)
> at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:504)
> at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:236)
> at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226)
> at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:445)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:389)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:376)
> at org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectCache.getProjectsFor(OpenShiftProjectCache.java:59)
> at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:93)
> at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:167)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21877) Make error message shown in OpenShift Explorer for outdated token more user friendly
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21877:
-----------------------------------
Fix Version/s: 4.4.x
> Make error message shown in OpenShift Explorer for outdated token more user friendly
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-21877
> URL: https://issues.jboss.org/browse/JBIDE-21877
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: connection, openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> When I am trying to connect to OpenShift connection with outdated token stored in secure storage, an error tree item is shown in OpenShift Explorer under the connection. Erro tree item is "java.lang.NullPointerException", but it could be something more user friendly such as "Expired credentials" or the one we are already using in other scenarious - You must obtain an API token by .... Following stack trace is in error log
> {code}
> There was an error retrieving children in the OpenShift explorer
> java.lang.NullPointerException
> at org.eclipse.epp.internal.mpc.core.util.ProxyHelper$ProxyAuthenticator.getPasswordAuthentication(ProxyHelper.java:124)
> at java.net.Authenticator.requestPasswordAuthentication(Authenticator.java:317)
> at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getSystemCreds(SystemDefaultCredentialsProvider.java:92)
> at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getCredentials(SystemDefaultCredentialsProvider.java:113)
> at com.openshift.internal.restclient.authorization.OpenShiftCredentialsProvider.getCredentials(OpenShiftCredentialsProvider.java:69)
> at org.apache.http.impl.client.AuthenticationStrategyImpl.select(AuthenticationStrategyImpl.java:184)
> at org.apache.http.impl.client.TargetAuthenticationStrategy.select(TargetAuthenticationStrategy.java:43)
> at org.apache.http.impl.auth.HttpAuthenticator.handleAuthChallenge(HttpAuthenticator.java:154)
> at org.apache.http.impl.execchain.MainClientExec.needAuthentication(MainClientExec.java:557)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:275)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:99)
> at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:504)
> at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:236)
> at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226)
> at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:445)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:389)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:376)
> at org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectCache.getProjectsFor(OpenShiftProjectCache.java:59)
> at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:93)
> at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:167)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21877) Make error message shown in OpenShift Explorer for outdated token more user friendly
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21877:
-----------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.4.x)
> Make error message shown in OpenShift Explorer for outdated token more user friendly
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-21877
> URL: https://issues.jboss.org/browse/JBIDE-21877
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: connection, openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> When I am trying to connect to OpenShift connection with outdated token stored in secure storage, an error tree item is shown in OpenShift Explorer under the connection. Erro tree item is "java.lang.NullPointerException", but it could be something more user friendly such as "Expired credentials" or the one we are already using in other scenarious - You must obtain an API token by .... Following stack trace is in error log
> {code}
> There was an error retrieving children in the OpenShift explorer
> java.lang.NullPointerException
> at org.eclipse.epp.internal.mpc.core.util.ProxyHelper$ProxyAuthenticator.getPasswordAuthentication(ProxyHelper.java:124)
> at java.net.Authenticator.requestPasswordAuthentication(Authenticator.java:317)
> at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getSystemCreds(SystemDefaultCredentialsProvider.java:92)
> at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getCredentials(SystemDefaultCredentialsProvider.java:113)
> at com.openshift.internal.restclient.authorization.OpenShiftCredentialsProvider.getCredentials(OpenShiftCredentialsProvider.java:69)
> at org.apache.http.impl.client.AuthenticationStrategyImpl.select(AuthenticationStrategyImpl.java:184)
> at org.apache.http.impl.client.TargetAuthenticationStrategy.select(TargetAuthenticationStrategy.java:43)
> at org.apache.http.impl.auth.HttpAuthenticator.handleAuthChallenge(HttpAuthenticator.java:154)
> at org.apache.http.impl.execchain.MainClientExec.needAuthentication(MainClientExec.java:557)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:275)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:99)
> at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:504)
> at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:236)
> at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226)
> at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:445)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:389)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:376)
> at org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectCache.getProjectsFor(OpenShiftProjectCache.java:59)
> at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:93)
> at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:167)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21822) Remote invocation problem when deploying and running EAP apps from JBDS
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21822?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-21822:
--------------------------------------
Assignee: Mickael Istria (was: Rob Stryker)
[~mickael_istria] can you please take a look?
> Remote invocation problem when deploying and running EAP apps from JBDS
> -----------------------------------------------------------------------
>
> Key: JBIDE-21822
> URL: https://issues.jboss.org/browse/JBIDE-21822
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport, server
> Affects Versions: 4.3.0.Final
> Environment: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: /opt/apache-maven-3.3.9
> Java version: 1.8.0_74, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_74/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.3-300.fc23.x86_64+debug", arch: "amd64", family: "unix"
> Fedora 23
> Reporter: Michal Jurc
> Assignee: Mickael Istria
> Fix For: 4.4.0.Alpha1
>
>
> When attempting to follow the steps in ejb-remote quickstart for EAP 6.4.6.GA and 7.0.0.ER6, after deploying the server-side application, the client application has problem with remote invocation of the application deployed:
> {code}
> Exception in thread "main" java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:jboss-ejb-remote-server-side, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@731a74c
> at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:798)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:128)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
> at com.sun.proxy.$Proxy0.add(Unknown Source)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.invokeStatelessBean(RemoteEJBClient.java:57)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.main(RemoteEJBClient.java:38)
> {code}
> The same quickstart can be completed when ran from terminal on standalone EAP (EAP not launched and managed by JBDS).
> I was so far unable to reproduce the issue on other machines.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21822) Remote invocation problem when deploying and running EAP apps from JBDS
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21822?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21822:
-----------------------------------
Fix Version/s: 4.4.0.Alpha1
> Remote invocation problem when deploying and running EAP apps from JBDS
> -----------------------------------------------------------------------
>
> Key: JBIDE-21822
> URL: https://issues.jboss.org/browse/JBIDE-21822
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport, server
> Affects Versions: 4.3.0.Final
> Environment: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: /opt/apache-maven-3.3.9
> Java version: 1.8.0_74, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_74/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.3-300.fc23.x86_64+debug", arch: "amd64", family: "unix"
> Fedora 23
> Reporter: Michal Jurc
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha1
>
>
> When attempting to follow the steps in ejb-remote quickstart for EAP 6.4.6.GA and 7.0.0.ER6, after deploying the server-side application, the client application has problem with remote invocation of the application deployed:
> {code}
> Exception in thread "main" java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:jboss-ejb-remote-server-side, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@731a74c
> at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:798)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:128)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
> at com.sun.proxy.$Proxy0.add(Unknown Source)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.invokeStatelessBean(RemoteEJBClient.java:57)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.main(RemoteEJBClient.java:38)
> {code}
> The same quickstart can be completed when ran from terminal on standalone EAP (EAP not launched and managed by JBDS).
> I was so far unable to reproduce the issue on other machines.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22008) JBoss EAP 6.x server fails to stop in JBDS 9 , if a port-offset is used.
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22008?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22008:
-----------------------------------
Fix Version/s: 4.4.x
> JBoss EAP 6.x server fails to stop in JBDS 9 , if a port-offset is used.
> ------------------------------------------------------------------------
>
> Key: JBIDE-22008
> URL: https://issues.jboss.org/browse/JBIDE-22008
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Reporter: Harshada Boob
> Assignee: Rob Stryker
> Fix For: 4.4.x
>
> Attachments: .log, Screenshot-JBoss - JBoss EAP 6.4 - JBoss Developer Studio .png
>
>
> 1. When EAP 6.4.x is started with a port-offset, the EAP server starts succesfully and works all good, but there is an issue while stopping the server from JBDS.
> 2. It fails to stop when clicking for the first time on the 'stop' button in the 'server' tab/window and then the server process is terminated/killed if you again try to stop the server by second time clicking on the 'stop' button in the server tab.
> 3. Attached is the screenshot - which is seen when you try to stop the server for the first time and following exception is seen in the workspace/.metadat/.log file (File attached):
> -------------------------------------------------------------------------------------------------------------------
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://localhost:10000. The connection failed
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:361)
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9ManagerService.execute(Wildfly9ManagerService.java:171)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.jboss.ide.eclipse.as.management.core.service.DelegatingManagerService.execute(DelegatingManagerService.java:132)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:291)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:1)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerUtil.executeWithService(JBoss7ManagerUtil.java:136)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.executeWithResult(AS7DeploymentScannerUtility.java:289)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScanners(AS7DeploymentScannerUtility.java:161)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScannersFromServer(AS7DeploymentScannerUtility.java:249)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.loadScannersFromServer(LocalJBoss7DeploymentScannerAdditions.java:173)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.loadScannersFromServerSafely(LocalJBoss7DeploymentScannerAdditions.java:135)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.ensureScannersRemoved(LocalJBoss7DeploymentScannerAdditions.java:150)
> at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions.removeAddedDeploymentScanners(AbstractDeploymentScannerAdditions.java:83)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.removeScanners(LocalLegacyShutdownController.java:75)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:58)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:53)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.stop(ControllableServerBehavior.java:252)
> at org.eclipse.wst.server.core.internal.Server.stopImpl2(Server.java:3688)
> at org.eclipse.wst.server.core.internal.Server.stopImpl(Server.java:3645)
> at org.eclipse.wst.server.core.internal.Server$StopJob.run(Server.java:403)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://localhost:10000. The connection failed
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:350)
> ... 22 more
> Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://localhost:10000. The connection failed
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:122)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:257)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:71)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:212)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:146)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:147)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:122)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> ... 24 more
> Caused by: java.io.EOFException: XNIO000812: Connection closed unexpectedly
> at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:416)
> at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:400)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:88)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:539)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:272)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:253)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:351)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:339)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:83)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:114)
> ... 34 more
> ------------------------------------------------------------------------------------------------------------------
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22008) JBoss EAP 6.x server fails to stop in JBDS 9 , if a port-offset is used.
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22008?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22008:
-----------------------------------
Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio))
Key: JBIDE-22008 (was: JBDS-3673)
Workflow: GIT Pull Request workflow (was: CDW v1)
Status: Open (was: New)
Docs QE Status: (was: NEW)
Component/s: server
(was: server)
Affects Version/s: 4.3.0.Final
(was: 9.0.0.GA)
> JBoss EAP 6.x server fails to stop in JBDS 9 , if a port-offset is used.
> ------------------------------------------------------------------------
>
> Key: JBIDE-22008
> URL: https://issues.jboss.org/browse/JBIDE-22008
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Reporter: Harshada Boob
> Assignee: Rob Stryker
> Attachments: .log, Screenshot-JBoss - JBoss EAP 6.4 - JBoss Developer Studio .png
>
>
> 1. When EAP 6.4.x is started with a port-offset, the EAP server starts succesfully and works all good, but there is an issue while stopping the server from JBDS.
> 2. It fails to stop when clicking for the first time on the 'stop' button in the 'server' tab/window and then the server process is terminated/killed if you again try to stop the server by second time clicking on the 'stop' button in the server tab.
> 3. Attached is the screenshot - which is seen when you try to stop the server for the first time and following exception is seen in the workspace/.metadat/.log file (File attached):
> -------------------------------------------------------------------------------------------------------------------
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://localhost:10000. The connection failed
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:361)
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9ManagerService.execute(Wildfly9ManagerService.java:171)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.jboss.ide.eclipse.as.management.core.service.DelegatingManagerService.execute(DelegatingManagerService.java:132)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:291)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:1)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerUtil.executeWithService(JBoss7ManagerUtil.java:136)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.executeWithResult(AS7DeploymentScannerUtility.java:289)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScanners(AS7DeploymentScannerUtility.java:161)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScannersFromServer(AS7DeploymentScannerUtility.java:249)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.loadScannersFromServer(LocalJBoss7DeploymentScannerAdditions.java:173)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.loadScannersFromServerSafely(LocalJBoss7DeploymentScannerAdditions.java:135)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.ensureScannersRemoved(LocalJBoss7DeploymentScannerAdditions.java:150)
> at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions.removeAddedDeploymentScanners(AbstractDeploymentScannerAdditions.java:83)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.removeScanners(LocalLegacyShutdownController.java:75)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:58)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:53)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.stop(ControllableServerBehavior.java:252)
> at org.eclipse.wst.server.core.internal.Server.stopImpl2(Server.java:3688)
> at org.eclipse.wst.server.core.internal.Server.stopImpl(Server.java:3645)
> at org.eclipse.wst.server.core.internal.Server$StopJob.run(Server.java:403)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://localhost:10000. The connection failed
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:350)
> ... 22 more
> Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://localhost:10000. The connection failed
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:122)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:257)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:71)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:212)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:146)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:147)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:122)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> ... 24 more
> Caused by: java.io.EOFException: XNIO000812: Connection closed unexpectedly
> at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:416)
> at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:400)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:88)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:539)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:272)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:253)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:351)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:339)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:83)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:114)
> ... 34 more
> ------------------------------------------------------------------------------------------------------------------
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21939) datatypes.dtd and properties.dtd not present in xml catalog
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21939?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21939:
-----------------------------------
Fix Version/s: 4.4.x
> datatypes.dtd and properties.dtd not present in xml catalog
> -----------------------------------------------------------
>
> Key: JBIDE-21939
> URL: https://issues.jboss.org/browse/JBIDE-21939
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.x
>
>
> Maybe this is not an issue at all but need to check.
> While verifying JBIDE-21690, I noticed that there are two dtd files that are not referenced in plugin.xml of org.jboss.tools.as.catalog_3.1.1.CR1-v20160316-0026-B106.jar .
> {code}
> $ for i in `find schema -name '*.dtd'`; do grep $i plugin.xml >/dev/null || echo $i not found; done
> schema/dtd/datatypes.dtd not found
> schema/dtd/properties.dtd not found
> {code}
> Is this ok or not?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21935) "Reuse" flow in clone wizard is ambiguous
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21935?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21935:
-----------------------------------
Fix Version/s: 4.4.x
> "Reuse" flow in clone wizard is ambiguous
> -----------------------------------------
>
> Key: JBIDE-21935
> URL: https://issues.jboss.org/browse/JBIDE-21935
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.x
>
>
> continuation of JBIDE-14828:
> with the intended behavior explained then lets make that visible to the user:
> a) don't hide/show controls in a wizard, enable/disable them.
> b) The "Reuse" is ambiguous, i.e. I read it as the clone will happen into this folder, not that it will do exactly the opposite of what the wizard says (not clone). I suggest something like "Do not clone - reuse existing folder".
> c) if not already there, add a check that what is inside the folder is actually a clone of what we are trying to clone.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years