May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19738) Failed runtime download offers no error message

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19738?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-19738. --------------------------------- Resolution: Done pushed to master. Message is now more informative. > Failed runtime download offers no error message > ----------------------------------------------- > > Key: JBIDE-19738 > URL: https://issues.jboss.org/browse/JBIDE-19738 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.2.3.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > While verifying JBIDE-19571 the runtime download failed and there was no error whatsoever. The download of FSW 6.0 almost started, but after a few seconds on the progress bar an error window showed up for a moment and then disappeared again and the download window was gone, too. After this, there was no error in the error view or the workspace log. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19641: ------------------------------------- [~mmalina] Some more details here would be helpful. Seems to work for me =/ > Big war deployment via management API gets stuck > ------------------------------------------------ > > Key: JBIDE-19641 > URL: https://issues.jboss.org/browse/JBIDE-19641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it will not go through. > This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually used that JIRA to fix a side issue - the stuck operation could not be canceled. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19854) When Wildfly starts in debug mode occurs ClassNotFoundException with org.jboss.modules.Main

by Giancarlo giulian (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19854?page=com.atlassian.jira.plugi... ] Giancarlo giulian updated JBIDE-19854: -------------------------------------- Attachment: image3.png Classpath > When Wildfly starts in debug mode occurs ClassNotFoundException with org.jboss.modules.Main > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19854 > URL: https://issues.jboss.org/browse/JBIDE-19854 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: OS: Windows 8.1; Intel Core i3 540 3.07Ghz; 4GB DDR3 1333Mhz; Java Version 1.7.0_75; > Reporter: Giancarlo giulian > Labels: classnotfound, debug, debugging, jboss, main, wildfly > Attachments: image2.png, image3.png, imagem1.png > > > This problem has recently begun, before that is it working in debug mode. Errors log are not created and doesn't appear in console output using Eclipse Luna. > Program Arguments: > {quote} > -mp "C:/wildfly-8.1/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\wildfly-8.1\standalone > {quote} > VM Arguments: > {quote} > "-Dprogram.name=JBossTools: WildFly 8.1" -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=C:/wildfly-8.1/standalone/log/boot.log" "-Dlogging.configuration=file:/C:/wildfly-8.1/standalone/configuration/logging.properties" "-Djboss.home.dir=C:/wildfly-8.1" -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost > {quote} > Images: > https://www.dropbox.com/s/g0hdwh1tz543q1p/imagem1.png > https://www.dropbox.com/s/ivpnd3ggaprtl2v/image2.png -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19854) When Wildfly starts in debug mode occurs ClassNotFoundException with org.jboss.modules.Main

