[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
[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
[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