[jira] [Resolved] (KARAF-5668) Upgrade to JLine 3.6.2
[ https://issues.apache.org/jira/browse/KARAF-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-5668. - Resolution: Fixed > Upgrade to JLine 3.6.2 > -- > > Key: KARAF-5668 > URL: https://issues.apache.org/jira/browse/KARAF-5668 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0, 4.1.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5657) client.bat doesn't work on Windows
[
https://issues.apache.org/jira/browse/KARAF-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-5657:
Fix Version/s: 4.2.0
> client.bat doesn't work on Windows
> --
>
> Key: KARAF-5657
> URL: https://issues.apache.org/jira/browse/KARAF-5657
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.5
> Environment: Windows 7
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.2.0, 4.1.6
>
>
> When using {{client.bat}} on Windows 7, the login is OK but we can't type
> anything in the shell, it fails with:
> {code}
> 2018-03-05T13:35:39,496 | ERROR | Karaf ssh console user karaf | ShellUtil
> | 43 - org.apache.karaf.shell.core - 4.1.5 | Exception
> caught while executing command
> java.lang.NullPointerException: null
> at
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:348)
> [43:org.apache.karaf.shell.core:4.1.5]
> at java.lang.Thread.run(Thread.java:748) [?:?]
> 2018-03-05T13:35:40,011 | WARN | sshd-SshServer[50ae478a]-nio2-thread-3 |
> ServerSessionImpl| 48 - org.apache.sshd.core - 1.6.0 |
> exceptionCaught(ServerSessionImpl[karaf@/127.0.0.1:65321])[state=Opened]
> IOException: The specified network name is no longer available.
> {code}
> NB: putty works fine, and {{client.bat}} 4.1.4 works fine.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5668) Upgrade to JLine 3.6.2
[ https://issues.apache.org/jira/browse/KARAF-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401135#comment-16401135 ] ASF subversion and git services commented on KARAF-5668: Commit 06a5520d698472093e9106fd42e276198f846a4b in karaf's branch refs/heads/karaf-4.1.x from [~j...@nanthrax.net] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=06a5520 ] [KARAF-5668] Upgrade to jline 3.6.2 > Upgrade to JLine 3.6.2 > -- > > Key: KARAF-5668 > URL: https://issues.apache.org/jira/browse/KARAF-5668 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0, 4.1.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5668) Upgrade to JLine 3.6.2
[ https://issues.apache.org/jira/browse/KARAF-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401133#comment-16401133 ] ASF subversion and git services commented on KARAF-5668: Commit 4e1eeeb38eecbc4808bc2283a001b2aac78659ad in karaf's branch refs/heads/master from [~jbonofre] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=4e1eeeb ] Merge pull request #472 from jbonofre/KARAF-5668 [KARAF-5668] Upgrade to jline 3.6.2 > Upgrade to JLine 3.6.2 > -- > > Key: KARAF-5668 > URL: https://issues.apache.org/jira/browse/KARAF-5668 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0, 4.1.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5668) Upgrade to JLine 3.6.2
[ https://issues.apache.org/jira/browse/KARAF-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401132#comment-16401132 ] ASF subversion and git services commented on KARAF-5668: Commit c333ec732c9c5a29549773f5924099fdcbd7aad9 in karaf's branch refs/heads/master from [~j...@nanthrax.net] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=c333ec7 ] [KARAF-5668] Upgrade to jline 3.6.2 > Upgrade to JLine 3.6.2 > -- > > Key: KARAF-5668 > URL: https://issues.apache.org/jira/browse/KARAF-5668 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0, 4.1.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5668) Upgrade to JLine 3.6.2
[ https://issues.apache.org/jira/browse/KARAF-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401131#comment-16401131 ] ASF GitHub Bot commented on KARAF-5668: --- jbonofre closed pull request #472: [KARAF-5668] Upgrade to jline 3.6.2 URL: https://github.com/apache/karaf/pull/472 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/pom.xml b/pom.xml index 4430b7daa5..09575449af 100644 --- a/pom.xml +++ b/pom.xml @@ -259,7 +259,7 @@ 1.17 3.9.0.GA 9.3.21.v20170918 -3.6.1 +3.6.2 3.2.3 1.2.17 3.5.2 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to JLine 3.6.2 > -- > > Key: KARAF-5668 > URL: https://issues.apache.org/jira/browse/KARAF-5668 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0, 4.1.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5668) Upgrade to JLine 3.6.2
[ https://issues.apache.org/jira/browse/KARAF-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401134#comment-16401134 ] ASF subversion and git services commented on KARAF-5668: Commit 4e1eeeb38eecbc4808bc2283a001b2aac78659ad in karaf's branch refs/heads/master from [~jbonofre] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=4e1eeeb ] Merge pull request #472 from jbonofre/KARAF-5668 [KARAF-5668] Upgrade to jline 3.6.2 > Upgrade to JLine 3.6.2 > -- > > Key: KARAF-5668 > URL: https://issues.apache.org/jira/browse/KARAF-5668 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0, 4.1.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5628) Corrupt gc.log due to unseparated VM settings
[ https://issues.apache.org/jira/browse/KARAF-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400934#comment-16400934 ] Jean-Baptiste Onofré commented on KARAF-5628: - Understood. Let me prepare a PR to move JAVA_OPTS in a condition (based on the script). > Corrupt gc.log due to unseparated VM settings > - > > Key: KARAF-5628 > URL: https://issues.apache.org/jira/browse/KARAF-5628 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Reporter: Rico Neubauer >Assignee: Jean-Baptiste Onofré >Priority: Major > > The VM properties used for the start, stop, status and client scripts all use > one common configuration of the VM properties, like Xmx and GC settings. > This has one particular issue when activating the gc.log (-Xloggc:gc.log with > Oracle-VM): Invoking e.g. status while Karaf is running, uses the same > settings, thus points to the same file and corrupts it with NUL values (see > here for details: > [Stackoverflow|[https://stackoverflow.com/questions/8353401/garbage-collector-log-loggc-file-rotation-with-logrotate-does-not-work-properl]] > ). > > I would like to request the possibility to configure the VM properties for > starting the instance independently from the maintenance scripts - due to the > issue and also since e.g. running status with lots of heap (if instance is > configured to it) is unneeded. > > Even making it broader, I think it would also make sense to be able to > configure the settings completely, since currently some things are hard-coded > in the scripts, like the _-Xdum_p and _-Xlp_ settings for AIX, where I > personally would like to configure it to _-Xdump:heap:events=gpf,opts=PHD_, > which is currently not possible using the configuration only. Also especially > for AIX, there is _LDR_CNTRL=MAXDATA=0xB000@DSA_, which might not be > desired when running with heaps larger than 3GB. > > If you agree on a separation, I would make a proposal as PR. Please let me > know. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5628) Corrupt gc.log due to unseparated VM settings
[
https://issues.apache.org/jira/browse/KARAF-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400926#comment-16400926
]
Rico Neubauer commented on KARAF-5628:
--
[~jbonofre] unfortunately not. Those are only *extra* JAVA_OPTS, that get
concatenated to some hard-coded values in the scripts, depending on VM-version
and -vendor.
see e.g. this part of the "inc" script:
{code:java}
if [ "x${EXTRA_JAVA_OPTS}" != "x" ]; then
JAVA_OPTS="${JAVA_OPTS} ${EXTRA_JAVA_OPTS}"
fi
{code}
and the part below "_#Set the JVM_VENDOR specific JVM flags_"
I can suggest a PR as said, just did not start since you mentioned you would do
the improvements.
> Corrupt gc.log due to unseparated VM settings
> -
>
> Key: KARAF-5628
> URL: https://issues.apache.org/jira/browse/KARAF-5628
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
>Reporter: Rico Neubauer
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>
> The VM properties used for the start, stop, status and client scripts all use
> one common configuration of the VM properties, like Xmx and GC settings.
> This has one particular issue when activating the gc.log (-Xloggc:gc.log with
> Oracle-VM): Invoking e.g. status while Karaf is running, uses the same
> settings, thus points to the same file and corrupts it with NUL values (see
> here for details:
> [Stackoverflow|[https://stackoverflow.com/questions/8353401/garbage-collector-log-loggc-file-rotation-with-logrotate-does-not-work-properl]]
> ).
>
> I would like to request the possibility to configure the VM properties for
> starting the instance independently from the maintenance scripts - due to the
> issue and also since e.g. running status with lots of heap (if instance is
> configured to it) is unneeded.
>
> Even making it broader, I think it would also make sense to be able to
> configure the settings completely, since currently some things are hard-coded
> in the scripts, like the _-Xdum_p and _-Xlp_ settings for AIX, where I
> personally would like to configure it to _-Xdump:heap:events=gpf,opts=PHD_,
> which is currently not possible using the configuration only. Also especially
> for AIX, there is _LDR_CNTRL=MAXDATA=0xB000@DSA_, which might not be
> desired when running with heaps larger than 3GB.
>
> If you agree on a separation, I would make a proposal as PR. Please let me
> know.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KARAF-5667) Installing the audit-log feature never ends
[ https://issues.apache.org/jira/browse/KARAF-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-5667. Resolution: Fixed For the record, the problem is caused by the features service failing to install a config because the config admin bundle has been stopped, so it fails with an error and just leaves all bundles in the stopped state. > Installing the audit-log feature never ends > --- > > Key: KARAF-5667 > URL: https://issues.apache.org/jira/browse/KARAF-5667 > Project: Karaf > Issue Type: Bug >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Critical > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5667) Installing the audit-log feature never ends
[ https://issues.apache.org/jira/browse/KARAF-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400770#comment-16400770 ] ASF subversion and git services commented on KARAF-5667: Commit a0e44246e33c616bf580fe62df040cf5c1bedfff in karaf's branch refs/heads/master from [~gnt] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=a0e4424 ] Merge pull request #470 from gnodet/KARAF-5667 [KARAF-5667] Installing the audit-log feature never ends > Installing the audit-log feature never ends > --- > > Key: KARAF-5667 > URL: https://issues.apache.org/jira/browse/KARAF-5667 > Project: Karaf > Issue Type: Bug >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Critical > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5667) Installing the audit-log feature never ends
[ https://issues.apache.org/jira/browse/KARAF-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400769#comment-16400769 ] ASF subversion and git services commented on KARAF-5667: Commit 3b52c038ff8bfb82220868053192a8d26034fe32 in karaf's branch refs/heads/master from [~gnt] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=3b52c03 ] [KARAF-5667] Installing the audit-log feature never ends > Installing the audit-log feature never ends > --- > > Key: KARAF-5667 > URL: https://issues.apache.org/jira/browse/KARAF-5667 > Project: Karaf > Issue Type: Bug >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Critical > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5667) Installing the audit-log feature never ends
[ https://issues.apache.org/jira/browse/KARAF-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400771#comment-16400771 ] ASF subversion and git services commented on KARAF-5667: Commit a0e44246e33c616bf580fe62df040cf5c1bedfff in karaf's branch refs/heads/master from [~gnt] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=a0e4424 ] Merge pull request #470 from gnodet/KARAF-5667 [KARAF-5667] Installing the audit-log feature never ends > Installing the audit-log feature never ends > --- > > Key: KARAF-5667 > URL: https://issues.apache.org/jira/browse/KARAF-5667 > Project: Karaf > Issue Type: Bug >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Critical > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5667) Installing the audit-log feature never ends
[
https://issues.apache.org/jira/browse/KARAF-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400768#comment-16400768
]
ASF GitHub Bot commented on KARAF-5667:
---
gnodet closed pull request #470: [KARAF-5667] Installing the audit-log feature
never ends
URL: https://github.com/apache/karaf/pull/470
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/features/core/src/main/java/org/apache/karaf/features/internal/osgi/Activator.java
b/features/core/src/main/java/org/apache/karaf/features/internal/osgi/Activator.java
index 5ef8870f57..8ac3e3bcb6 100644
---
a/features/core/src/main/java/org/apache/karaf/features/internal/osgi/Activator.java
+++
b/features/core/src/main/java/org/apache/karaf/features/internal/osgi/Activator.java
@@ -152,6 +152,7 @@ protected void doStart() throws Exception {
bundleContext.getBundle(),
bundleContext,
systemBundleContext,
+getTrackedServiceRef(ConfigurationAdmin.class).getBundle(),
configInstaller,
dg);
register(RegionDigraphPersistence.class, () ->
installSupport.saveDigraph());
@@ -326,6 +327,7 @@ protected void doStop() {
if (installSupport != null) {
installSupport.unregister();
installSupport.saveDigraph();
+installSupport = null;
}
}
diff --git
a/features/core/src/main/java/org/apache/karaf/features/internal/service/BundleInstallSupport.java
b/features/core/src/main/java/org/apache/karaf/features/internal/service/BundleInstallSupport.java
index fb31a7a462..9dc06a4852 100644
---
a/features/core/src/main/java/org/apache/karaf/features/internal/service/BundleInstallSupport.java
+++
b/features/core/src/main/java/org/apache/karaf/features/internal/service/BundleInstallSupport.java
@@ -85,6 +85,7 @@ void replaceDigraph(Map>> policies,
class FrameworkInfo {
public Bundle ourBundle;
public Bundle systemBundle;
+public Bundle cmBundle;
public int initialBundleStartLevel;
public int currentStartLevel;
public Map bundles = new HashMap<>();
diff --git
a/features/core/src/main/java/org/apache/karaf/features/internal/service/BundleInstallSupportImpl.java
b/features/core/src/main/java/org/apache/karaf/features/internal/service/BundleInstallSupportImpl.java
index 24c2fbfcad..5b0c7e67df 100644
---
a/features/core/src/main/java/org/apache/karaf/features/internal/service/BundleInstallSupportImpl.java
+++
b/features/core/src/main/java/org/apache/karaf/features/internal/service/BundleInstallSupportImpl.java
@@ -68,6 +68,7 @@
private final RegionDigraph digraph;
private final Bundle ourBundle;
+private final Bundle cmBundle;
private final BundleContext ourBundleContext;
private final FeatureConfigInstaller configInstaller;
@@ -85,11 +86,13 @@
public BundleInstallSupportImpl(Bundle ourBundle,
BundleContext ourBundleContext,
BundleContext systemBundleContext,
+ Bundle cmBundle,
FeatureConfigInstaller configInstaller,
RegionDigraph digraph) {
this.ourBundle = ourBundle;
this.ourBundleContext = ourBundleContext;
this.systemBundleContext = systemBundleContext;
+this.cmBundle = cmBundle;
this.configInstaller = configInstaller;
this.digraph = digraph;
if (systemBundleContext != null) {
@@ -102,6 +105,7 @@ public BundleInstallSupportImpl(Bundle ourBundle,
public void unregister() {
if (hookRegistration != null) {
hookRegistration.unregister();
+hookRegistration = null;
}
}
@@ -315,6 +319,7 @@ public FrameworkInfo getInfo() {
for (Bundle bundle : systemBundleContext.getBundles()) {
info.bundles.put(bundle.getBundleId(), bundle);
}
+info.cmBundle = cmBundle;
info.systemBundle = info.bundles.get(0L);
return info;
}
diff --git
a/features/core/src/main/java/org/apache/karaf/features/internal/service/Deployer.java
b/features/core/src/main/java/org/apache/karaf/features/internal/service/Deployer.java
index dab5f60bda..14086e734c 100644
---
a/features/core/src/main/java/org/apache/karaf/features/internal/service/Deployer.java
+++
b/features/core/src/main/java/org/apache/karaf/features/internal/service/Deployer.java
@@ -79,6 +79,7 @@
import org.osgi.resource.Wire;
import org.osgi.service.repository.Repository;
import org.osgi.service.resolver.Resolver;
+import
[jira] [Commented] (KARAF-5668) Upgrade to JLine 3.6.2
[ https://issues.apache.org/jira/browse/KARAF-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400651#comment-16400651 ] ASF GitHub Bot commented on KARAF-5668: --- jbonofre opened a new pull request #472: [KARAF-5668] Upgrade to jline 3.6.2 URL: https://github.com/apache/karaf/pull/472 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to JLine 3.6.2 > -- > > Key: KARAF-5668 > URL: https://issues.apache.org/jira/browse/KARAF-5668 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0, 4.1.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5668) Upgrade to JLine 3.6.2
Jean-Baptiste Onofré created KARAF-5668: --- Summary: Upgrade to JLine 3.6.2 Key: KARAF-5668 URL: https://issues.apache.org/jira/browse/KARAF-5668 Project: Karaf Issue Type: Dependency upgrade Components: karaf-shell Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.2.0, 4.1.6 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-5658) Upgrade to Spring 5.0.4.RELEASE
[ https://issues.apache.org/jira/browse/KARAF-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-5658. - Resolution: Fixed > Upgrade to Spring 5.0.4.RELEASE > --- > > Key: KARAF-5658 > URL: https://issues.apache.org/jira/browse/KARAF-5658 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5658) Upgrade to Spring 5.0.4.RELEASE
[ https://issues.apache.org/jira/browse/KARAF-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400637#comment-16400637 ] ASF subversion and git services commented on KARAF-5658: Commit ae677427560b624930e7f2faad265a5ee62333fe in karaf's branch refs/heads/master from [~gnt] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=ae67742 ] Merge pull request #471 from gnodet/KARAF-5658 [KARAF-5658] Upgrade to Spring 5.0.4.RELEASE > Upgrade to Spring 5.0.4.RELEASE > --- > > Key: KARAF-5658 > URL: https://issues.apache.org/jira/browse/KARAF-5658 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5658) Upgrade to Spring 5.0.4.RELEASE
[ https://issues.apache.org/jira/browse/KARAF-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400636#comment-16400636 ] ASF subversion and git services commented on KARAF-5658: Commit 9c93bba437b751972ce85dc4fe042c870170bd87 in karaf's branch refs/heads/master from [~gnt] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=9c93bba ] [KARAF-5658] Upgrade to Spring 5.0.4.RELEASE > Upgrade to Spring 5.0.4.RELEASE > --- > > Key: KARAF-5658 > URL: https://issues.apache.org/jira/browse/KARAF-5658 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5658) Upgrade to Spring 5.0.4.RELEASE
[ https://issues.apache.org/jira/browse/KARAF-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400635#comment-16400635 ] ASF GitHub Bot commented on KARAF-5658: --- gnodet closed pull request #471: [KARAF-5658] Upgrade to Spring 5.0.4.RELEASE URL: https://github.com/apache/karaf/pull/471 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/pom.xml b/pom.xml index 4430b7daa5..86cd622296 100644 --- a/pom.xml +++ b/pom.xml @@ -293,7 +293,7 @@ 4.1.9.RELEASE_1 4.2.9.RELEASE_1 4.3.14.RELEASE_1 -5.0.3.RELEASE_1 +5.0.4.RELEASE_1 3.1.4.RELEASE 4.2.4.RELEASE_1 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to Spring 5.0.4.RELEASE > --- > > Key: KARAF-5658 > URL: https://issues.apache.org/jira/browse/KARAF-5658 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5658) Upgrade to Spring 5.0.4.RELEASE
[ https://issues.apache.org/jira/browse/KARAF-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400638#comment-16400638 ] ASF subversion and git services commented on KARAF-5658: Commit ae677427560b624930e7f2faad265a5ee62333fe in karaf's branch refs/heads/master from [~gnt] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=ae67742 ] Merge pull request #471 from gnodet/KARAF-5658 [KARAF-5658] Upgrade to Spring 5.0.4.RELEASE > Upgrade to Spring 5.0.4.RELEASE > --- > > Key: KARAF-5658 > URL: https://issues.apache.org/jira/browse/KARAF-5658 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5628) Corrupt gc.log due to unseparated VM settings
[
https://issues.apache.org/jira/browse/KARAF-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400617#comment-16400617
]
Jean-Baptiste Onofré commented on KARAF-5628:
-
I think you can already do what you want. In {{bin/setenv}}, you can configure
settings for a particular script:
{code}
if [ "${KARAF_SCRIPT}" == "karaf" ]; then
EXTRA_JAVA_OPTS="..."
fi
{code}
Is it not what you are looking for ?
> Corrupt gc.log due to unseparated VM settings
> -
>
> Key: KARAF-5628
> URL: https://issues.apache.org/jira/browse/KARAF-5628
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
>Reporter: Rico Neubauer
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>
> The VM properties used for the start, stop, status and client scripts all use
> one common configuration of the VM properties, like Xmx and GC settings.
> This has one particular issue when activating the gc.log (-Xloggc:gc.log with
> Oracle-VM): Invoking e.g. status while Karaf is running, uses the same
> settings, thus points to the same file and corrupts it with NUL values (see
> here for details:
> [Stackoverflow|[https://stackoverflow.com/questions/8353401/garbage-collector-log-loggc-file-rotation-with-logrotate-does-not-work-properl]]
> ).
>
> I would like to request the possibility to configure the VM properties for
> starting the instance independently from the maintenance scripts - due to the
> issue and also since e.g. running status with lots of heap (if instance is
> configured to it) is unneeded.
>
> Even making it broader, I think it would also make sense to be able to
> configure the settings completely, since currently some things are hard-coded
> in the scripts, like the _-Xdum_p and _-Xlp_ settings for AIX, where I
> personally would like to configure it to _-Xdump:heap:events=gpf,opts=PHD_,
> which is currently not possible using the configuration only. Also especially
> for AIX, there is _LDR_CNTRL=MAXDATA=0xB000@DSA_, which might not be
> desired when running with heaps larger than 3GB.
>
> If you agree on a separation, I would make a proposal as PR. Please let me
> know.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5628) Corrupt gc.log due to unseparated VM settings
[ https://issues.apache.org/jira/browse/KARAF-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400500#comment-16400500 ] Guillaume Nodet commented on KARAF-5628: [~riconeubauer] feel free to work on a PR, that would definitely help speed things up ! > Corrupt gc.log due to unseparated VM settings > - > > Key: KARAF-5628 > URL: https://issues.apache.org/jira/browse/KARAF-5628 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Reporter: Rico Neubauer >Assignee: Jean-Baptiste Onofré >Priority: Major > > The VM properties used for the start, stop, status and client scripts all use > one common configuration of the VM properties, like Xmx and GC settings. > This has one particular issue when activating the gc.log (-Xloggc:gc.log with > Oracle-VM): Invoking e.g. status while Karaf is running, uses the same > settings, thus points to the same file and corrupts it with NUL values (see > here for details: > [Stackoverflow|[https://stackoverflow.com/questions/8353401/garbage-collector-log-loggc-file-rotation-with-logrotate-does-not-work-properl]] > ). > > I would like to request the possibility to configure the VM properties for > starting the instance independently from the maintenance scripts - due to the > issue and also since e.g. running status with lots of heap (if instance is > configured to it) is unneeded. > > Even making it broader, I think it would also make sense to be able to > configure the settings completely, since currently some things are hard-coded > in the scripts, like the _-Xdum_p and _-Xlp_ settings for AIX, where I > personally would like to configure it to _-Xdump:heap:events=gpf,opts=PHD_, > which is currently not possible using the configuration only. Also especially > for AIX, there is _LDR_CNTRL=MAXDATA=0xB000@DSA_, which might not be > desired when running with heaps larger than 3GB. > > If you agree on a separation, I would make a proposal as PR. Please let me > know. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5657) client.bat doesn't work on Windows
[
https://issues.apache.org/jira/browse/KARAF-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400496#comment-16400496
]
Guillaume Nodet commented on KARAF-5657:
JLine 3.6.2 has just been released, we need to upgrade to it.
> client.bat doesn't work on Windows
> --
>
> Key: KARAF-5657
> URL: https://issues.apache.org/jira/browse/KARAF-5657
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.5
> Environment: Windows 7
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.1.6
>
>
> When using {{client.bat}} on Windows 7, the login is OK but we can't type
> anything in the shell, it fails with:
> {code}
> 2018-03-05T13:35:39,496 | ERROR | Karaf ssh console user karaf | ShellUtil
> | 43 - org.apache.karaf.shell.core - 4.1.5 | Exception
> caught while executing command
> java.lang.NullPointerException: null
> at
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:348)
> [43:org.apache.karaf.shell.core:4.1.5]
> at java.lang.Thread.run(Thread.java:748) [?:?]
> 2018-03-05T13:35:40,011 | WARN | sshd-SshServer[50ae478a]-nio2-thread-3 |
> ServerSessionImpl| 48 - org.apache.sshd.core - 1.6.0 |
> exceptionCaught(ServerSessionImpl[karaf@/127.0.0.1:65321])[state=Opened]
> IOException: The specified network name is no longer available.
> {code}
> NB: putty works fine, and {{client.bat}} 4.1.4 works fine.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5641) Karaf boot scripts need to deal with JDK10 version patterns
[
https://issues.apache.org/jira/browse/KARAF-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400495#comment-16400495
]
Guillaume Nodet commented on KARAF-5641:
We should also verify on windows I think.
> Karaf boot scripts need to deal with JDK10 version patterns
> ---
>
> Key: KARAF-5641
> URL: https://issues.apache.org/jira/browse/KARAF-5641
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
>Affects Versions: 4.2.0.M2
>Reporter: Sanne Grinovero
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.2.0
>
>
> The {{checkJvmVersion()}} function in the {{/bin/inc}} script of the
> distribution is not dealing with the new output of {{java -version}} of JDK10
> (and later?).
> The {{VERSION}} variable is left undefined, which then has the main
> bootscript to not set the Jigsaw modules correctly (the various JVM flags
> which need to be enabled since Java 9).
> This is a blocker to use Karaf on Java 10, which is already in candidate
> release. I don't think much else is changed compared to Java 9 so it would be
> great to sort this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5658) Upgrade to Spring 5.0.4.RELEASE
[ https://issues.apache.org/jira/browse/KARAF-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400305#comment-16400305 ] ASF GitHub Bot commented on KARAF-5658: --- gnodet opened a new pull request #471: [KARAF-5658] Upgrade to Spring 5.0.4.RELEASE URL: https://github.com/apache/karaf/pull/471 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to Spring 5.0.4.RELEASE > --- > > Key: KARAF-5658 > URL: https://issues.apache.org/jira/browse/KARAF-5658 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-5646) Support env:XXX subtitution missing for system.properties
[ https://issues.apache.org/jira/browse/KARAF-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-5646. Resolution: Fixed Fix Version/s: 4.1.6 4.2.0 > Support env:XXX subtitution missing for system.properties > - > > Key: KARAF-5646 > URL: https://issues.apache.org/jira/browse/KARAF-5646 > Project: Karaf > Issue Type: Bug > Components: karaf-util >Affects Versions: 4.2.0, 4.1.5 >Reporter: Łukasz Dywicki >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.2.0, 4.1.6 > > > Variable substitution implemented as part of KARAF-3434 works fine with files > processed via fileinstall, however it does not work with properties files > used by karaf for setting up entire environment such system.properties and > config.properties. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-5646) Support env:XXX subtitution missing for system.properties
[ https://issues.apache.org/jira/browse/KARAF-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned KARAF-5646: -- Assignee: Guillaume Nodet (was: Jean-Baptiste Onofré) > Support env:XXX subtitution missing for system.properties > - > > Key: KARAF-5646 > URL: https://issues.apache.org/jira/browse/KARAF-5646 > Project: Karaf > Issue Type: Bug > Components: karaf-util >Affects Versions: 4.2.0, 4.1.5 >Reporter: Łukasz Dywicki >Assignee: Guillaume Nodet >Priority: Major > > Variable substitution implemented as part of KARAF-3434 works fine with files > processed via fileinstall, however it does not work with properties files > used by karaf for setting up entire environment such system.properties and > config.properties. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5646) Support env:XXX subtitution missing for system.properties
[ https://issues.apache.org/jira/browse/KARAF-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400286#comment-16400286 ] ASF subversion and git services commented on KARAF-5646: Commit d4fe806bf3c33163c4e8e17cbd8b2c2aa81cd47a in karaf's branch refs/heads/master from [~gnt] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=d4fe806 ] [KARAF-5646] Support env:XXX substitution for system.properties > Support env:XXX subtitution missing for system.properties > - > > Key: KARAF-5646 > URL: https://issues.apache.org/jira/browse/KARAF-5646 > Project: Karaf > Issue Type: Bug > Components: karaf-util >Affects Versions: 4.2.0, 4.1.5 >Reporter: Łukasz Dywicki >Assignee: Jean-Baptiste Onofré >Priority: Major > > Variable substitution implemented as part of KARAF-3434 works fine with files > processed via fileinstall, however it does not work with properties files > used by karaf for setting up entire environment such system.properties and > config.properties. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5646) Support env:XXX subtitution missing for system.properties
[ https://issues.apache.org/jira/browse/KARAF-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400287#comment-16400287 ] ASF subversion and git services commented on KARAF-5646: Commit 48802f750ae28fe2ab55d74b282cb51d3ffaebe5 in karaf's branch refs/heads/karaf-4.1.x from [~gnt] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=48802f7 ] [KARAF-5646] Support env:XXX substitution for system.properties > Support env:XXX subtitution missing for system.properties > - > > Key: KARAF-5646 > URL: https://issues.apache.org/jira/browse/KARAF-5646 > Project: Karaf > Issue Type: Bug > Components: karaf-util >Affects Versions: 4.2.0, 4.1.5 >Reporter: Łukasz Dywicki >Assignee: Jean-Baptiste Onofré >Priority: Major > > Variable substitution implemented as part of KARAF-3434 works fine with files > processed via fileinstall, however it does not work with properties files > used by karaf for setting up entire environment such system.properties and > config.properties. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5640) Unable to acquire the state change lock for apache.felix.fileinstall
[
https://issues.apache.org/jira/browse/KARAF-5640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400084#comment-16400084
]
vijay p commented on KARAF-5640:
-
Even after having JAVA env set, I get the same error.
> Unable to acquire the state change lock for apache.felix.fileinstall
>
>
> Key: KARAF-5640
> URL: https://issues.apache.org/jira/browse/KARAF-5640
> Project: Karaf
> Issue Type: Question
> Components: karaf-osgi
>Affects Versions: 4.1.4
>Reporter: vijay p
>Priority: Major
>
> Hi ,
> I tried to install karaf 4.1.4 and i am getting the following error .
> {code}
> 2018-02-22T14:56:12.912+0100 | ERROR | blisher@6eebc39e | o.a.f.fileinstall |
> ogback.internal.FrameworkHandler 144 | 9 - org.apache.felix.fileinstall -
> 3.6.4 | FrameworkEvent ERROR - org.apache.felix.fileinstall
> org.osgi.framework.BundleException: Unable to acquire the state change lock
> for the module: osgi.identity; osgi.identity="org.apache.felix.fileinstall";
> type="osgi.bundle"; version:Version="3.6.4" [id=9] STOPPED [STOPPED]
> at org.eclipse.osgi.container.Module.lockStateChange(Module.java:337)
> at org.eclipse.osgi.container.Module.stop(Module.java:490)
> at
> org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.decStartLevel(ModuleContainer.java:1661)
> at
> org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1580)
> at org.eclipse.osgi.container.SystemModule.stopWorker(SystemModule.java:270)
> at
> org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule.stopWorker(EquinoxBundle.java:147)
> at org.eclipse.osgi.container.Module.doStop(Module.java:636)
> at org.eclipse.osgi.container.Module.stop(Module.java:498)
> at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:202)
> at
> org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:165)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.util.concurrent.TimeoutException: Timeout after waiting 5
> seconds to acquire the lock.
> at org.eclipse.osgi.container.Module.lockStateChange(Module.java:334)
> ... 10 common frames omitted
> {code}
> May i know where am i wrong and could you give me a solution on how to
> resolve this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (KARAF-5666) Shell interprets exclamation mark
[ https://issues.apache.org/jira/browse/KARAF-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed KARAF-5666. -- Resolution: Not A Problem Assignee: Guillaume Nodet > Shell interprets exclamation mark > -- > > Key: KARAF-5666 > URL: https://issues.apache.org/jira/browse/KARAF-5666 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.2.0.M2 >Reporter: Linus Tentler >Assignee: Guillaume Nodet >Priority: Major > > Shell interprets exclamation mark in passwords when trying to add a user. > Steps to reproduce: > --> open ssh session > --> manage realm > --> user-add test 1212! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
