April 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-45) Update composite*.xml files for latest SwitchYard release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-45?page=com.atlassian.jira.plugin.s... ] Nick Boldt resolved JBTIS-45. ----------------------------- Fix Version/s: 4.0.0 Resolution: Done Done. > Update composite*.xml files for latest SwitchYard release > --------------------------------------------------------- > > Key: JBTIS-45 > URL: https://issues.jboss.org/browse/JBTIS-45 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: switchyard > Reporter: Rob Cernich > Assignee: Rob Cernich > Fix For: 4.0.0 > > > Need to add SwitchYard 0.8.0.Final to the composite*.xml files for .../stable/juno/soa-tooling/switchyard. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13800) Error when installing jenkins-client cartridge just after creating the jenkins application (on LiveCD) (WATCHER ISSUE)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13800?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13800: ------------------------------------- Fix Version/s: 4.1.x > Error when installing jenkins-client cartridge just after creating the jenkins application (on LiveCD) (WATCHER ISSUE) > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13800 > URL: https://issues.jboss.org/browse/JBIDE-13800 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Fix For: 4.1.x > > > In REST API version 1.0 (running a LiveCD on VirtualBox), I got the following error message when I tried to install a jenkins-client on my application. > Could not embed cartridges for application test2 > Could not request https://192.168.56.101/broker/rest/domains/devoxx/applications/test2/cart...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "157".Reason given: "Error contacting Jenkins server. > Could not download https://jenkins-devoxx.example.com/jnlpJars/jenkins-cli.jar" > I also created the jenkins application since I did not have one in my domain before, so my guess is that the lib download occurred before the application was available, which ended up with that error message. > Trying to install the same jenkins-client embedded cartridge a few minutes later worked. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13801) Wrong Server Adapter name generated from Wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13801?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-13801. -------------------------------------- Resolution: Duplicate Issue > Wrong Server Adapter name generated from Wizard > ----------------------------------------------- > > Key: JBIDE-13801 > URL: https://issues.jboss.org/browse/JBIDE-13801 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > > When you create a server adapter for an existing application, in case it's missing, the server name is made after the first app in the domain, not the selected app in the openshift explorer view. > In my case, I had 2 applications: "html5" and "test", and I wanted to create a server adapter for the "test" one (using the "Create Server Adapter" command), but the name was "html5 on OpenShift" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13659) OpenShift Server wizard is giving different name to server adapter

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13659?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13659: ------------------------------------- Description: Trying to create server adapter for application *spring* and server wizard uses a different name for the server adapter (actually from different accout): see [^out.ogv] No entry in error log. quoted from JBIDE-13801 (duplicate issue) {quote} When you create a server adapter for an existing application, in case it's missing, the server name is made after the first app in the domain, not the selected app in the openshift explorer view. In my case, I had 2 applications: "html5" and "test", and I wanted to create a server adapter for the "test" one (using the "Create Server Adapter" command), but the name was "html5 on OpenShift" {quote} was: Trying to create server adapter for application *spring* and server wizard uses a different name for the server adapter (actually from different accout): see [^out.ogv] No entry in error log. > OpenShift Server wizard is giving different name to server adapter > ------------------------------------------------------------------ > > Key: JBIDE-13659 > URL: https://issues.jboss.org/browse/JBIDE-13659 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers, openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Assignee: Stefan Bunciak > Priority: Critical > Fix For: 4.1.0.Beta1 > > Attachments: out.ogv > > > Trying to create server adapter for application *spring* and server wizard uses a different name for the server adapter (actually from different accout): see [^out.ogv] > No entry in error log. > quoted from JBIDE-13801 (duplicate issue) > {quote} > When you create a server adapter for an existing application, in case it's missing, the server name is made after the first app in the domain, not the selected app in the openshift explorer view. > In my case, I had 2 applications: "html5" and "test", and I wanted to create a server adapter for the "test" one (using the "Create Server Adapter" command), but the name was "html5 on OpenShift" > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13800) Error when installing jenkins-client cartridge just after creating the jenkins application (on LiveCD) (WATCHER ISSUE)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13800?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13800: ------------------------------------- Summary: Error when installing jenkins-client cartridge just after creating the jenkins application (on LiveCD) (WATCHER ISSUE) (was: Error when installing jenkins-client cartridge just after creating the jenkins application (on LiveCD)) > Error when installing jenkins-client cartridge just after creating the jenkins application (on LiveCD) (WATCHER ISSUE) > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13800 > URL: https://issues.jboss.org/browse/JBIDE-13800 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > > In REST API version 1.0 (running a LiveCD on VirtualBox), I got the following error message when I tried to install a jenkins-client on my application. > Could not embed cartridges for application test2 > Could not request https://192.168.56.101/broker/rest/domains/devoxx/applications/test2/cart...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "157".Reason given: "Error contacting Jenkins server. > Could not download https://jenkins-devoxx.example.com/jnlpJars/jenkins-cli.jar" > I also created the jenkins application since I did not have one in my domain before, so my guess is that the lib download occurred before the application was available, which ended up with that error message. > Trying to install the same jenkins-client embedded cartridge a few minutes later worked. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13800) Error when installing jenkins-client cartridge just after creating the jenkins application (on LiveCD)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13800?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13800: ------------------------------------- Issue Type: Task (was: Bug) > Error when installing jenkins-client cartridge just after creating the jenkins application (on LiveCD) > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13800 > URL: https://issues.jboss.org/browse/JBIDE-13800 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > > In REST API version 1.0 (running a LiveCD on VirtualBox), I got the following error message when I tried to install a jenkins-client on my application. > Could not embed cartridges for application test2 > Could not request https://192.168.56.101/broker/rest/domains/devoxx/applications/test2/cart...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "157".Reason given: "Error contacting Jenkins server. > Could not download https://jenkins-devoxx.example.com/jnlpJars/jenkins-cli.jar" > I also created the jenkins application since I did not have one in my domain before, so my guess is that the lib download occurred before the application was available, which ended up with that error message. > Trying to install the same jenkins-client embedded cartridge a few minutes later worked. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13882) Allow users to easily "binary deploy" in the wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13882?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13882: ------------------------------------- Issue Type: Enhancement (was: Feature Request) > Allow users to easily "binary deploy" in the wizard > --------------------------------------------------- > > Key: JBIDE-13882 > URL: https://issues.jboss.org/browse/JBIDE-13882 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta1 > > > We should have an option in the wizard that allows easy "binary only" deployment > {quote} > 'binary deployment only' option which will go disable the the build marker...but what do we do about the existing project content - just leave it in place I would say.{quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13882) Allow users to easily "binary deploy" in the wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13882?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13882: ------------------------------------- Fix Version/s: 4.1.x (was: 4.1.0.Beta1) > Allow users to easily "binary deploy" in the wizard > --------------------------------------------------- > > Key: JBIDE-13882 > URL: https://issues.jboss.org/browse/JBIDE-13882 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.x > > > We should have an option in the wizard that allows easy "binary only" deployment > {quote} > 'binary deployment only' option which will go disable the the build marker...but what do we do about the existing project content - just leave it in place I would say.{quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13894) 'Tail files...' dialog ignores -n parameter value

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13894?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13894: ------------------------------------- Priority: Minor (was: Critical) > 'Tail files...' dialog ignores -n parameter value > ------------------------------------------------- > > Key: JBIDE-13894 > URL: https://issues.jboss.org/browse/JBIDE-13894 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.x > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.0.Beta1 > > Attachments: tail1.png > > > I set -n parameter to 3: > !tail1.png|thumbnail! > but the console output contains much more lines right away: > {code} > Loading.... > ==> jbosseap-6.0/logs/server.log <== > 2013/04/02 07:57:42,044 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment ROOT.war > 2013/04/02 07:57:44,331 INFO [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web context: > 2013/04/02 07:57:48,743 INFO [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /jboss-as-helloworld-errai > 2013/04/02 07:57:48,933 INFO [org.jboss.as.server] (ServerService Thread Pool -- 35) JBAS018559: Deployed "jboss-as-helloworld-errai.war" > 2013/04/02 07:57:48,934 INFO [org.jboss.as.server] (ServerService Thread Pool -- 35) JBAS018559: Deployed "ROOT.war" > 2013/04/02 07:57:49,138 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.9.25.129:9990/management > 2013/04/02 07:57:49,141 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.9.25.129:9990 > 2013/04/02 07:57:49,141 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) started in 67688ms - Started 319 of 462 services (140 services are passive or on-demand) > 2013/04/02 08:03:58,941 INFO [org.jboss.resteasy.cdi.CdiInjectorFactory] (http-127.9.25.129/127.9.25.129:8080-4) Found BeanManager at java:comp/BeanManager > 2013/04/02 08:03:59,130 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (http-127.9.25.129/127.9.25.129:8080-4) Deploying javax.ws.rs.core.Application: class org.jboss.tools.example.html5.rest.JaxRsActivator$Proxy$_$$_WeldClientProxy > ==> jbosseap-6.0/logs/boot.log <== > user.name = 515ac573e0b8cd1da6000005 > user.timezone = America/New_York > 07:56:45,930 DEBUG [org.jboss.as.config] VM Arguments: -D[Standalone] -XX:+TieredCompilation -Xmx256m -XX:MaxPermSize=102m -XX:+AggressiveOpts -Dorg.apache.tomcat.util.LOW_MEMORY=true -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dfile.encoding=UTF-8 -Djava.net.preferIPv4Stack=true -Djboss.node.name=binary-pipistiks.rhcloud.com -Djgroups.bind_addr=127.9.25.129 -Dorg.apache.coyote.http11.Http11Protocol.COMPRESSION=on -Dorg.jboss.boot.log.file=/var/lib/openshift/515ac573e0b8cd1da6000005/jbosseap-6.0/jbosseap-6.0/standalone/log/boot.log -Dlogging.configuration=file:/var/lib/openshift/515ac573e0b8cd1da6000005/jbosseap-6.0/jbosseap-6.0/standalone/configuration/logging.properties > 07:56:56,854 WARN [org.jboss.as.server] JBAS015883: No security realm defined for native management service; all access will be unrestricted. > 07:56:56,853 INFO [org.xnio] XNIO Version 3.0.7.GA-redhat-1 > 07:56:57,037 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http) > 07:56:57,038 WARN [org.jboss.as.server] JBAS015884: No security realm defined for http management service; all access will be unrestricted. > 07:56:56,959 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.7.GA-redhat-1 > 07:56:57,148 INFO [org.jboss.remoting] JBoss Remoting version 3.2.14.GA-redhat-1 > 07:56:57,938 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers > {code} > I would expect the same behaviour like on linux system - to output just the specified 3 lines... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13894) 'Tail files...' dialog ignores -n parameter value

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13894?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13894: ------------------------------------------ Setting to minor since this is just annoying but not breaking anyone > 'Tail files...' dialog ignores -n parameter value > ------------------------------------------------- > > Key: JBIDE-13894 > URL: https://issues.jboss.org/browse/JBIDE-13894 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.x > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.0.Beta1 > > Attachments: tail1.png > > > I set -n parameter to 3: > !tail1.png|thumbnail! > but the console output contains much more lines right away: > {code} > Loading.... > ==> jbosseap-6.0/logs/server.log <== > 2013/04/02 07:57:42,044 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment ROOT.war > 2013/04/02 07:57:44,331 INFO [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web context: > 2013/04/02 07:57:48,743 INFO [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /jboss-as-helloworld-errai > 2013/04/02 07:57:48,933 INFO [org.jboss.as.server] (ServerService Thread Pool -- 35) JBAS018559: Deployed "jboss-as-helloworld-errai.war" > 2013/04/02 07:57:48,934 INFO [org.jboss.as.server] (ServerService Thread Pool -- 35) JBAS018559: Deployed "ROOT.war" > 2013/04/02 07:57:49,138 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.9.25.129:9990/management > 2013/04/02 07:57:49,141 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.9.25.129:9990 > 2013/04/02 07:57:49,141 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) started in 67688ms - Started 319 of 462 services (140 services are passive or on-demand) > 2013/04/02 08:03:58,941 INFO [org.jboss.resteasy.cdi.CdiInjectorFactory] (http-127.9.25.129/127.9.25.129:8080-4) Found BeanManager at java:comp/BeanManager > 2013/04/02 08:03:59,130 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (http-127.9.25.129/127.9.25.129:8080-4) Deploying javax.ws.rs.core.Application: class org.jboss.tools.example.html5.rest.JaxRsActivator$Proxy$_$$_WeldClientProxy > ==> jbosseap-6.0/logs/boot.log <== > user.name = 515ac573e0b8cd1da6000005 > user.timezone = America/New_York > 07:56:45,930 DEBUG [org.jboss.as.config] VM Arguments: -D[Standalone] -XX:+TieredCompilation -Xmx256m -XX:MaxPermSize=102m -XX:+AggressiveOpts -Dorg.apache.tomcat.util.LOW_MEMORY=true -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dfile.encoding=UTF-8 -Djava.net.preferIPv4Stack=true -Djboss.node.name=binary-pipistiks.rhcloud.com -Djgroups.bind_addr=127.9.25.129 -Dorg.apache.coyote.http11.Http11Protocol.COMPRESSION=on -Dorg.jboss.boot.log.file=/var/lib/openshift/515ac573e0b8cd1da6000005/jbosseap-6.0/jbosseap-6.0/standalone/log/boot.log -Dlogging.configuration=file:/var/lib/openshift/515ac573e0b8cd1da6000005/jbosseap-6.0/jbosseap-6.0/standalone/configuration/logging.properties > 07:56:56,854 WARN [org.jboss.as.server] JBAS015883: No security realm defined for native management service; all access will be unrestricted. > 07:56:56,853 INFO [org.xnio] XNIO Version 3.0.7.GA-redhat-1 > 07:56:57,037 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http) > 07:56:57,038 WARN [org.jboss.as.server] JBAS015884: No security realm defined for http management service; all access will be unrestricted. > 07:56:56,959 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.7.GA-redhat-1 > 07:56:57,148 INFO [org.jboss.remoting] JBoss Remoting version 3.2.14.GA-redhat-1 > 07:56:57,938 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers > {code} > I would expect the same behaviour like on linux system - to output just the specified 3 lines... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

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 April 2013