by Giancarlo giulian (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19854?page=com.atlassian.jira.plugi... ] Giancarlo giulian updated JBIDE-19854: -------------------------------------- Description: This problem has recently begun, before that is it working in debug mode. Errors log are not created and doesn't appear in console output using Eclipse Luna. Program Arguments: {quote} -mp "C:/wildfly-8.1/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\wildfly-8.1\standalone {quote} VM Arguments: {quote} "-Dprogram.name=JBossTools: WildFly 8.1" -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=C:/wildfly-8.1/standalone/log/boot.log" "-Dlogging.configuration=file:/C:/wildfly-8.1/standalone/configuration/logging.properties" "-Djboss.home.dir=C:/wildfly-8.1" -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost {quote} Images: https://www.dropbox.com/s/g0hdwh1tz543q1p/imagem1.png https://www.dropbox.com/s/ivpnd3ggaprtl2v/image2.png was: This problem has recently begun, before that is it working in debug mode. Errors log are not created and doesn't appear in console output using Eclipse Luna. Images: https://www.dropbox.com/s/g0hdwh1tz543q1p/imagem1.png https://www.dropbox.com/s/ivpnd3ggaprtl2v/image2.png > When Wildfly starts in debug mode occurs ClassNotFoundException with org.jboss.modules.Main > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19854 > URL: https://issues.jboss.org/browse/JBIDE-19854 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: OS: Windows 8.1; Intel Core i3 540 3.07Ghz; 4GB DDR3 1333Mhz; Java Version 1.7.0_75; > Reporter: Giancarlo giulian > Labels: classnotfound, debug, debugging, jboss, main, wildfly > Attachments: image2.png, imagem1.png > > > This problem has recently begun, before that is it working in debug mode. Errors log are not created and doesn't appear in console output using Eclipse Luna. > Program Arguments: > {quote} > -mp "C:/wildfly-8.1/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\wildfly-8.1\standalone > {quote} > VM Arguments: > {quote} > "-Dprogram.name=JBossTools: WildFly 8.1" -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=C:/wildfly-8.1/standalone/log/boot.log" "-Dlogging.configuration=file:/C:/wildfly-8.1/standalone/configuration/logging.properties" "-Djboss.home.dir=C:/wildfly-8.1" -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost > {quote} > Images: > https://www.dropbox.com/s/g0hdwh1tz543q1p/imagem1.png > https://www.dropbox.com/s/ivpnd3ggaprtl2v/image2.png -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19847) Central doesn't load - Extract central page error - File name too long

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19847?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19847: -------------------------------- Sprint: Sprint #4 May 2015 > Central doesn't load - Extract central page error - File name too long > ---------------------------------------------------------------------- > > Key: JBIDE-19847 > URL: https://issues.jboss.org/browse/JBIDE-19847 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Beta1 > Environment: Mars M7, > JBT nigtly from 2015-05-24 > Reporter: Pavol Srna > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: central-err.png > > > {code} > IO error > IO error > /home/psrna/data/testing/workspaces/e18/.metadata/.plugins/org.jboss.tools.foundation.core/ECF_REMOTE_CACHE/https___repository_jboss_org_nexus_content_groups_public_jboss_org_jboss_tools_central_jbosstools_central_webpage_0_0_1_SNAPSHOT_jbosstools_central_webpage_0_0_1_20150525_145248_3_zip-1043033484887124864.tmp (File name too long) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19500) warn/inform users running on non-compatilbe JVMs they are loosing out on features

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19500?page=com.atlassian.jira.plugi... ] Daniel Azarov edited comment on JBIDE-19500 at 5/26/15 12:52 PM: ----------------------------------------------------------------- In order to have this worked we need to put this in the plugin with the lowest "Required Execution Environment". And foundation.core should depend on this plugin (In order to have this plugin installed). May be JavaSE-1.4 or so. Otherwise plugin which contains this functionality will not be loaded too. So user will never see this warning. [~maxandersen], What do you think? was (Author: dazarov): In order to have this worked we need to put this in the plugin with the lowest "Required Execution Environment". May be JavaSE-1.4 or so. Otherwise plugin which contains this functionality will not be loaded too. So user will never see this warning. [~maxandersen], What do you think? > warn/inform users running on non-compatilbe JVMs they are loosing out on features > --------------------------------------------------------------------------------- > > Key: JBIDE-19500 > URL: https://issues.jboss.org/browse/JBIDE-19500 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Reporter: Max Rydahl Andersen > Assignee: Daniel Azarov > Fix For: 4.3.0.Beta1 > > Attachments: JVMProblemDetector.png, JVMProblemDetector2.png > > > while reading https://developer.jboss.org/message/922318?et=watches.email.thread#922318 I got the idea that we could have a startup plugin that detects if the error log has lines matching: > {code} > org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.preferences [1447] > Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))" > {code} > and there by tell them that they need to run JavaSE 1.7 to get this to work. > This dialog should show up and have "don't disturb me again" for the specific bundle/feature that is filtered out. > This is to warn those users that run ecipse with default javavm that still is java 6 on many installs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19854) When Wildfly starts in debug mode occurs ClassNotFoundException with org.jboss.modules.Main

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19854?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19854: ------------------------------------- Some steps to replicate would be very helpful. Other things you can do to help us debug is to double-click your server to open the server editor, then click "Open Launch Configuration" and paste us the vm-args nad prog-args sections. Also, move to the 'classpath' tab and verify what is on the classpath. > When Wildfly starts in debug mode occurs ClassNotFoundException with org.jboss.modules.Main > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19854 > URL: https://issues.jboss.org/browse/JBIDE-19854 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: OS: Windows 8.1; Intel Core i3 540 3.07Ghz; 4GB DDR3 1333Mhz; Java Version 1.7.0_75; > Reporter: Giancarlo giulian > Labels: classnotfound, debug, debugging, jboss, main, wildfly > Attachments: image2.png, imagem1.png > > > This problem has recently begun, before that is it working in debug mode. Errors log are not created and doesn't appear in console output using Eclipse Luna. > Images: > https://www.dropbox.com/s/g0hdwh1tz543q1p/imagem1.png > https://www.dropbox.com/s/ivpnd3ggaprtl2v/image2.png -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19852) Set default path for runtimes downloaded and installed via java -jar

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19852?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19852: ------------------------------------- Yes, this obviously won't be possible in existing installers, but it would be nice if we could get a sysprop we can set when running java -jar that would set the default value for installation folder. I'm not sure who we would talk to regarding getting this uniformly implemented across all our installers, though. > Set default path for runtimes downloaded and installed via java -jar > -------------------------------------------------------------------- > > Key: JBIDE-19852 > URL: https://issues.jboss.org/browse/JBIDE-19852 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection, server > Affects Versions: 4.3.0.Alpha2 > Reporter: Radim Hopp > > I'm not sure if this is possible, but it would be nice if the installer would fill the installation path from Download Runtime wizard. > The same for runtime detection after the download and installation is finished. > Example scenario: > 1. Select JBoss DV 6.1 for download&installation > 2. On "Download Runtime" page of wizard fill some install folder (for example /home/<user>/downloadedDV) > 3. Click Finish - DV is downloaded and it's installer executed > ASSERT: /home/<user>/downloadedDV is default installation path in installer > 4. In the installer select different installation folder (for example /home/<user>/DV) > 5. Finish installer > ASSERT: /home/<user>/DV is added to runtime-detection paths instead of /home/<user>/downloadedDV -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19500) warn/inform users running on non-compatilbe JVMs they are loosing out on features

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19500?page=com.atlassian.jira.plugi... ] Daniel Azarov commented on JBIDE-19500: --------------------------------------- In order to have this worked we need to put this in the plugin with the lowest "Required Execution Environment". May be JavaSE-1.4 or so. Otherwise plugin which contains this functionality will not be loaded too. So user will never see this warning. [~maxandersen], What do you think? > warn/inform users running on non-compatilbe JVMs they are loosing out on features > --------------------------------------------------------------------------------- > > Key: JBIDE-19500 > URL: https://issues.jboss.org/browse/JBIDE-19500 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Reporter: Max Rydahl Andersen > Assignee: Daniel Azarov > Fix For: 4.3.0.Beta1 > > Attachments: JVMProblemDetector.png, JVMProblemDetector2.png > > > while reading https://developer.jboss.org/message/922318?et=watches.email.thread#922318 I got the idea that we could have a startup plugin that detects if the error log has lines matching: > {code} > org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.preferences [1447] > Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))" > {code} > and there by tell them that they need to run JavaSE 1.7 to get this to work. > This dialog should show up and have "don't disturb me again" for the specific bundle/feature that is filtered out. > This is to warn those users that run ecipse with default javavm that still is java 6 on many installs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19500) warn/inform users running on non-compatilbe JVMs they are loosing out on features

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19500?page=com.atlassian.jira.plugi... ] Daniel Azarov reassigned JBIDE-19500: ------------------------------------- Assignee: Daniel Azarov (was: Alexey Kazakov) > warn/inform users running on non-compatilbe JVMs they are loosing out on features > --------------------------------------------------------------------------------- > > Key: JBIDE-19500 > URL: https://issues.jboss.org/browse/JBIDE-19500 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Reporter: Max Rydahl Andersen > Assignee: Daniel Azarov > Fix For: 4.3.0.Beta1 > > Attachments: JVMProblemDetector.png, JVMProblemDetector2.png > > > while reading https://developer.jboss.org/message/922318?et=watches.email.thread#922318 I got the idea that we could have a startup plugin that detects if the error log has lines matching: > {code} > org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.preferences [1447] > Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))" > {code} > and there by tell them that they need to run JavaSE 1.7 to get this to work. > This dialog should show up and have "don't disturb me again" for the specific bundle/feature that is filtered out. > This is to warn those users that run ecipse with default javavm that still is java 6 on many installs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 May 2015