February 2015 - jbosstools-issues

[JBoss JIRA] (TOOLSDOC-561) We should mention that the internal web browser will save the RESTFUL output to a file and not display it

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-561?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-561: ------------------------------------- Sprint: 2014/S20 (27-Oct > 9-Nov), 2015/S4 (16-Feb > 01-Mar) (was: 2014/S20 (27-Oct > 9-Nov)) > We should mention that the internal web browser will save the RESTFUL output to a file and not display it > --------------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-561 > URL: https://issues.jboss.org/browse/TOOLSDOC-561 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Affects Versions: 4.2.0.Final > Environment: Build Name: 22960, Start Developing-8.0 > Build Date: 22-10-2014 11:29:36 > Topic ID: 13785-717269 [Latest] > Reporter: Len DiMaggio > Assignee: Michelle Murray > Priority: Minor > Fix For: 4.2.0.Final > > > Title: Add a RESTful Web Service > Describe the issue: > The final step in this section reads: > Open a new Web Browser and in the address bar of the Web Browser enter http://localhost:8080/ticket-monster/rest/events. This shows the output of the new RESTful endpoint. > Suggestions for improvement: > We should mention that the internal web browser will save the RESTFUL output to a file and not display it > Additional information: -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3361) Cannot install JBDS 8.0.2.GA in offline mode

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3361?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3361: ------------------------------------- {quote}the installer.jar does not get released everytime and in future is not going to be just one updatesite so just give up on using installer jar for it And to be clear, we should NOT nest JBDS TP into the JBDS Update site - the suggestion is (as I understand it) that we make an updatesite zip that composite JBDS TP and JBDS update site. Correct ? Then +1 for that idea, I would like to see the size difference of this though.{quote} That's is exactly the same thing we have in installer to combine JBDS Product and TestNG p2repos. There are composite[Artifacts|Content].xml files in the root of installer jar with references to textng and jbds sub-folders with actual p2repos. > Cannot install JBDS 8.0.2.GA in offline mode > -------------------------------------------- > > Key: JBDS-3361 > URL: https://issues.jboss.org/browse/JBDS-3361 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 8.0.2.GA > Reporter: Tomáš Sedmík > Assignee: Nick Boldt > Priority: Blocker > Fix For: 8.1.0.Beta1, 9.0.0.Alpha2 > > > Cannot install JBDS 8.0.2.GA in offline mode - see the problem > {code:borderStyle=solid} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Developer Studio (Core Features) 8.0.2.GA-v20150114-2029-B382 (com.jboss.devstudio.core.feature.feature.group 8.0.2.GA-v20150114-2029-B382) > Missing requirement: JBoss Developer Studio (Core Features) 8.0.2.GA-v20150114-2029-B382 (com.jboss.devstudio.core.feature.feature.group 8.0.2.GA-v20150114-2029-B382) requires 'org.eclipse.core.runtime.compatibility.auth 0.0.0' but it could not be found > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19376) Eclipse freezes at or shortly after startup

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19376?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19376: --------------------------------------- Could we just use org.eclipse.wst.server.ui.internal.Startup and have JBossServerCore activated right after servers are loaded? [ResourceManager.java#L245 | https://github.com/eclipse/webtools.servertools/blob/master/plugins/org.e...] > Eclipse freezes at or shortly after startup > ------------------------------------------- > > Key: JBIDE-19376 > URL: https://issues.jboss.org/browse/JBIDE-19376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.2.Final > Environment: Eclipse Luna EE. > Reporter: Anton Meller > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.3.CR1, 4.3.0.Alpha2 > > Attachments: 20150224_threaddump-1424762289905.tdump, 20150225_threaddump-1424847077811.tdump, 20150225_threaddump-1424847803263.tdump, 20150226_threaddump-1424936318015.tdump > > > Sometimes (probably once or twice a month) my eclipse freezes either right at startup or short after startup if I try to save some modified file. In Java VisualVM I can see than a deadlock in org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start() method. > Today I have updated JBoss plugins to latest version (from the update site for JBoss Tools 4.2.2.Final) and was able to reproduce the problem at every second or third startup . It looks like it occurs on larger workspaces (my current workspace has about 70 open projects (most of them are java projects and depends on each other)) and if servers view is open/visible right at startup. In a smaller workspace with only 11 projects I had no luck reproducing the deadlock. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19382) Prompt for credentials for existing v3 connection

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19382: ------------------------------------- Summary: Prompt for credentials for existing v3 connection Key: JBIDE-19382 URL: https://issues.jboss.org/browse/JBIDE-19382 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Jeff Cantrill Assignee: Jeff Cantrill -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19381) Add in ssl callback when creating v3 connection

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19381?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-19381: ---------------------------------- Summary: Add in ssl callback when creating v3 connection (was: Add in ssl credential prompt when creating v3 connection) > Add in ssl callback when creating v3 connection > ----------------------------------------------- > > Key: JBIDE-19381 > URL: https://issues.jboss.org/browse/JBIDE-19381 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Alpha2 > > > Display cert dialog similiar to v2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19376) Eclipse freezes at or shortly after startup

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19376?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19376: ------------------------------------- I don't think we should move it into ServerCorePlugin. I think the constructor for UnifiedServerListenerManager should launch a thread to initialize itself. ServerCorePlugin.start() needs to return quickly and not be doing so much stuff in wst.server.core, because it's probably triggering even more loading and potentially even loops once extension points are brought in. So I think we need ServerCorePlugin.start to complete as quick as possible and do as little as possible. But the other danger is that if others add listeners to UnifiedServerListenerManager that get missed, ie, UnifiedServerListenerManager has already started adding listeners to wst.server.core, and someone adds a new listener to UnifiedServerListenerManager which doesn't get added to wst.server.core. I'll look into it more tomorrow. > Eclipse freezes at or shortly after startup > ------------------------------------------- > > Key: JBIDE-19376 > URL: https://issues.jboss.org/browse/JBIDE-19376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.2.Final > Environment: Eclipse Luna EE. > Reporter: Anton Meller > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.3.CR1, 4.3.0.Alpha2 > > Attachments: 20150224_threaddump-1424762289905.tdump, 20150225_threaddump-1424847077811.tdump, 20150225_threaddump-1424847803263.tdump, 20150226_threaddump-1424936318015.tdump > > > Sometimes (probably once or twice a month) my eclipse freezes either right at startup or short after startup if I try to save some modified file. In Java VisualVM I can see than a deadlock in org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start() method. > Today I have updated JBoss plugins to latest version (from the update site for JBoss Tools 4.2.2.Final) and was able to reproduce the problem at every second or third startup . It looks like it occurs on larger workspaces (my current workspace has about 70 open projects (most of them are java projects and depends on each other)) and if servers view is open/visible right at startup. In a smaller workspace with only 11 projects I had no luck reproducing the deadlock. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19376) Eclipse freezes at or shortly after startup

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19376?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19376: --------------------------------------- UnifiedServerListenerManager initialization should not happen inside UnifiedServerListenerManager.getDefault(), probably we can move it in ServerCorePlugin.start right after UnifiedServerListenerManager.getDefault() call? componentcore.internal.builder triggers common.core DependencyGraph builde which in turn activates IntegrationPlugin and load UnitedServerListenerManager. UnifiedServerListenerManager tries to to add itself to all registered servers in constructor and that triggers lock 0x00000000e78ca690 on UnifiedServerListener.class instance. Then when it walks through the servers and try to call Server.removeServerListener on each instance and gets to 0x00000000e485d930 lock. Locks order is: 0x00000000e78ca690 -> 0x00000000e485d930 At the same time Servers View triggers servers initialization by iterating them in ServersView2.deferInitialization and that eventually gets to Server.getChildModules call which triggres the lock on object that is instance of Server.class 0x00000000e485d930, next it tiggers JBossServerCorePlugin loading. In turn it tries to get instance of UnifiedServerListener through synchronized getDefault() method and gets to 0x00000000e78ca690 lock. So the lock order is: 0x00000000e485d930 -> 0x00000000e78ca690 When lock are obtained in different order DL usually happens. > Eclipse freezes at or shortly after startup > ------------------------------------------- > > Key: JBIDE-19376 > URL: https://issues.jboss.org/browse/JBIDE-19376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.2.Final > Environment: Eclipse Luna EE. > Reporter: Anton Meller > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.3.CR1, 4.3.0.Alpha2 > > Attachments: 20150224_threaddump-1424762289905.tdump, 20150225_threaddump-1424847077811.tdump, 20150225_threaddump-1424847803263.tdump, 20150226_threaddump-1424936318015.tdump > > > Sometimes (probably once or twice a month) my eclipse freezes either right at startup or short after startup if I try to save some modified file. In Java VisualVM I can see than a deadlock in org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start() method. > Today I have updated JBoss plugins to latest version (from the update site for JBoss Tools 4.2.2.Final) and was able to reproduce the problem at every second or third startup . It looks like it occurs on larger workspaces (my current workspace has about 70 open projects (most of them are java projects and depends on each other)) and if servers view is open/visible right at startup. In a smaller workspace with only 11 projects I had no luck reproducing the deadlock. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19381) Add in ssl credential prompt when creating v3 connection

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19381: ------------------------------------- Summary: Add in ssl credential prompt when creating v3 connection Key: JBIDE-19381 URL: https://issues.jboss.org/browse/JBIDE-19381 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Jeff Cantrill Assignee: Jeff Cantrill Display cert dialog similiar to v2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19380) When reporting Multiple Version issues, versionwatch should omit the ones that are excluded (known issues) and show both versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19380?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19380: ------------------------------- Summary: When reporting Multiple Version issues, versionwatch should omit the ones that are excluded (known issues) and show both versions (was: When reporting Multiple Version issues, versionwatch should omit the ones that are excluded and show both versions) > When reporting Multiple Version issues, versionwatch should omit the ones that are excluded (known issues) and show both versions > --------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19380 > URL: https://issues.jboss.org/browse/JBIDE-19380 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1 > Reporter: Nick Boldt > > {code} > Multiple Version issue > org.apache.commons.logging_1.0.4.v201101211617 > org.eclipse.jdt.annotation_1.1.0.v20140129-1625 > com.jcraft.jsch_0.1.51.v201410302000 > javax.wsdl_1.5.1.v201012040544 > Ignored/known issues: > org.apache.commons.logging_1.0.4.v201101211617 > org.eclipse.jdt.annotation_1.1.0.v20140129-1625 > javax.wsdl_1.5.1.v201012040544 > {code} > Should be: > {code} > Multiple Version issue > com.jcraft.jsch_0.1.51.v201410302000 > Ignored/known issues: > org.apache.commons.logging_1.0.4.v201101211617 > org.eclipse.jdt.annotation_1.1.0.v20140129-1625 > javax.wsdl_1.5.1.v201012040544 > {code} > Or even better: > {code} > Multiple Version issue > com.jcraft.jsch_0.1.51.v201410302000 and 0.1.50.v[actual-timestamp-here] > Ignored/known issues: > org.apache.commons.logging_1.0.4.v201101211617 and [other version] > org.eclipse.jdt.annotation_1.1.0.v20140129-1625 and [other version] > javax.wsdl_1.5.1.v201012040544 and [other version] > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19380) When reporting Multiple Version issues, versionwatch should omit the ones that are excluded and show both versions

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-19380: ---------------------------------- Summary: When reporting Multiple Version issues, versionwatch should omit the ones that are excluded and show both versions Key: JBIDE-19380 URL: https://issues.jboss.org/browse/JBIDE-19380 Project: Tools (JBoss Tools) Issue Type: Bug Components: qa Affects Versions: 4.3.0.Alpha1, 4.2.3.Beta1 Reporter: Nick Boldt {code} Multiple Version issue org.apache.commons.logging_1.0.4.v201101211617 org.eclipse.jdt.annotation_1.1.0.v20140129-1625 com.jcraft.jsch_0.1.51.v201410302000 javax.wsdl_1.5.1.v201012040544 Ignored/known issues: org.apache.commons.logging_1.0.4.v201101211617 org.eclipse.jdt.annotation_1.1.0.v20140129-1625 javax.wsdl_1.5.1.v201012040544 {code} Should be: {code} Multiple Version issue com.jcraft.jsch_0.1.51.v201410302000 Ignored/known issues: org.apache.commons.logging_1.0.4.v201101211617 org.eclipse.jdt.annotation_1.1.0.v20140129-1625 javax.wsdl_1.5.1.v201012040544 {code} Or even better: {code} Multiple Version issue com.jcraft.jsch_0.1.51.v201410302000 and 0.1.50.v[actual-timestamp-here] Ignored/known issues: org.apache.commons.logging_1.0.4.v201101211617 and [other version] org.eclipse.jdt.annotation_1.1.0.v20140129-1625 and [other version] javax.wsdl_1.5.1.v201012040544 and [other version] {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

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 February 2015