August 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10023) When hot code replace fails, offer "restart deployment "as an alternative

by Max Rydahl Andersen (Created) (JIRA)

When hot code replace fails, offer "restart deployment "as an alternative ------------------------------------------------------------------------- Key: JBIDE-10023 URL: https://issues.jboss.org/browse/JBIDE-10023 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Reporter: Gavin King Assignee: Rob Stryker Priority: Optional The dialog box t hat eclipse pops up when hot code replace fails is very irritating, but it would be less irritating if it offered "restart deployment" as an alternative. Actually it should be smart enough to NOT pop this dialog at all for classes in src/action. So I think the Seam tools need to hijack this whole feature of eclipse. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

4
5
0 / 0

[JBoss JIRA] (JBIDE-12468) Re-organization of the "common" component

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-12468: ----------------------------------- Summary: Re-organization of the "common" component Key: JBIDE-12468 URL: https://issues.jboss.org/browse/JBIDE-12468 Project: Tools (JBoss Tools) Issue Type: Task Components: common/jst/core Affects Versions: 4.0.0.M1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.0.0.M1 This jira is here to track the jbosstools 4.0.0 reorganization of the 'common' component. As was discussed on the mailing lists, some plugins should be split, some merged, some deleted / deprecated, etc. This jira will act as the enclosing jira for several to-be-determined subtasks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] (JBIDE-12109) JMX connection to AS7/EAP6 not working if server started with Java 1.7

by Martin Malina (JIRA)

Martin Malina created JBIDE-12109: ------------------------------------- Summary: JMX connection to AS7/EAP6 not working if server started with Java 1.7 Key: JBIDE-12109 URL: https://issues.jboss.org/browse/JBIDE-12109 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.CR1 Environment: jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar Reporter: Martin Malina Assignee: Rob Stryker Fix For: 3.3.1 When you set up your AS7/EAP6 server to use Java 1.7 runtime, the tooling fails to connect to the server via JMX. The error in the log is: {code} !ENTRY org.jboss.ide.eclipse.as.jmx.integration 4 0 2012-06-06 12:17:52.897 !MESSAGE Error connecting to jmx for server jboss-eap-6.0.0.CR1 !STACK 1 org.jboss.tools.jmx.core.JMXException: Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:78) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:138) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:111) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:221) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:213) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.lang.RuntimeException: Operation failed with status WAITING at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:168) at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:67) ... 6 more !SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2012-06-06 12:17:52.897 !MESSAGE Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property !STACK 0 java.lang.RuntimeException: Operation failed with status WAITING at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:168) at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:67) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:138) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:111) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:221) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:213) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} This has several consequences: - server cannot be connected in MBean Explorer - management startup poller does not work and hence the server keeps starting forever until it reaches timeout (and then it tries to stop the server, but fails to do so - see below) - server fails to stop because it seems it tries to do so using management service, second attempt kills the process successfully Unfortunately I didn't catch this earlier. AS7/EAP6 with Java 1.7 worked for me in JBDS in the past, but that was probably before the jmx connection started working correctly at all. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-473) JBoss AS ignores context root property of dynamic web project

by Viacheslav Kabanovich (JIRA)

JBoss AS ignores context root property of dynamic web project ------------------------------------------------------------- Key: JBIDE-473 URL: http://jira.jboss.com/jira/browse/JBIDE-473 Project: JBoss Tools Issue Type: Feature Request Reporter: Viacheslav Kabanovich Open editor for Tomcat Server (double click Tomcat node in Servers view). The editor has two tabs - Overview and Modules. In Modules tab, it is possible to select a registered web project and call dialog for changing path (context root) property by Edit button. Then, for example, if project's name is MyProject but path is set to /OurProject, in order to access the application running on Tomcat server one has to type in browser an address like http://localhost:8080/OurProject rather than http://localhost:8080/MyProject. Red Hat studio defines menu action 'Register Web Context in Server', which invokes dialog that allows to set context root property. That works fine with Tomcat server, but fails with JBoss AS, because it seems that its implementation ignores this property of web project when deploying it. Hence, the request is to develop this functionality of JBoss AS to the level of Tomcat server. Context root property is accessible through class org.eclipse.wst.common.componentcore.internal.util.ComponentUtilities with methods public static void setServerContextRoot(IProject project, String contextRoot) public static String getServerContextRoot(IProject project) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

