May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19755) Implement ServerPort portion of wst.servertools API

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19755?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-19755: -------------------------------- Fix Version/s: 4.3.0.Beta1 > Implement ServerPort portion of wst.servertools API > --------------------------------------------------- > > Key: JBIDE-19755 > URL: https://issues.jboss.org/browse/JBIDE-19755 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Rob Stryker > Fix For: 4.3.0.Beta1 > > > WTP has support for port monitoring in it. This is a piece of code that I've neglected to implement for, oh, 9 years. I think now's the time, since [~bbrodt] has been asking about it. > Unfortunately, I've been hit by an upstream bug that hinders my progress: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466109 > To be clear, I have a proposed patch which works for HTTP monitoring but simply doesn't function for monitoring the management port due to an upstream bug. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19755) Implement ServerPort portion of wst.servertools API

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19755?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-19755: -------------------------------- Component/s: upstream > Implement ServerPort portion of wst.servertools API > --------------------------------------------------- > > Key: JBIDE-19755 > URL: https://issues.jboss.org/browse/JBIDE-19755 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Affects Versions: 4.3.0.Alpha2 > Reporter: Rob Stryker > Fix For: 4.3.0.Beta1 > > > WTP has support for port monitoring in it. This is a piece of code that I've neglected to implement for, oh, 9 years. I think now's the time, since [~bbrodt] has been asking about it. > Unfortunately, I've been hit by an upstream bug that hinders my progress: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466109 > To be clear, I have a proposed patch which works for HTTP monitoring but simply doesn't function for monitoring the management port due to an upstream bug. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19755) Implement ServerPort portion of wst.servertools API

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19755?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19755: ------------------------------------- I've pushed the patch that does an initial implementation. I would strongly suggest users do not monitor the management port at all until an upstream fix is committed. I will be writing a blog entry on how to use this in the near future, both for users and for extenders. > Implement ServerPort portion of wst.servertools API > --------------------------------------------------- > > Key: JBIDE-19755 > URL: https://issues.jboss.org/browse/JBIDE-19755 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Rob Stryker > > WTP has support for port monitoring in it. This is a piece of code that I've neglected to implement for, oh, 9 years. I think now's the time, since [~bbrodt] has been asking about it. > Unfortunately, I've been hit by an upstream bug that hinders my progress: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466109 > To be clear, I have a proposed patch which works for HTTP monitoring but simply doesn't function for monitoring the management port due to an upstream bug. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19755) Implement ServerPort portion of wst.servertools API

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-19755: ----------------------------------- Summary: Implement ServerPort portion of wst.servertools API Key: JBIDE-19755 URL: https://issues.jboss.org/browse/JBIDE-19755 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: server Affects Versions: 4.3.0.Alpha2 Reporter: Rob Stryker WTP has support for port monitoring in it. This is a piece of code that I've neglected to implement for, oh, 9 years. I think now's the time, since [~bbrodt] has been asking about it. Unfortunately, I've been hit by an upstream bug that hinders my progress: https://bugs.eclipse.org/bugs/show_bug.cgi?id=466109 To be clear, I have a proposed patch which works for HTTP monitoring but simply doesn't function for monitoring the management port due to an upstream bug. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19389) Cannot set timeout configuration to connect JDV server on Teiid designer

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19389?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19389: ------------------------------------- ... Ok so it seems I misunderstood the situation. You guys want a UI. Well, its definitely better to have one UI rather than 2, and it's obvious that the UI would belong in my codebase... but I don't exactly have the time to provide the UI given that the API exists. If you guys do go make a preference page, I would really really appreciate it if you could provide it as a patch to my codebase, so it can be in its proper repository. Would that be possible? > Cannot set timeout configuration to connect JDV server on Teiid designer > ------------------------------------------------------------------------ > > Key: JBIDE-19389 > URL: https://issues.jboss.org/browse/JBIDE-19389 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Reporter: Eiichi Nagai > Assignee: Barry LaFond > > Describe the issue: > The teiid-designer cannot connect to remote JDV server by timeout exceptions. However, the teiid-designer cannnot set timeout for it. > {noformat} > org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out > at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:336) > at org.jboss.ide.eclipse.as.internal.management.as71.JBoss71ManagerService.execute(JBoss71ManagerService.java:171) > at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87) > at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.executeRequest(JBoss7ServerUtil.java:66) > at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.isTeiidServer(JBoss7ServerUtil.java:192) > at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptJBoss7Server(TeiidServerAdapterFactory.java:181) > at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptServer(TeiidServerAdapterFactory.java:82) > at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:153) > at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125) > at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:742) > at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:650) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143) > at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.setServerStarted(ControllableServerBehavior.java:201) > at org.jboss.tools.as.core.server.controllable.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:127) > at org.jboss.ide.eclipse.as.rse.core.StandardRSEStartLaunchDelegate.preLaunchCheck(StandardRSEStartLaunchDelegate.java:72) > at org.jboss.ide.eclipse.as.rse.core.subsystems.RSECommandLineLaunchController.preLaunchCheck(RSECommandLineLaunchController.java:103) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71) > at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:325) > ... 23 more > Caused by: java.net.ConnectException: JBAS012144: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:144) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:98) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) > ... 25 more > {noformat} > Additional information: > We want to set a property of "IAS7ManagementDetails.PROPERTY_TIMEOUT" via teiid-designer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19754) Red Deer using very old target platforms from Eclipse 4.3 (Kepler)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19754?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19754: ---------------------------------- Assignee: Martin Malina > Red Deer using very old target platforms from Eclipse 4.3 (Kepler) > ------------------------------------------------------------------ > > Key: JBIDE-19754 > URL: https://issues.jboss.org/browse/JBIDE-19754 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Martin Malina > > Noticed today that the RedDeer master branch job, https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/RedDeer_master/ , uses TARGET_PLATFORM_VERSION = 4.30.6.Final and TARGET_PLATFORM_VERSION_MAXIMUM = 4.32.0.Final, which are from the JBoss Tools 4.1 (Eclipse 4.3 Kepler) days. > Shouldn't you be building with Eclipse 4.5 Mars, or at least Eclipse 4.4 Luna? > cc: [~mmalina] [~maxandersen] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19754) Red Deer using very old target platforms from Eclipse 4.3 (Kepler)

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-19754: ---------------------------------- Summary: Red Deer using very old target platforms from Eclipse 4.3 (Kepler) Key: JBIDE-19754 URL: https://issues.jboss.org/browse/JBIDE-19754 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.3.0.Beta1 Reporter: Nick Boldt Noticed today that the RedDeer master branch job, https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/RedDeer_master/ , uses TARGET_PLATFORM_VERSION = 4.30.6.Final and TARGET_PLATFORM_VERSION_MAXIMUM = 4.32.0.Final, which are from the JBoss Tools 4.1 (Eclipse 4.3 Kepler) days. Shouldn't you be building with Eclipse 4.5 Mars, or at least Eclipse 4.4 Luna? cc: [~mmalina] [~maxandersen] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19753) Investigate if Arquillian works fine with Sapphire 9.0.0

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19753?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19753: ----------------------------------- Fix Version/s: 4.3.0.Beta1 > Investigate if Arquillian works fine with Sapphire 9.0.0 > -------------------------------------------------------- > > Key: JBIDE-19753 > URL: https://issues.jboss.org/browse/JBIDE-19753 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: arquillian > Reporter: Alexey Kazakov > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.3.0.Beta1 > > > Currently JBT TP includes Sapphire 9.0.0.201408261741 (available in Eclipse Mars M6 update site). > I just checked the latest nightly build from https://hudson.eclipse.org/sapphire/job/9.0.x/ and I see that some Sapphire API has been changed. We have compilation problems in Batch because of it. > Sapphire is gonna be updated in Mars M7 - https://www.eclipse.org/forums/index.php/t/1066214/ > And we have to switch to the new API in Batch in JBT 4.3.0.Beta1 and update Sapphire in our TP. > So, we also should make sure that Arquillian supports the latest Sapphire 9.0.0.x. Otherwise we will get a problem with two components (Batch and Arquillian) which depends on two incompatible versions of Sapphire. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3425) Disable Unintsaller generation for Mac OS X

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3425?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3425: -------------------------------- Sprint: Sprint #3 May 2015 (was: Sprint #2 April 2015) > Disable Unintsaller generation for Mac OS X > ------------------------------------------- > > Key: JBDS-3425 > URL: https://issues.jboss.org/browse/JBDS-3425 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.Beta1 > > > Uninstaller doesn't make sense for Mac platform, because it is literally just removing .app package. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3411) have installer build actually use M6 p2 product build

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3411?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3411: -------------------------------- Sprint: Sprint #3 May 2015 (was: Sprint #2 April 2015) > have installer build actually use M6 p2 product build > ----------------------------------------------------- > > Key: JBDS-3411 > URL: https://issues.jboss.org/browse/JBDS-3411 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer, updatesite > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.Beta1 > > > talking with [~prapicault] I learned that since M6 the following changes are required for proper working p2 product/osx build: > {code} > <products> > <product> > ... > <rootFolders> > <macosx>MyProduct.app</macosx> > </rootFolders> > </product> > {code} > And to use tycho 0.23-snapshot -- 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