June 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-7379) Importing / Exporting of AS servers ignore command line args, filesets, xpaths, and even runtimes

by Rob Stryker (JIRA)

Importing / Exporting of AS servers ignore command line args, filesets, xpaths, and even runtimes ------------------------------------------------------------------------------------------------- Key: JBIDE-7379 URL: https://jira.jboss.org/browse/JBIDE-7379 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.Beta1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.0.Beta2, 3.2.0.CR1 Exporting of servers is incomplete. It does not export any saved filesets, xpaths, or custom launch configuration args. Importing of servers is also incomplete, not importing any of these elements. Also, while the servers themselves are imported, sometimes their runtimes are not created at all, and you get a server with no runtime. This has been very hard to track down, but no runtimeAdded event is ever fired, and in our code it looks as if they're not even created or looked for. This needs to be re-visited and tested extensively. I expect I will move import / export functionality into the AS plugin for now since hte o.j.t.runtime plugin already depends on AS. This will allow me to use classes already in the AS test suite for filesets and xpaths properly. I will keep the handler in the runtimes plugin but merely have it delegate to the functionality stored in the as plugin. It currently seems to be saving only servers and not the runtimes. -- 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, 6 months

3
9
0 / 0

[JBoss JIRA] (JBIDE-12156) Apps are not deployed after EAP 6 restart

by Martin Malina (JIRA)

Martin Malina created JBIDE-12156: ------------------------------------- Summary: Apps are not deployed after EAP 6 restart Key: JBIDE-12156 URL: https://issues.jboss.org/browse/JBIDE-12156 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 JBoss EAP 6 CR1 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 3.3.1 Found this when verifying JBIDE-11509. When you have EAP 6 up and running with an app deployed (any app, e.g. a simple dynamic web project) and then you stop and start the server, the app won't be deployed anymore. This is specific to EAP. In AS 7.1.1 the app gets deployed at the server start. With EAP 6 CR1 you will be shown this in the server log: {code} 15:46:25,828 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy {code} I understand this is an issue of EAP, but we need to decide if we can do something to overcome this limitation. -- 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, 6 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4681) investigate amazon

by Rob Stryker (JIRA)

investigate amazon ------------------ Key: JBIDE-4681 URL: https://jira.jboss.org/jira/browse/JBIDE-4681 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.1.0.M4 investigate amazon for server adapters -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

5
13
0 / 0

[JBoss JIRA] Created: (JBDS-1229) ESB binary export from JBDS doesn't include source

by Stelios Koussouris (JIRA)

ESB binary export from JBDS doesn't include source -------------------------------------------------- Key: JBDS-1229 URL: https://jira.jboss.org/browse/JBDS-1229 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: libmanagement Affects Versions: 3.0.0.GA Reporter: Stelios Koussouris Trying to export ESB binary along with the source code of a) the esb actions b) the referenced jars The result of setting the references to other projects/jars via ESB Project --> Properties --> Module Assembly and then ESB Project --> Export --> ESB --> clicking the "export source files" the jars of the referenced projects are included but no source code for nether the ESB classes or the referenced projects. -- 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, 6 months

4
6
0 / 0

[JBoss JIRA] (JBIDE-10788) Add setting ui for openshift source servers to use wtp context root if required

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-10788: ----------------------------------- Summary: Add setting ui for openshift source servers to use wtp context root if required Key: JBIDE-10788 URL: https://issues.jboss.org/browse/JBIDE-10788 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: JBossAS/Servers Affects Versions: 3.3.0.M5 Reporter: Rob Stryker Assignee: Rob Stryker Priority: Minor Fix For: 3.3.0.Beta1 link to JBIDE-10514 , a UI is required for this setting. -- 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, 6 months

1
4
0 / 0

[JBoss JIRA] (JBIDE-11517) Support for launching an AS 7.1.2 application client the "appclient.bat/sh" way

by Wolfgang Knauf (JIRA)

Wolfgang Knauf created JBIDE-11517: -------------------------------------- Summary: Support for launching an AS 7.1.2 application client the "appclient.bat/sh" way Key: JBIDE-11517 URL: https://issues.jboss.org/browse/JBIDE-11517 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Reporter: Wolfgang Knauf Assignee: Rob Stryker Priority: Minor JBoss 7.1.x introduced a new way to start a JavaEE application client: now the batch file "bin\appclient.bat" or "bin/appclient.sh" has to be used. I don't know the details of this file, but it basically starts a small application server, initializes e.g. JNDI and starts the main file of the app client. This approach is needed if the app client has to use the Environment Naming Context or even uses EJB injection. See this forum thread for some more details and a sample app: https://community.jboss.org/thread/195232 It would be very helpful (especially for newbies) if an JavaEE application client could be started the same way directly inside 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, 6 months

3
4
0 / 0

[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, 6 months

4
5
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, 6 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, 6 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, 6 months

4
8
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 June 2012