July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17640) there is a 'com.fusesource.ide.jvmmonitor' in my processes - jvmmonitor agent project moved + renamed into jbt-server repo

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17640?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17640: -------------------------------- Summary: there is a 'com.fusesource.ide.jvmmonitor' in my processes - jvmmonitor agent project moved + renamed into jbt-server repo (was: there is a 'com.fusesource.ide.jvmmonitor' in my processes) > there is a 'com.fusesource.ide.jvmmonitor' in my processes - jvmmonitor agent project moved + renamed into jbt-server repo > --------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-17640 > URL: https://issues.jboss.org/browse/JBIDE-17640 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Reporter: Max Rydahl Andersen > Fix For: 4.2.0.Beta3 > > > when connecting to a process even when I dont have fusesource ide installed an mbean called "com.fusesource.ide.jvmmonitor" shows up. > I reckon this is a missing refactoring/renaming in the migration. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17312) [API Deficiency] JVM Monitor jvms unable to access raw startup command

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17312?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17312. --------------------------------- Assignee: Rob Stryker Resolution: Done This API was added > [API Deficiency] JVM Monitor jvms unable to access raw startup command > ---------------------------------------------------------------------- > > Key: JBIDE-17312 > URL: https://issues.jboss.org/browse/JBIDE-17312 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Beta3 > > > When turning a given JVM object into a JMX server connection, the underlying impl only exposes the name of the main class that was used to start the process. This is not enough information to correctly differentiate various server types from each other. > This is a pre-requisite to accurately detecting duplicates in the JMX view and ensuring they don't pollute the view. It's also important to correctly match detected jvms with top-level jmx connection nodes such as the Wildfly nodes or EAP nodes. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17700) Cannot deploy jsf war with eclipse luna and jboss 7.1.x

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17700: ------------------------------------- Adding forge and maven to component list for wider visibility. > Cannot deploy jsf war with eclipse luna and jboss 7.1.x > ------------------------------------------------------- > > Key: JBIDE-17700 > URL: https://issues.jboss.org/browse/JBIDE-17700 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, maven, server > Environment: Win 7, Eclilpse Luna, JBoss Tools (via market place) > Reporter: Oliver Pfau > Priority: Critical > > When I publish my war to jboss 7.1 the following error occurs: > An internal error occurred during: "Publishing to JBoss AS 7.1...". > Could not initialize class de.schlichtherle.io.ArchiveControllers -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17700) Cannot deploy jsf war with eclipse luna and jboss 7.1.x

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17700: -------------------------------- Component/s: forge maven > Cannot deploy jsf war with eclipse luna and jboss 7.1.x > ------------------------------------------------------- > > Key: JBIDE-17700 > URL: https://issues.jboss.org/browse/JBIDE-17700 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, maven, server > Environment: Win 7, Eclilpse Luna, JBoss Tools (via market place) > Reporter: Oliver Pfau > Priority: Critical > > When I publish my war to jboss 7.1 the following error occurs: > An internal error occurred during: "Publishing to JBoss AS 7.1...". > Could not initialize class de.schlichtherle.io.ArchiveControllers -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17733) Cleanup Central discovery catalog: remove pre-installed items

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17733?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-17733: ----------------------------------- Description: Here is a list of items that should probably be removed from Central catalog: *EGit*: Egit is already included in all Eclipse packages we target (JEE, Standard, PDE, if not all) and is included in JBDS product definition. It is also a dependency of OpenShift tooling so that anything that has OpenShift tools installed is guaranteed to have EGit installed. So we should remove EGit from our Central discovery catalogs. *jst.server* is already installed in JBDS, so there is no point in having it on JBDS Central was: Egit is already included in all Eclipse packages we target (JEE, Standard, PDE, if not all) and is included in JBDS product definition. It is also a dependency of OpenShift tooling so that anything that has OpenShift tools installed is guaranteed to have EGit installed. So we should remove EGit from our Central discovery catalogs. > Cleanup Central discovery catalog: remove pre-installed items > ------------------------------------------------------------- > > Key: JBIDE-17733 > URL: https://issues.jboss.org/browse/JBIDE-17733 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Mickael Istria > Fix For: 4.2.0.CR1 > > Attachments: eclipse-platform-installs-jbt-beta3-OK.png, eclipse-standard-installs-jbt-beta3-OK.png > > > Here is a list of items that should probably be removed from Central catalog: > *EGit*: Egit is already included in all Eclipse packages we target (JEE, Standard, PDE, if not all) and is included in JBDS product definition. It is also a dependency of OpenShift tooling so that anything that has OpenShift tools installed is guaranteed to have EGit installed. > So we should remove EGit from our Central discovery catalogs. > *jst.server* is already installed in JBDS, so there is no point in having it on JBDS Central -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17473) After forcestop, management shutdown does not clear forcestop flag

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17473?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17473. --------------------------------- Resolution: Done I'm marking this as done for b3. I'm not able to replicate it using recent master. > After forcestop, management shutdown does not clear forcestop flag > ------------------------------------------------------------------ > > Key: JBIDE-17473 > URL: https://issues.jboss.org/browse/JBIDE-17473 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Beta3 > > > After a failed stop attempt, a flag is set on the server that the next stop attempt should be a force / kill of the process. > The second stop attempt is a force kill. > If you then start the server, and try to shut it down, it is force-killed immediately. This should not happen. It should try a normal stop first. > Solution is to clear the force flag after a force stop. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17733) Cleanup Central discovery catalog: remove pre-installed items

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17733?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-17733: ----------------------------------- Summary: Cleanup Central discovery catalog: remove pre-installed items (was: Remove EGit from Central Discovery) > Cleanup Central discovery catalog: remove pre-installed items > ------------------------------------------------------------- > > Key: JBIDE-17733 > URL: https://issues.jboss.org/browse/JBIDE-17733 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Mickael Istria > Fix For: 4.2.0.CR1 > > Attachments: eclipse-platform-installs-jbt-beta3-OK.png, eclipse-standard-installs-jbt-beta3-OK.png > > > Egit is already included in all Eclipse packages we target (JEE, Standard, PDE, if not all) and is included in JBDS product definition. It is also a dependency of OpenShift tooling so that anything that has OpenShift tools installed is guaranteed to have EGit installed. > So we should remove EGit from our Central discovery catalogs. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17473) After forcestop, management shutdown does not clear forcestop flag

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17473?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17473: ------------------------------------- As soon as I change the password in your step 2 and save the editor, I get an error dialog that shows up that says that we cannot verify the server is up. This is actually kinda expected, as an incremental publish is being called once the server editor is saved, and since we're in management mode, we need to verify the server's management is up and ready. This isn't really relevant to the issue, but just thought I'd mention it. 1. Start a remote EAP 6.2 (management, no runtime) 2. Once server is started, change credentials in server editor to something wrong 2a) Error message as shown above (SEMI-expected?) 3. Stop server - fails (expected) 4. Stop server again - is killed (expected) 5. Fix credentials in server editor and save 6. Start server again 7. Stop server - WORKS AS EXPECTED I've traced through the code to verify I'm not missing anything, and it seems all flags are properly maintained and cleared when they're supposed to. So, I'm not able to replicate this. > After forcestop, management shutdown does not clear forcestop flag > ------------------------------------------------------------------ > > Key: JBIDE-17473 > URL: https://issues.jboss.org/browse/JBIDE-17473 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Beta3 > > > After a failed stop attempt, a flag is set on the server that the next stop attempt should be a force / kill of the process. > The second stop attempt is a force kill. > If you then start the server, and try to shut it down, it is force-killed immediately. This should not happen. It should try a normal stop first. > Solution is to clear the force flag after a force stop. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17733) Remove EGit from Central Discovery

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17733?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17733: ---------------------------------------- {quote}But does it hurt? We have other stuff in Central that is preinstalled in JBDS, like the jst.server connector.{quote} If this is installed by default, then it should probably be removed from Central as well. > Remove EGit from Central Discovery > ---------------------------------- > > Key: JBIDE-17733 > URL: https://issues.jboss.org/browse/JBIDE-17733 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Mickael Istria > Fix For: 4.2.0.CR1 > > Attachments: eclipse-platform-installs-jbt-beta3-OK.png, eclipse-standard-installs-jbt-beta3-OK.png > > > Egit is already included in all Eclipse packages we target (JEE, Standard, PDE, if not all) and is included in JBDS product definition. It is also a dependency of OpenShift tooling so that anything that has OpenShift tools installed is guaranteed to have EGit installed. > So we should remove EGit from our Central discovery catalogs. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17733) Remove EGit from Central Discovery

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17733?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-17733: ----------------------------------- Issue Type: Enhancement (was: Feature Request) > Remove EGit from Central Discovery > ---------------------------------- > > Key: JBIDE-17733 > URL: https://issues.jboss.org/browse/JBIDE-17733 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Mickael Istria > Fix For: 4.2.0.CR1 > > Attachments: eclipse-platform-installs-jbt-beta3-OK.png, eclipse-standard-installs-jbt-beta3-OK.png > > > Egit is already included in all Eclipse packages we target (JEE, Standard, PDE, if not all) and is included in JBDS product definition. It is also a dependency of OpenShift tooling so that anything that has OpenShift tools installed is guaranteed to have EGit installed. > So we should remove EGit from our Central discovery catalogs. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 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 July 2014