September 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-3064) New JBDS 8 Welcome screen graphics

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3064?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3064: -------------------------------------- Fix Version/s: 8.0.1.GA 9.0.0.Alpha1 (was: 8.0.0.CR2) > New JBDS 8 Welcome screen graphics > ---------------------------------- > > Key: JBDS-3064 > URL: https://issues.jboss.org/browse/JBDS-3064 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: ui/branding > Affects Versions: 8.0.0.Beta2 > Reporter: Pavol Srna > Fix For: 8.0.1.GA, 9.0.0.Alpha1 > > > JBDS 8 comes with new splash and installer graphics (see https://issues.jboss.org/browse/JBDS-3036) > It would be good to have new graphics also for the Welcome screen. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-16066: ------------------------------------------- As far as JBDS 7.1 and deploying to EAP 6.1, I'm seeing an ear in the /standalone/deployments directory with a contained war and classes in the jar in there. > Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16066 > URL: https://issues.jboss.org/browse/JBIDE-16066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1, EAP-6.1 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Fix For: 4.2.0.CR2 > > Attachments: topDownServer.log > > > Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible. > It works with other slider levels and all levels works when the server isn't started before the web service is created. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3057) JBDS causes "not responding" message on RHEL

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBDS-3057?page=com.atlassian.jira.plugin.... ] Jiri Peterka commented on JBDS-3057: ------------------------------------ No, it still here when you're using Gnome Shell as your window manager. > JBDS causes "not responding" message on RHEL > -------------------------------------------- > > Key: JBDS-3057 > URL: https://issues.jboss.org/browse/JBDS-3057 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: upstream > Affects Versions: 7.1.1.GA > Environment: RHEL 7 Beta > OpenJDK 1.7 > JBDS 7.1.1 > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 8.0.0.GA > > Attachments: jbds-not-responding.png > > > I was smoke testing JBDS 7 on RHEL 7 Beta and every time I started JBDS with a new workspace, I got a "not responding" window where I could either force quit JBDS or wait. > Obviously this is due to some limit that is set in the OS and when reached, this popup is shown. > On subsequent starts of JBDS with the same workspace, this does not happen. > The system was a VirtualBox VM run on Windows, but there was nothing else happening on the machine, so this shouldn't slow things down too much. Also, the machine has 8 GB of RAM out of which 4 GB was dedicated to the VM. So I don't think the HW is particularly slow. > I understand that this JIRA is very vague, but maybe it's worth trying to find if it's caused by some synchronous processes that we run at JBDS start. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18399) JBT website "What's new" page missing Alpha-Beta3 new features

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18399?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-18399: --------------------------------------- [~maxandersen], [~mmurray], let me check that. > JBT website "What's new" page missing Alpha-Beta3 new features > -------------------------------------------------------------- > > Key: JBIDE-18399 > URL: https://issues.jboss.org/browse/JBIDE-18399 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.2.0.CR1 > Reporter: Michelle Murray > Assignee: Xavier Coulon > Fix For: 4.2.0.Final > > > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.0.CR1.html > Alpha-Beta3 tabs for 4.2.0 have been removed with the release of CR1. Now it looks like the only improvements since 4.2.1 are those listed for CR1. I assume for the 4.2.0.Final release all of the "What's new" for Alpha-Beta3-CR2 will all be combined into one tab titled 4.2.0.Final. Until then, can the Alpha-Beta3 pages be reinstated? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16066: --------------------------------------------- can you get a jstack for the eclipse process ? > Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16066 > URL: https://issues.jboss.org/browse/JBIDE-16066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1, EAP-6.1 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Fix For: 4.2.0.CR2 > > Attachments: topDownServer.log > > > Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible. > It works with other slider levels and all levels works when the server isn't started before the web service is created. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18366) Sometimes, EAP6/WildFly8/AS7 fails to start - Failed initializing module org.jboss.as.logging

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18366?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18366: ---------------------------------------- Fix Version/s: 4.2.0.CR2 (was: 4.2.x) > Sometimes, EAP6/WildFly8/AS7 fails to start - Failed initializing module org.jboss.as.logging > --------------------------------------------------------------------------------------------- > > Key: JBIDE-18366 > URL: https://issues.jboss.org/browse/JBIDE-18366 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR2 > > > Sometimes, right after start of the IDE, a server fails to start. When this happens, it produces something like this in the server log: > {code} > INFO: JBoss MSC version 1.1.5.Final-redhat-1 > Sep 17, 2014 11:27:40 AM org.jboss.as.server.ApplicationServerService start > INFO: JBAS015899: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) starting > Sep 17, 2014 11:27:40 AM org.jboss.as.controller.AbstractOperationContext executeStep > ERROR: JBAS014612: Operation ("parallel-extension-add") failed - address: ([]) > java.lang.RuntimeException: JBAS014670: Failed initializing module org.jboss.as.logging > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:111) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:611) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:489) > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:290) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:285) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1132) > at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:299) > at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:292) > at org.jboss.as.server.ServerService.boot(ServerService.java:346) > at org.jboss.as.server.ServerService.boot(ServerService.java:321) > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:254) > at java.lang.Thread.run(Thread.java:695) > Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager" > at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) > at java.util.concurrent.FutureTask.get(FutureTask.java:83) > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:103) > ... 11 more > Caused by: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager" > at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:106) > at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:97) > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:139) > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:125) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:695) > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > Sep 17, 2014 11:27:40 AM org.jboss.as.server.ServerService boot > FATAL: JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > {code} > Unfortunately I don't have a reliable way to reproduce this. It happened to me like 3 times over the last few days. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18366) Sometimes, EAP6/WildFly8/AS7 fails to start - Failed initializing module org.jboss.as.logging

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18366?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-18366: -------------------------------------- Which OS? JVM? > Sometimes, EAP6/WildFly8/AS7 fails to start - Failed initializing module org.jboss.as.logging > --------------------------------------------------------------------------------------------- > > Key: JBIDE-18366 > URL: https://issues.jboss.org/browse/JBIDE-18366 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR2 > > > Sometimes, right after start of the IDE, a server fails to start. When this happens, it produces something like this in the server log: > {code} > INFO: JBoss MSC version 1.1.5.Final-redhat-1 > Sep 17, 2014 11:27:40 AM org.jboss.as.server.ApplicationServerService start > INFO: JBAS015899: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) starting > Sep 17, 2014 11:27:40 AM org.jboss.as.controller.AbstractOperationContext executeStep > ERROR: JBAS014612: Operation ("parallel-extension-add") failed - address: ([]) > java.lang.RuntimeException: JBAS014670: Failed initializing module org.jboss.as.logging > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:111) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:611) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:489) > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:290) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:285) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1132) > at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:299) > at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:292) > at org.jboss.as.server.ServerService.boot(ServerService.java:346) > at org.jboss.as.server.ServerService.boot(ServerService.java:321) > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:254) > at java.lang.Thread.run(Thread.java:695) > Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager" > at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) > at java.util.concurrent.FutureTask.get(FutureTask.java:83) > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:103) > ... 11 more > Caused by: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager" > at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:106) > at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:97) > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:139) > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:125) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:695) > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > Sep 17, 2014 11:27:40 AM org.jboss.as.server.ServerService boot > FATAL: JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > {code} > Unfortunately I don't have a reliable way to reproduce this. It happened to me like 3 times over the last few days. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18399) JBT website "What's new" page missing Alpha-Beta3 new features

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18399?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18399: ---------------------------------------- Fix Version/s: 4.2.0.Final (was: 4.2.0.CR2) > JBT website "What's new" page missing Alpha-Beta3 new features > -------------------------------------------------------------- > > Key: JBIDE-18399 > URL: https://issues.jboss.org/browse/JBIDE-18399 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.2.0.CR1 > Reporter: Michelle Murray > Fix For: 4.2.0.Final > > > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.0.CR1.html > Alpha-Beta3 tabs for 4.2.0 have been removed with the release of CR1. Now it looks like the only improvements since 4.2.1 are those listed for CR1. I assume for the 4.2.0.Final release all of the "What's new" for Alpha-Beta3-CR2 will all be combined into one tab titled 4.2.0.Final. Until then, can the Alpha-Beta3 pages be reinstated? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18399) JBT website "What's new" page missing Alpha-Beta3 new features

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18399?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18399: -------------------------------- Assignee: Xavier Coulon > JBT website "What's new" page missing Alpha-Beta3 new features > -------------------------------------------------------------- > > Key: JBIDE-18399 > URL: https://issues.jboss.org/browse/JBIDE-18399 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.2.0.CR1 > Reporter: Michelle Murray > Assignee: Xavier Coulon > Fix For: 4.2.0.Final > > > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.0.CR1.html > Alpha-Beta3 tabs for 4.2.0 have been removed with the release of CR1. Now it looks like the only improvements since 4.2.1 are those listed for CR1. I assume for the 4.2.0.Final release all of the "What's new" for Alpha-Beta3-CR2 will all be combined into one tab titled 4.2.0.Final. Until then, can the Alpha-Beta3 pages be reinstated? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18054) Visual Preview page is empty for Ionic myApp project index.html

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18054?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-18054: ------------------------------------------- Assignee: Max Rydahl Andersen (was: Konstantin Marmalyukov) > Visual Preview page is empty for Ionic myApp project index.html > --------------------------------------------------------------- > > Key: JBIDE-18054 > URL: https://issues.jboss.org/browse/JBIDE-18054 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta3 > Environment: Linux x86_64 > Reporter: Denis Golovin > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.CR2 > > Attachments: alert.png, ionic-index-html.png > > > Create Ionic myApp foloving instructions on http://ionicframework.com/getting-started/. > Import it using Thym Import Project and open www/index.html in visual editor. The result is almost empty page > !ionic-index-html.png! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2014