March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22034) Replace Pin Console toggle tool item by Show Console Output When Standard Out Changes toggle item

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22034: ------------------------------------- Summary: Replace Pin Console toggle tool item by Show Console Output When Standard Out Changes toggle item Key: JBIDE-22034 URL: https://issues.jboss.org/browse/JBIDE-22034 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda Currently console containing output of rsync contains Pin Console toggle item which is useless there. Item should be changed to Show Console Output When Standard Out Changes which, when is enabled, show console view when output in it changes - this makes sense because if user want to track what have been rsynced, this is nice way to do it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22034) Replace Pin Console toggle tool item by Show Console Output When Standard Out Changes toggle item

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22034?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22034: ---------------------------------- Labels: openshift_v3 (was: ) > Replace Pin Console toggle tool item by Show Console Output When Standard Out Changes toggle item > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-22034 > URL: https://issues.jboss.org/browse/JBIDE-22034 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > > Currently console containing output of rsync contains Pin Console toggle item which is useless there. Item should be changed to Show Console Output When Standard Out Changes which, when is enabled, show console view when output in it changes - this makes sense because if user want to track what have been rsynced, this is nice way to do it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21981) Error during rsync

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21981?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21981: ------------------------------------- I know everyone's been able to replicate this but so far I haven't. I'll keep trying. > Error during rsync > ------------------ > > Key: JBIDE-21981 > URL: https://issues.jboss.org/browse/JBIDE-21981 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Xavier Coulon > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.3.1.CR1 > > > While testing the debugging support on the server adapter, I got the following error: > {code} > Could not sync all pods to folder /Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample@eap-app/deploy > OpenShiftBinaryCapability process exited: rsync: delete_file: rmdir "/Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample(a)eap-app/deploy/ROOT.war" failed: Directory not empty (66) > rsync error: some files could not be transferred (code 23) at /SourceCache/rsync/rsync-45/rsync/main.c(1400) [generator=2.6.9] > error: exit status 23 > {code} > The content of the {{.../deploy}} directory was: > {code} > drwxr-xr-x 9 xcoulon staff 306 Mar 25 12:19 ./ > drwxr-xr-x 4 xcoulon staff 136 Mar 25 11:55 ../ > -rw-r--r-- 1 xcoulon staff 9041 Mar 27 2015 README.txt > drwxr-xr-x 7 xcoulon staff 238 Mar 25 11:59 ROOT.war/ > -rw-r--r-- 1 xcoulon staff 8 Mar 23 17:59 ROOT.war.deployed > -rw-r--r-- 1 xcoulon staff 8 Mar 25 12:18 ROOT.war.isdeploying > -rw-r--r-- 1 xcoulon staff 8415373 Aug 11 2015 activemq-rar.rar > -rw-r--r-- 1 xcoulon staff 16 Aug 11 2015 activemq-rar.rar.deployed > -rw-r--r-- 1 xcoulon staff 16 Mar 25 12:18 activemq-rar.rar.isdeploying > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21989) Show In - Web Browser from context menu of J2EE module on OS3 Server Adapter opens localhost

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21989?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21989: ------------------------------------- [~mlabuda] Are you sure this is the right issue for that? I think that requires a new issue. > Show In - Web Browser from context menu of J2EE module on OS3 Server Adapter opens localhost > -------------------------------------------------------------------------------------------- > > Key: JBIDE-21989 > URL: https://issues.jboss.org/browse/JBIDE-21989 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > When selecting Show In - Web Browser from context menu of Java EE module under an OpenShift 3 connection, it opens a localhost, what is wrong (it does not use root). Such module can be e.g. jboss-kitchensink when using application based on eap s2i template with param CONTEXT_DIR kitchensink. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21989) Show In - Web Browser from context menu of J2EE module on OS3 Server Adapter opens localhost

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21989?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21989: ------------------------------------- By my tests, once a server has a proper host, showin -> web browser functions properly. I think the linked issues should solve this directly. > Show In - Web Browser from context menu of J2EE module on OS3 Server Adapter opens localhost > -------------------------------------------------------------------------------------------- > > Key: JBIDE-21989 > URL: https://issues.jboss.org/browse/JBIDE-21989 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > When selecting Show In - Web Browser from context menu of Java EE module under an OpenShift 3 connection, it opens a localhost, what is wrong (it does not use root). Such module can be e.g. jboss-kitchensink when using application based on eap s2i template with param CONTEXT_DIR kitchensink. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22020) For JBIDE 4.3.1.CR1: Prepare for Final/GA [Playground]

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22020?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-22020. ---------------------------------- Assignee: Mickael Istria Resolution: Done Done. Thanks for the instructions. > For JBIDE 4.3.1.CR1: Prepare for Final/GA [Playground] > ------------------------------------------------------ > > Key: JBIDE-22020 > URL: https://issues.jboss.org/browse/JBIDE-22020 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.3.1.CR1 > > > For JBIDE 4.3.1.CR1 [Playground]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final > [Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch: > {code} > git checkout jbosstools-4.3.x > {code} > 2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch > 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0) > {code} > mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT > {code} > 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2) > {code} > mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22005) Unexpected EOF in pod log

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22005?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22005: --------------------------------------- It is also an option. I had IDE running for a long time (several hours) and then this happened. Although I was able to work with connection (I was not prompted to reenter password). Unfortunately I don't have eclipse log (while I was testing I cleared it) but as far as I remember I have not spotted error in log. I am going to update this JIRA as soon as I am able to reproduce it. > Unexpected EOF in pod log > ------------------------- > > Key: JBIDE-22005 > URL: https://issues.jboss.org/browse/JBIDE-22005 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Critical > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > I had an eap application running on OpenShift. I was watching pod log of the application (stdout from EAP server). Unfortunately in some point console was not enough for displaying pod log and it stopped streaming pod log. > Last lines from console (output of application pod log) > {code} > ... > [0m[33m09:27:29,845 WARN [org.jgroups.protocols.openshift.KUBE_PING] (Timer-4,shared=tcp) Problem getting Pod json from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={Authorization=#MASKED:885#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.openshift.ping.common.stream.InsecureStreamProvider@4fb96d85] for cluster [hornetq-channel], namespace [serveradaptertrests], labels [application=eap-app]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/serveradaptertrests/pods?labelSe... > error: unexpected EOF > {code} > I also checked pod log via Web UI, whether there is something wrong on OpenShift side, but it is tooling related - memory/space for pod log output in console is limited and it went "out of memory". Pod log in Web UI was streaming all the time. This block user from checking pod log once it reach a specific length. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-716) JBDSIS 8.0.6: Release Notes + Support Page

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-716?page=com.atlassian.jira.plug... ] Andrej Podhradsky closed TOOLSDOC-716. -------------------------------------- Resolution: Done Verified both docs. I'm closing this issue since now the docs are ok. > JBDSIS 8.0.6: Release Notes + Support Page > ------------------------------------------ > > Key: TOOLSDOC-716 > URL: https://issues.jboss.org/browse/TOOLSDOC-716 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Release Notes > Affects Versions: 8.0.6 > Reporter: Misha Ali > Assignee: Misha Ali > Fix For: 8.0.6 > > Attachments: support.png, support_correction.png > > > Create and publish release notes for 8.0.6 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21995) Hostname is set to localhost when prompt for route is checked

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21995?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21995: ------------------------------------- This bug is actually a regression from using the default route. If you expand 'advanced' while creating the server adapter, and select the route manually, the server adapter gets a proper host. I'm trying to discover how to fix it best, but I can't seem find a clean solution at the moment. > Hostname is set to localhost when prompt for route is checked > ------------------------------------------------------------- > > Key: JBIDE-21995 > URL: https://issues.jboss.org/browse/JBIDE-21995 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > Hostname in Server Editor for an OpenShift 3 application is set to localhost if checkbox "Prompt for route when multiple routes available to show in browser" is checked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21822) Remote invocation problem when deploying and running EAP apps from JBDS

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21822?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21822: ---------------------------------------- [~fbricon] IIRC I've already seen some projects in the workspace which have project name != folder name. If so, it's not a platform restriction. Are you aware of any bugzilla open with similar issue at Eclipse.org? > 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)

9 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2016