8
22
0 / 0

[JBoss JIRA] Created: (JBIDE-2278) Group JBoss Servers into a JBoss Cluster and allow cluster wide operations

by Galder Zamarreno (JIRA)

Group JBoss Servers into a JBoss Cluster and allow cluster wide operations -------------------------------------------------------------------------- Key: JBIDE-2278 URL: http://jira.jboss.com/jira/browse/JBIDE-2278 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: Galder Zamarreno Thinking about this, maybe in the future you can group servers together as a cluster, and click on something like: "Start Cluster". JB Tools would then start each server separated by a configurable time. For example: - start server 1, wait X seconds - start server 2, wait X seconds - start server 3, wait X seconds. ... That would safe me having to click 3 times start... :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-7515) Add (optional) start/stop script to the Deploy only server

by Max Andersen (JIRA)

Add (optional) start/stop script to the Deploy only server ---------------------------------------------------------- Key: JBIDE-7515 URL: https://jira.jboss.org/browse/JBIDE-7515 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: Max Andersen Assignee: Rob Stryker Fix For: 3.2.0.Beta2, 3.2.x Currently the "Deploy only" server can just "deploy" - I suggest we add support for running a start (and optional) a stop script to let users start/stop what they want. This would be a nice stop-gap feature for things like AS 7 or other runtimes out in the world until "native" integration is possible. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
5
0 / 0

[JBoss JIRA] (JBDS-2084) Add new status for when a deployment fails on server

by Mustafa Musaji (JIRA)

Mustafa Musaji created JBDS-2084: ------------------------------------ Summary: Add new status for when a deployment fails on server Key: JBDS-2084 URL: https://issues.jboss.org/browse/JBDS-2084 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: servers Affects Versions: 5.0.0.Beta1 Environment: JBoss Developer Studio 5 Beta JBoss Enterprise Application 6 Beta Reporter: Mustafa Musaji Priority: Minor When deployment of an application fails on JBoss EAP, JBoss Tools doesn't recognize this as failure and continues to report the status as [Started, Synchronized]. This a request to add the ability for JBDS to report back via the console when a deployment fails due to application errors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8276) Suggest removing related servers when removing RSE connection

by Libor Zoubek (JIRA)

Suggest removing related servers when removing RSE connection ------------------------------------------------------------- Key: JBIDE-8276 URL: https://issues.jboss.org/browse/JBIDE-8276 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: Libor Zoubek Assignee: Rob Stryker If a server is created using deltacloud it is related to RSE connection. If user removes RSE Connection and then tries to start server, he gets error about possibly deleted connection, which is fine. Is it possible to suggest him deleting related servers when deleting RSE Connection like it is when server runtime is deleted? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

5
7
0 / 0

[JBoss JIRA] (JBIDE-12524) Move loading of extension points to a clean model class

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-12524: ----------------------------------- Summary: Move loading of extension points to a clean model class Key: JBIDE-12524 URL: https://issues.jboss.org/browse/JBIDE-12524 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Rob Stryker The extension loading should be in a dedicated class. -- 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

13 years, 8 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-12016) OpenShift Wizard - SSH2 Preferences

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-12016: ----------------------------------- Summary: OpenShift Wizard - SSH2 Preferences Key: JBIDE-12016 URL: https://issues.jboss.org/browse/JBIDE-12016 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Reporter: Burr Sutter Assignee: Andre Dietisheim Attachments: Screen Shot 2012-05-25 at 10.57.18 AM.png If the end-user's .ssh directory is empty - we should provide a stronger warning for them - ideally provide a URL to some documentation/video explaining how the user can use Eclipse/JBoss Tools to create their private/public keys - so they can then upload the .pub to OpenShift. At least 10 users failed this test today and had to be "handheld" through the process. What is worse, if the end-user uploads a slightly butchered pub key - the create application phase still works but the git clone fails - with a relatively poor error message - recovery normally means having to go up to the OpenShift console, deleting the poorly created apps - getting the pub key uploaded correctly (deleting the previous one) and starting again. The fact that Eclipse could create the keys was actually unknown by the instructor's of today's class. SSH is still a nightmare for the newbie trying to use OpenShift + JBDS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
32
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 August 2012