April 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12352) Remote management connection to servers cannot be established with IPv6

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12352?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-12352: -------------------------------- Assignee: (was: Rob Stryker) Fix Version/s: (was: 4.1.x) These issues are now available for interested parties to investigate a fix for. > Remote management connection to servers cannot be established with IPv6 > ----------------------------------------------------------------------- > > Key: JBIDE-12352 > URL: https://issues.jboss.org/browse/JBIDE-12352 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.1.Final > Environment: JBDS 5.0.1 > Fedora 17 32bit > OpenJDK 1.6 > Reporter: Martin Malina > > After creating JBIDE-12351 for JMX connection, I found out that the connection cannot be established at all - even when you don't try to connect via JMX. > When you set up a remote as7/eap6 server accessible over IPv6 and start the server, the remote connection will fail with this error: > {code} > Jul 20, 2012 3:14:57 PM org.xnio.Xnio <clinit> > INFO: XNIO Version 3.0.3.GA > Jul 20, 2012 3:14:57 PM org.xnio.nio.NioXnio <clinit> > INFO: XNIO NIO Implementation Version 3.0.3.GA > Jul 20, 2012 3:14:57 PM org.jboss.remoting3.EndpointImpl <clinit> > INFO: JBoss Remoting version 3.2.7.GA > Jul 20, 2012 3:15:46 PM org.jboss.remoting3.remote.RemoteConnection handleException > ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > Jul 20, 2012 3:15:46 PM org.jboss.remoting3.remote.RemoteConnection handleException > ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > Jul 20, 2012 3:15:51 PM org.xnio.Xnio <clinit> > INFO: XNIO Version 3.0.4.GA-redhat-1 > Jul 20, 2012 3:15:51 PM org.xnio.nio.NioXnio <clinit> > INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1 > Jul 20, 2012 3:15:51 PM org.jboss.remoting3.EndpointImpl <clinit> > INFO: JBoss Remoting version 3.2.8.GA-redhat-1 > Jul 20, 2012 3:15:52 PM org.jboss.remoting3.remote.RemoteConnection handleException > ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > {code} -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9794) Add a CLI batch file feature

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9794?page=com.atlassian.jira.plugin... ] Rob Stryker updated JBIDE-9794: ------------------------------- Assignee: (was: Rob Stryker) Fix Version/s: (was: 4.1.x) These issues are now available for interested parties to investigate a fix for. > Add a CLI batch file feature > ---------------------------- > > Key: JBIDE-9794 > URL: https://issues.jboss.org/browse/JBIDE-9794 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 3.3.0.M3 > Environment: AS7 > Reporter: Scott Stark > > This is a feature request to support a "CLI Batch" file that contains a collection of admin commands that will be run through the cli interface. There will need to be a remote/local notion to support the openshift case of having this file be in the application git repo and applied when pushed vs applied to a local server by invoking the cli tool. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12282) Local AS7/EAP6 fails to stop when bound to IPv6 address or anything but localhost really

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12282?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-12282: -------------------------------- Assignee: (was: Rob Stryker) Fix Version/s: (was: 4.1.x) These issues are now available for interested parties to investigate a fix for. > Local AS7/EAP6 fails to stop when bound to IPv6 address or anything but localhost really > ---------------------------------------------------------------------------------------- > > Key: JBIDE-12282 > URL: https://issues.jboss.org/browse/JBIDE-12282 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.Final > Environment: JBDS 5.0.0.GA > Fedora 17 / OS X 10.7 Lion > JBoss EAP 6.0.0.GA > Reporter: Martin Malina > > When you set up your server to be bound to IPv6 (but you don't bind the management port to anything), the server fails to stop. Second attempt will force the server to stop. > This is the error in the log: > {code} > !ENTRY org.eclipse.wst.server.core 4 0 2012-07-02 16:49:05.284 > !MESSAGE Server jboss-eap-6.0.0.GA failed to stop. > {code} > This happens most probably because in such scenario, the management port is bound to IPv4 localhost (127.0.0.1). > Indeed I just verified that this is not related to IPv6 specifically but any host name other than localhost - if you don't check "Expose your management port" (and don't set -Dmanagement manually) and the hostname is something else than localhost, then this issue will arise. Note that with remote servers you don't need to bind the management port to anything for server stop to work. So we either need to set -Dmanagement always or make sure it is not needed. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-7379) Importing / Exporting of AS servers ignore command line args, filesets, xpaths, and even runtimes

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7379?page=com.atlassian.jira.plugin... ] Rob Stryker updated JBIDE-7379: ------------------------------- Assignee: (was: Rob Stryker) Fix Version/s: (was: 4.1.x) These issues are now available for interested parties to investigate a fix for. > Importing / Exporting of AS servers ignore command line args, filesets, xpaths, and even runtimes > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-7379 > URL: https://issues.jboss.org/browse/JBIDE-7379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.2.0.Beta1 > Reporter: Rob Stryker > > Exporting of servers is incomplete. It does not export any saved filesets, xpaths, or custom launch configuration args. > Importing of servers is also incomplete, not importing any of these elements. Also, while the servers themselves are imported, sometimes their runtimes are not created at all, and you get a server with no runtime. This has been very hard to track down, but no runtimeAdded event is ever fired, and in our code it looks as if they're not even created or looked for. > This needs to be re-visited and tested extensively. I expect I will move import / export functionality into the AS plugin for now since hte o.j.t.runtime plugin already depends on AS. This will allow me to use classes already in the AS test suite for filesets and xpaths properly. I will keep the handler in the runtimes plugin but merely have it delegate to the functionality stored in the as plugin. > It currently seems to be saving only servers and not the runtimes. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14099) CLONE - Project Archives incorrectly loading saved .packages

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14099?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-14099. --------------------------------- Resolution: Won't Fix This was fixed in master. There are no more 4.0.x versions planned. > CLONE - Project Archives incorrectly loading saved .packages > ------------------------------------------------------------ > > Key: JBIDE-14099 > URL: https://issues.jboss.org/browse/JBIDE-14099 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.0.0.Final > Environment: Eclipse juno 32 bit > Reporter: Rafael Sisto > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.0.2.Final > > > After creating a project archive from the Project Archives window, consisting of a war file, a jar file and EarContent folder it creates the ear successfully. > After restarting eclipse (or closing and opening the project) the Project Archive does not load the jar and war archives, only the EarContent fileset. > Testing a little further, adding only a jar archive and a fileset works, but when adding the second jar (war in this case), the project archives loads only the fileset, discarding both jars. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16638) Improve UI of Deployment Scanner settings

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16638?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-16638: -------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.CR1) > Improve UI of Deployment Scanner settings > ----------------------------------------- > > Key: JBIDE-16638 > URL: https://issues.jboss.org/browse/JBIDE-16638 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Alpha2 > Environment: JBDS 8.0.0.Alpha2b B71 > Reporter: Martin Malina > Fix For: 4.2.x > > Attachments: scanner-options-mockup.png, scanner-options.png > > > Looking at the new options introduced in JBIDE-15287, I don't quite like to look of it. > Let me know if you disagree, but using "(default)" in a field that's supposed to take numbers is not very nice. > !scanner-options.png! > Instead, I propose adding a checkbox in front of the options: > !scanner-options-mockup.png! > Excuse the ugly picture, but the idea is that if the checkbox is not checked, the field is greyed out (and empty). If it is checked, a value is expected. WDYT? -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-492) Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-492?page=com.atlassian.jira.plug... ] Mustafa Musaji commented on TOOLSDOC-492: ----------------------------------------- For the CSP, the docs have to be in the same format their available in now (html-single, html and pdf). I'm not sure if this change will impact the CSP or just community pages. Are you wanting to link the proposed landing page to docs on jboss.org or to access.redhat.com? > Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process) > ------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-492 > URL: https://issues.jboss.org/browse/TOOLSDOC-492 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: User Guide > Affects Versions: 4.2.0.Beta1 > Reporter: Nick Boldt > Assignee: Michelle Murray > Fix For: 4.2.0.Beta2 > > > With the release of the new tools.jboss.org site, it's time to migrate the docs to the same skin / format / markup. Docbook is dead, long live Asciidoc! > What [~mmurray] and I are thinking is that we would have a new landing page similar to one of these: > http://tools.jboss.org/features/ (with icons that link to projects' latest doc) > or > http://tools.jboss.org/documentation/whatsnew/ (with the latest doc linked) > And then under that landing page we'd have doc for each of projects' contributions to the User Guide, by milestone or Final release. > Questions: > a. [~maxandersen] [~burrsutter] [~mmusaji] Do we still need to provide 3 formats of doc - HTML, HTML-single, and PDF? Or can we replace that with this new content, PLUS include inline help doc within Eclipse? (That's another issue - see [~dgolovin] 's https://github.com/dgolovin/jbosstools-eclipse-docs/blob/master/docs/scen... for prototype) > b. [~maxandersen] Should we include docs for "dead" projects like Freemarker, Portal, etc.? I'm guessing YES, even if the doc becomes out of date (ie., the doc for JBT 4.2 for Freemarker won't have changed much (or at all) since JBT 4.0/4.1). > c. [~maxandersen] Should we convert old JBT 4.1.x (and/or 4.0.x, 3.3.x) doc to the new adoc format, or just start w/ the JBT 4.2.0.Beta1/2 doc? I'd be OK with 4.1 and maybe 4.0, but can we skip 3.3 since JBDS 5 is no longer fully supported? > d. Will docbook2asciidoc [0] work for batch-converting docbook docs to adoc? @nick will try. If conversion works easily, then converting older User Guides is definitely more doable / less time consuming. > [0] https://github.com/oreillymedia/docbook2asciidoc > e. [~xcoulon] Is :page-component_version: still used, eg., in [1], or is the filename version itself used to categorize the content by milestone? > [1] https://github.com/jbosstools/jbosstools-website/blob/master/documentatio... > f. If we decide to continue to include other formats (eg., html-single, pdf) should we link to those from these places [2], [3]? > [2] http://tools.jboss.org/downloads/overview.html > [3] http://tools.jboss.org/downloads/jbosstools/luna/4.2.0.Beta1.html -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17208) cannot create python app w/jenkins

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17208?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-17208: ------------------------------------------ With the fix in JBIDE-17205 the error is slightly different: No error happens when creating the application, everything works smoothly. But jenkins-client wont get embedded :( > cannot create python app w/jenkins > ---------------------------------- > > Key: JBIDE-17208 > URL: https://issues.jboss.org/browse/JBIDE-17208 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > > When trying to create a pyton 2.7 w/jenkins client I get this error: > Could not create application "jira" > Could not request https://openshift.redhat.com/broker/rest/domain/man/applications?include=...: An application must contain one web cartridge. None of the specified cartridges is a web cartridge. Please include one of the following cartridges: diy-0.1, jboss-dv-6.0.0, jboss-vertx-2.1, jbossas-7, jbosseap-6, jbossews-1.0, jbossews-2.0, jenkins-1, nodejs-0.10, nodejs-0.6, perl-5.10, php-5.3, php-5.4, python-2.6, python-2.7, python-3.3, ruby-1.8, ruby-1.9, zend-5.6, and zend-6.1 or supply a valid url to a custom web_framework cartridge. > -- Configuration Details -- > Product: Eclipse 4.4.0.20140301-1817 (org.eclipse.epp.package.jee.product) > Installed Features: > org.jboss.ide.eclipse.as.feature 3.0.0.Beta2-v20140421-1626-B483 -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17210) where is our nightly site OR why is nightly site not actually built regularly?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17210?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17210: --------------------------------------------- note, i'm asking this so tools.jboss.org links to nightly site actually works/has meaning and to get the updatesite naming schemas documented. > where is our nightly site OR why is nightly site not actually built regularly? > ------------------------------------------------------------------------------ > > Key: JBIDE-17210 > URL: https://issues.jboss.org/browse/JBIDE-17210 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > > http://download.jboss.org/jbosstools/updates/nightly/core/master > our official "nightly" updatesite has not been rebuilt for ~6 days at the time of writing. > see https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... > Why is this ? > Is there another site that can be used as "nightly" ? i.e. one that just composites instead of aggregates ? > p.s. i'm going to kick of a build so we get some fixes into the nightly. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17210) where is our nightly site OR why is nightly site not actually built regularly?

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-17210: ------------------------------------------- Summary: where is our nightly site OR why is nightly site not actually built regularly? Key: JBIDE-17210 URL: https://issues.jboss.org/browse/JBIDE-17210 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Reporter: Max Rydahl Andersen http://download.jboss.org/jbosstools/updates/nightly/core/master our official "nightly" updatesite has not been rebuilt for ~6 days at the time of writing. see https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... Why is this ? Is there another site that can be used as "nightly" ? i.e. one that just composites instead of aggregates ? p.s. i'm going to kick of a build so we get some fixes into the nightly. -- 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

11 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 April 2014