[jira] [Resolved] (KARAF-4742) Decanter: Add Java Process JMX Collector
[ https://issues.apache.org/jira/browse/KARAF-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck resolved KARAF-4742. --- Resolution: Fixed > Decanter: Add Java Process JMX Collector > > > Key: KARAF-4742 > URL: https://issues.apache.org/jira/browse/KARAF-4742 > Project: Karaf > Issue Type: New Feature > Components: decanter >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.3.0 > > > Right now there is a JMX collector available. Which is ok for open JMX > connections. Sometimes there are Java applications running which don't > explicitly have a JMX connection open, but are monitor able by JConsole. For > this a special JVM Process Collector is needed, which hooks itself into the > JVM Processes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4742) Decanter: Add Java Process JMX Collector
[ https://issues.apache.org/jira/browse/KARAF-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15541028#comment-15541028 ] ASF subversion and git services commented on KARAF-4742: Commit 1bd657db5e3d56a9ff0ff31c4e967bee30391caa in karaf-decanter's branch refs/heads/master from [~achim_nierbeck] [ https://git-wip-us.apache.org/repos/asf?p=karaf-decanter.git;h=1bd657d ] [KARAF-4742] - Decanter: Add Java Process JMX Collector make sure version is set to 0.0.0 > Decanter: Add Java Process JMX Collector > > > Key: KARAF-4742 > URL: https://issues.apache.org/jira/browse/KARAF-4742 > Project: Karaf > Issue Type: New Feature > Components: decanter >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.3.0 > > > Right now there is a JMX collector available. Which is ok for open JMX > connections. Sometimes there are Java applications running which don't > explicitly have a JMX connection open, but are monitor able by JConsole. For > this a special JVM Process Collector is needed, which hooks itself into the > JVM Processes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (KARAF-4742) Decanter: Add Java Process JMX Collector
[ https://issues.apache.org/jira/browse/KARAF-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck reopened KARAF-4742: --- versions shouldn't be 1.2.1 ... > Decanter: Add Java Process JMX Collector > > > Key: KARAF-4742 > URL: https://issues.apache.org/jira/browse/KARAF-4742 > Project: Karaf > Issue Type: New Feature > Components: decanter >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.3.0 > > > Right now there is a JMX collector available. Which is ok for open JMX > connections. Sometimes there are Java applications running which don't > explicitly have a JMX connection open, but are monitor able by JConsole. For > this a special JVM Process Collector is needed, which hooks itself into the > JVM Processes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4722) cluster:bundle-list shell command ignores the supplied ids argument
[ https://issues.apache.org/jira/browse/KARAF-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4722: Fix Version/s: cellar-4.0.3 > cluster:bundle-list shell command ignores the supplied ids argument > --- > > Key: KARAF-4722 > URL: https://issues.apache.org/jira/browse/KARAF-4722 > Project: Karaf > Issue Type: Bug > Components: cellar-bundle >Affects Versions: cellar-4.0.2 >Reporter: Sergiy Shyrkov >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: cellar-4.0.3 > > > The "ids" argument for the cluster:bundle-list is currently ignored, i.e. no > filtering happens in the displayed bundle list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4722) cluster:bundle-list shell command ignores the supplied ids argument
[ https://issues.apache.org/jira/browse/KARAF-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15540509#comment-15540509 ] ASF GitHub Bot commented on KARAF-4722: --- Github user asfgit closed the pull request at: https://github.com/apache/karaf-cellar/pull/39 > cluster:bundle-list shell command ignores the supplied ids argument > --- > > Key: KARAF-4722 > URL: https://issues.apache.org/jira/browse/KARAF-4722 > Project: Karaf > Issue Type: Bug > Components: cellar-bundle >Affects Versions: cellar-4.0.2 >Reporter: Sergiy Shyrkov >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: cellar-4.0.3 > > > The "ids" argument for the cluster:bundle-list is currently ignored, i.e. no > filtering happens in the displayed bundle list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4722) cluster:bundle-list shell command ignores the supplied ids argument
[ https://issues.apache.org/jira/browse/KARAF-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-4722. - Resolution: Fixed > cluster:bundle-list shell command ignores the supplied ids argument > --- > > Key: KARAF-4722 > URL: https://issues.apache.org/jira/browse/KARAF-4722 > Project: Karaf > Issue Type: Bug > Components: cellar-bundle >Affects Versions: cellar-4.0.2 >Reporter: Sergiy Shyrkov >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: cellar-4.0.3 > > > The "ids" argument for the cluster:bundle-list is currently ignored, i.e. no > filtering happens in the displayed bundle list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4722) cluster:bundle-list shell command ignores the supplied ids argument
[ https://issues.apache.org/jira/browse/KARAF-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15540508#comment-15540508 ] ASF subversion and git services commented on KARAF-4722: Commit 8eeb60202f46a506873b39711297b562ee89390d in karaf-cellar's branch refs/heads/master from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf-cellar.git;h=8eeb602 ] [KARAF-4722] This closes #39 > cluster:bundle-list shell command ignores the supplied ids argument > --- > > Key: KARAF-4722 > URL: https://issues.apache.org/jira/browse/KARAF-4722 > Project: Karaf > Issue Type: Bug > Components: cellar-bundle >Affects Versions: cellar-4.0.2 >Reporter: Sergiy Shyrkov >Assignee: Jean-Baptiste Onofré >Priority: Minor > > The "ids" argument for the cluster:bundle-list is currently ignored, i.e. no > filtering happens in the displayed bundle list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4722) cluster:bundle-list shell command ignores the supplied ids argument
[ https://issues.apache.org/jira/browse/KARAF-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15540507#comment-15540507 ] ASF subversion and git services commented on KARAF-4722: Commit 7d413fb76bc87d9096a7230c8fa0a8248ee6749e in karaf-cellar's branch refs/heads/master from [~shyrkov] [ https://git-wip-us.apache.org/repos/asf?p=karaf-cellar.git;h=7d413fb ] [KARAF-4722] do filtering of displayed bundles by the supplied ids > cluster:bundle-list shell command ignores the supplied ids argument > --- > > Key: KARAF-4722 > URL: https://issues.apache.org/jira/browse/KARAF-4722 > Project: Karaf > Issue Type: Bug > Components: cellar-bundle >Affects Versions: cellar-4.0.2 >Reporter: Sergiy Shyrkov >Assignee: Jean-Baptiste Onofré >Priority: Minor > > The "ids" argument for the cluster:bundle-list is currently ignored, i.e. no > filtering happens in the displayed bundle list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4721) Add support for clusterOnly and nodeOnly sync policies via shell command
[
https://issues.apache.org/jira/browse/KARAF-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-4721:
Fix Version/s: cellar-4.0.3
> Add support for clusterOnly and nodeOnly sync policies via shell command
>
>
> Key: KARAF-4721
> URL: https://issues.apache.org/jira/browse/KARAF-4721
> Project: Karaf
> Issue Type: Improvement
> Components: cellar-shell
>Affects Versions: cellar-4.0.2
>Reporter: Sergiy Shyrkov
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: cellar-4.0.3
>
>
> Right now the shell command (cluster:sync) does not support setting policy to
> clusterOnly or nodeOnly, i.e.:
> {code}
> jahia@dx(cluster)> sync -c clusterOnly
> The sync policy clusterOnly is not valid. Valid sync policies are: cluster,
> node, disabled
> {code}
> Would be nice to add those two policy types to the supported list for that
> command.
> Thank you!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4721) Add support for clusterOnly and nodeOnly sync policies via shell command
[
https://issues.apache.org/jira/browse/KARAF-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15540457#comment-15540457
]
ASF subversion and git services commented on KARAF-4721:
Commit 461cbd546822021f6eb55bcfc142367d9e72582d in karaf-cellar's branch
refs/heads/master from [~shyrkov]
[ https://git-wip-us.apache.org/repos/asf?p=karaf-cellar.git;h=461cbd5 ]
[KARAF-4721] Added support for clusterOnly and nodeOnly sync policies
via shell command
> Add support for clusterOnly and nodeOnly sync policies via shell command
>
>
> Key: KARAF-4721
> URL: https://issues.apache.org/jira/browse/KARAF-4721
> Project: Karaf
> Issue Type: Improvement
> Components: cellar-shell
>Affects Versions: cellar-4.0.2
>Reporter: Sergiy Shyrkov
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
>
> Right now the shell command (cluster:sync) does not support setting policy to
> clusterOnly or nodeOnly, i.e.:
> {code}
> jahia@dx(cluster)> sync -c clusterOnly
> The sync policy clusterOnly is not valid. Valid sync policies are: cluster,
> node, disabled
> {code}
> Would be nice to add those two policy types to the supported list for that
> command.
> Thank you!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4721) Add support for clusterOnly and nodeOnly sync policies via shell command
[
https://issues.apache.org/jira/browse/KARAF-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15540458#comment-15540458
]
ASF subversion and git services commented on KARAF-4721:
Commit 2373eb68b926b75eb0fae9902986b29a0f042698 in karaf-cellar's branch
refs/heads/master from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf-cellar.git;h=2373eb6 ]
[KARAF-4721] This closes #38
> Add support for clusterOnly and nodeOnly sync policies via shell command
>
>
> Key: KARAF-4721
> URL: https://issues.apache.org/jira/browse/KARAF-4721
> Project: Karaf
> Issue Type: Improvement
> Components: cellar-shell
>Affects Versions: cellar-4.0.2
>Reporter: Sergiy Shyrkov
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
>
> Right now the shell command (cluster:sync) does not support setting policy to
> clusterOnly or nodeOnly, i.e.:
> {code}
> jahia@dx(cluster)> sync -c clusterOnly
> The sync policy clusterOnly is not valid. Valid sync policies are: cluster,
> node, disabled
> {code}
> Would be nice to add those two policy types to the supported list for that
> command.
> Thank you!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-4737) Bundle start attribute in features XML is ignored
[
https://issues.apache.org/jira/browse/KARAF-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-4737.
-
Resolution: Fixed
> Bundle start attribute in features XML is ignored
> -
>
> Key: KARAF-4737
> URL: https://issues.apache.org/jira/browse/KARAF-4737
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 4.0.7
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.8
>
>
> If we have the following features XML:
> {code}
>
> http://karaf.apache.org/xmlns/features/v1.4.0; name="tests">
>
> ...
>
>
>
> {code}
> the bundle {{start}} attribute is ignored and the bundle is always started
> (even if {{start}} is set to {{false}}).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4737) Bundle start attribute in features XML is ignored
[
https://issues.apache.org/jira/browse/KARAF-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15540137#comment-15540137
]
ASF subversion and git services commented on KARAF-4737:
Commit 88ab5e87e75131711d3db742b4d012c7a3d7c689 in karaf's branch
refs/heads/master from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=88ab5e8 ]
[KARAF-4737] Check value of bundle start attribute to define if the bundle is
start or resolved when installing a feature
> Bundle start attribute in features XML is ignored
> -
>
> Key: KARAF-4737
> URL: https://issues.apache.org/jira/browse/KARAF-4737
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 4.0.7
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.8
>
>
> If we have the following features XML:
> {code}
>
> http://karaf.apache.org/xmlns/features/v1.4.0; name="tests">
>
> ...
>
>
>
> {code}
> the bundle {{start}} attribute is ignored and the bundle is always started
> (even if {{start}} is set to {{false}}).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4737) Bundle start attribute in features XML is ignored
[
https://issues.apache.org/jira/browse/KARAF-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-4737:
Fix Version/s: 4.0.8
4.1.0
> Bundle start attribute in features XML is ignored
> -
>
> Key: KARAF-4737
> URL: https://issues.apache.org/jira/browse/KARAF-4737
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 4.0.7
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.8
>
>
> If we have the following features XML:
> {code}
>
> http://karaf.apache.org/xmlns/features/v1.4.0; name="tests">
>
> ...
>
>
>
> {code}
> the bundle {{start}} attribute is ignored and the bundle is always started
> (even if {{start}} is set to {{false}}).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4737) Bundle start attribute in features XML is ignored
[
https://issues.apache.org/jira/browse/KARAF-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15540135#comment-15540135
]
ASF subversion and git services commented on KARAF-4737:
Commit b82d0b74ca297d4734f0bc696e844f99a3de195c in karaf's branch
refs/heads/karaf-4.0.x from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=b82d0b7 ]
[KARAF-4737] Check value of bundle start attribute to define if the bundle is
start or resolved when installing a feature
> Bundle start attribute in features XML is ignored
> -
>
> Key: KARAF-4737
> URL: https://issues.apache.org/jira/browse/KARAF-4737
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 4.0.7
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.8
>
>
> If we have the following features XML:
> {code}
>
> http://karaf.apache.org/xmlns/features/v1.4.0; name="tests">
>
> ...
>
>
>
> {code}
> the bundle {{start}} attribute is ignored and the bundle is always started
> (even if {{start}} is set to {{false}}).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4680) Karaf shell console (jline 3) leaves the terminal in "bad" state
[
https://issues.apache.org/jira/browse/KARAF-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15540096#comment-15540096
]
Jean-Baptiste Onofré commented on KARAF-4680:
-
It happens with screen and gnome terminal with {{TERM}} set to {{screen}} or
{{xterm-256color}} or {{xterm}}.
[~gnt] can we take a look together on that ?
> Karaf shell console (jline 3) leaves the terminal in "bad" state
>
>
> Key: KARAF-4680
> URL: https://issues.apache.org/jira/browse/KARAF-4680
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0
>
>
> Karaf 4.1.x is now using JLine 3. The Karaf shell works pretty well.
> However, when stopping Karaf 4.1.x (using CTRL-D), the Linux terminal is left
> in a bad state (input and output stream are "lost").
> We have to do a {{reset}} to have a terminal back to "normal".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-4742) Decanter: Add Java Process JMX Collector
[ https://issues.apache.org/jira/browse/KARAF-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck resolved KARAF-4742. --- Resolution: Fixed fixed by: http://git-wip-us.apache.org/repos/asf/karaf-decanter/commit/f1fa5cb6 > Decanter: Add Java Process JMX Collector > > > Key: KARAF-4742 > URL: https://issues.apache.org/jira/browse/KARAF-4742 > Project: Karaf > Issue Type: New Feature > Components: decanter >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.3.0 > > > Right now there is a JMX collector available. Which is ok for open JMX > connections. Sometimes there are Java applications running which don't > explicitly have a JMX connection open, but are monitor able by JConsole. For > this a special JVM Process Collector is needed, which hooks itself into the > JVM Processes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4742) Decanter: Add Java Process JMX Collector
[ https://issues.apache.org/jira/browse/KARAF-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15540082#comment-15540082 ] ASF subversion and git services commented on KARAF-4742: Commit f1fa5cb673a9ea97f24a0e9be18d5807ef9d5355 in karaf-decanter's branch refs/heads/master from [~achim_nierbeck] [ https://git-wip-us.apache.org/repos/asf?p=karaf-decanter.git;h=f1fa5cb ] [KARAF-4742] - Decanter: Add Java Process JMX Collector > Decanter: Add Java Process JMX Collector > > > Key: KARAF-4742 > URL: https://issues.apache.org/jira/browse/KARAF-4742 > Project: Karaf > Issue Type: New Feature > Components: decanter >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.3.0 > > > Right now there is a JMX collector available. Which is ok for open JMX > connections. Sometimes there are Java applications running which don't > explicitly have a JMX connection open, but are monitor able by JConsole. For > this a special JVM Process Collector is needed, which hooks itself into the > JVM Processes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4742) Decanter: Add Java Process JMX Collector
Achim Nierbeck created KARAF-4742: - Summary: Decanter: Add Java Process JMX Collector Key: KARAF-4742 URL: https://issues.apache.org/jira/browse/KARAF-4742 Project: Karaf Issue Type: New Feature Components: decanter Reporter: Achim Nierbeck Assignee: Achim Nierbeck Fix For: decanter-1.3.0 Right now there is a JMX collector available. Which is ok for open JMX connections. Sometimes there are Java applications running which don't explicitly have a JMX connection open, but are monitor able by JConsole. For this a special JVM Process Collector is needed, which hooks itself into the JVM Processes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
