[JBoss JIRA] (JBIDE-12537) "Unable to reach JBoss instance" error when stopping JBoss AS 7.1
by Jaroslav Jankovič (JIRA)
Jaroslav Jankovič created JBIDE-12537:
-----------------------------------------
Summary: "Unable to reach JBoss instance" error when stopping JBoss AS 7.1
Key: JBIDE-12537
URL: https://issues.jboss.org/browse/JBIDE-12537
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.0.0.Alpha1
Reporter: Jaroslav Jankovič
Assignee: Rob Stryker
Fix For: 4.0.0.Alpha2
After AS 7.1 is stopped running, there is a job in JBT trying to connect via jmx, which fails - error is thrown in Error log:
{code}
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.connect(RemotingConnector.java:154)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:267)
at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:67)
... 6 more
{code}
I am able to reproduce it only on AS 7.1(7.1.0, 7.1.1) runtimes instances. On AS 7.0 there is no such issue.
--
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, 6 months
[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, 6 months
[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, 6 months
[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, 6 months
[JBoss JIRA] (JBIDE-12653) Some plugins aren't marked as Alfa1
by Jiri Peterka (JIRA)
Jiri Peterka created JBIDE-12653:
------------------------------------
Summary: Some plugins aren't marked as Alfa1
Key: JBIDE-12653
URL: https://issues.jboss.org/browse/JBIDE-12653
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 4.0.0.Alpha1
Environment: JBDS 6.Alfa1b
Reporter: Jiri Peterka
Assignee: Nick Boldt
Fix For: 4.0.0.Alpha2
There is related output form checking script:
[ERROR] org.jboss.netty_3.2.5.Final-20120529-1956.jar not matching plugin pattern org\.jboss.*\.Alpha1.*
[ERROR] org.jboss.tools.maven.apt.core_1.0.0.201206052025.jar not matching plugin pattern org\.jboss.*\.Alpha1.*
[ERROR] org.jboss.tools.maven.apt.ui_1.0.0.201206052025.jar not matching plugin pattern org\.jboss.*\.Alpha1.*
--
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, 6 months