Hi
when moving from Java 8 to Java 9+ (i.e 17 in my case), what is the
preferred approach for JARs that so far were put into the Karafs
"lib/ext" directory?
- Martin
Hi all, I noticed a change in SSH server session close behavior, as I
upgraded from 4.3.10 to 4.4.5.
Doing calls such as
ssh -p 8101 karaf@localhost feature:list
still works fine. However with 4.4.5, the ssh client now sporadically
reports
Connection to localhost closed by remote host.
Hi
Wanted to understand if anyone has Camel 4 running in Karaf 4.3 or 4.4?
Also reading that Camel Karaf is being moved to Karaf as a subproject,
but I can't figure out the details..
Any wisdom is much appreciated :)
- Martin
wrote:
> Hi Martin,
>
> Let me try to reproduce. Did it work with previous Karaf version ?
>
> Regards
> JB
>
> On Fri, Sep 9, 2022 at 10:04 PM Martin Lichtin via user
> wrote:
> >
> > Using ssh to execute Karaf commands, there's buffering going on
Using ssh to execute Karaf commands, there's buffering going on and one
cannot see a command output as it happens.
e.g.
ssh -p 8101 karaf@localhost "ls; sleep 10"
does not show the "ls" output, it's only flushed and visible after the
10s sleep.
For commands with large output (say 10k) one c
Has anyone used Pax-Web settings
org.ops4j.pax.web.ssl.ciphersuites.excluded=
org.ops4j.pax.web.ssl.ciphersuites.included=
? I've tried, for example, to exclude all ciphers with
org.ops4j.pax.web.ssl.ciphersuites.excluded=.*
but it doesn't seem to have an effect.
+Shift+F9), going to the involved
Agent Group, then Agent Mapping > Debug... > tab *Agent Options*
To be effective it requires an application restart.
- Martin
On 03.09.2020 21:26, Martin Lichtin wrote:
It looks like Dynatrace has an issue during instrumentation. There's this stac
e the dynatrace agent creates its own MBeanServer, overriding the Karaf one
?
Can you check with the service:list command if you see the MBeanServer service
available (or bundle:server with karaf.management bundle id) ?
Regards
JB
Le 2 sept. 2020 à 15:31, Martin Lichtin a écrit :
Having an issue w
Having an issue with a Karaf deployment that is supervised by Dynatrace.
After upgrading from Karaf 14.1.7 to 4.2.9, the JMX bean server reference (in
blueprint)
is no longer available. Seeing "unresolved dependencies
[(objectClass=javax.management.MBeanServer)]" at startup.
Would anyone
Yes that should work. You need the parenthesis.
The code is doing something like
String filterString = '(' + Constants.OBJECTCLASS + '=' +
clazz.getName() + ')';
if (filter != null && !filter.isEmpty()) {
filterString = "(&" + filterString + fi
Yes, an option for disabling Ctrl-D would be great.
Perhaps when running Karaf in the foreground this could be the default (as a
'logout' is equal to 'shutdown').
On 03.06.2019 11:57, Jean-Baptiste Onofr?? wrote:
Hi,
You want to fully disable CTRL-D ? (and force "logout" usage instead)
I can
/2019 17:46, Martin Lichtin wrote:
https://issues.apache.org/jira/browse/KARAF-6234
Thanks in advance. Is this a situation Karaf can recover from or should
I restart if this issue occurs?
- Martin
On 11.04.2019 16:05, Jean-Baptiste Onofré wrote:
Yes, it's rarely null for the service refe
hould improve the code to fallback when it's null.
Can you please create a Jira, I will tackle that ?
Sorry about that.
Regards
JB
On 11/04/2019 15:56, Martin Lichtin wrote:
Has anyone seen this at Karaf startup and understands what the cause is?
2019-04-10T20:23:42,571 | INFO | Felix
Has anyone seen this at Karaf startup and understands what the cause is?
2019-04-10T20:23:42,571 | INFO | FelixStartLevel | CommandExtension
| mpl.action.osgi.CommandExtension 146 | 44 -
org.apache.karaf.shell.core - 4.1.7 | Registering commands for bundle
org.apache.
Hi, has anyone else seen this issue as well, or can reproduce it?
When using 'authentication by key' then sometimes Karaf still asks for the
password,
i.e. it fails to log on using the key.
I can easily reproduce it with
while true; do ssh -p 8101 -i karaf.id_dsa karaf@localhost date; done
Th
artin
On 22.12.2018 17:02, Martin Lichtin wrote:
Hi Karaf Users
Can someone confirm password-less login using a public/private key-pair works
with Karaf 4.1.7?
It's documented at:
http://karaf.apache.org/manual/latest/#_managing_authentication_by_key
I cannot get it work and wondering if I&#x
Hi Karaf Users
Can someone confirm password-less login using a public/private key-pair works
with Karaf 4.1.7?
It's documented at:
http://karaf.apache.org/manual/latest/#_managing_authentication_by_key
I cannot get it work and wondering if I'm doing something wrong. Steps I did to
test the fe
nal import in cause ?
Thanks,
Regards
JB
On 12/12/2018 11:32, Martin Lichtin wrote:
It happens during a Pax-Exam test, so all features are loaded via
"featuresBoot".
What I can see is that the pax-logging-log4j2 bundle has a lot of optional
Imports. So when more bundles are loaded,
Has anyone tried running
feature:install -v camel-cxf
? It has a big unwanted effect of refreshing many core Karaf bundles, due to
the fact that Camel CXF classes still import
"org.apache.aries.blueprint.reflect" (see also KARAF-4932).
Refreshing bundles:
org.apache.aries.blueprint.cm/1.1.0
you please provide your feature or do a feature:install -v to see
the cause of the refresh ?
A simple workaround is to set your feature as featuresBoot, you won't
have the refresh.
Regards
JB
On 11/12/2018 18:47, Martin Lichtin wrote:
When loading features, I have the problematic situat
When loading features, I have the problematic situation of
2018-12-11T18:16:00,189 | INFO | features-1-thread-1 | FeaturesServiceImpl
| FeaturesServiceImpl 1286 | karaf.features.core - 4.1.7 | Stopping bundles:
2018-12-11T18:16:00,189 | INFO | features-1-thread-1 | FeaturesServiceImpl
|
In the output I receive it's not clear which bundles were stopped (and why).
Just 1 or all 18?
Also, all log comes from the same code line, so is it from Deployer line 602 or
line 813?
Would be nice if this could be made clearer.
2017-12-06 11:21:35,552 | INFO | pool-2-thread-1 |
Featu
e you using ?
2. It mimics what we have for "dumper" (in the dump command). It's a way to
extend the info provided. So, some users/custom distributions can use this feature.
Regards
JB
On 11/14/2017 03:03 PM, Martin Lichtin wrote:
Wanted to ask two things about shell:
Wanted to ask two things about shell:info (4.0.10)
a) OS Memory details:
printValue("Total physical memory", maxNameLen,
printSizeInKb(getSunOsValueAsLong(os, "getTotalPhysicalMemorySize")));
printValue("Free physical memory", maxNameLen,
printSizeInKb(getSunOsValueAsLong(os, "getFreePh
I have a situation with loading a feature in that a completely unrelated bundle
gets re-loaded/updated.
The affected bundle is a synthetic one, i.e. blueprint: xml file.
The log shows:
| INFO | rnal.service.FeaturesServiceImpl 1225 | Adding features:
my-feature/[1.1.0.SNAPSHOT,1.1.0.SNAPSHOT]
|
| 0.0.0.0 |
Stopped | 0 | foobar
karaf@root()> instance:start foobar
8103 | 0.0.0.0 | 1101 | 0.0.0.0 | 6 | 0.0.0.0 |
Started | 17002 | foobar
Are you on Windows or Linux ?
I checked and etc seems OK.
Regards
JB
On 09/27/2017 06:54 PM, Martin Lichti
Wanted to ask if the "instance" feature is working for anyone in 4.0.10? It no
longer does for me.It seems the instance:create is not populating 'etc' with
all the necessary files.
Seeing the following once in a while when starting an instance:
java.lang.NullPointerException
at
org.apache.karaf.instance.core.internal.InstanceServiceImpl$14.call(InstanceServiceImpl.java:912)
at
org.apache.karaf.instance.core.internal.InstanceServiceImpl$14.call(InstanceServiceImpl.j
Trying to port a Completer (using the deprecated interface) to Karaf 4.
The code calls CommandSessionHolder.getSession(), unfortunately that no longer
returns the session.
Is there an alternative way to access the Felix CommandSession in an old-style
Completer?
-16 18:36 GMT+02:00 Martin Lichtin mailto:lich...@yahoo.com>>:
Hi Achim
Right, I can still use the "old"-style with Blueprint. But all this code is
marked as deprecated.
So I'm desparately trying to find a solution using the "new"-style Karaf
commands,
filtering available on that annotation.
regards, Achim
2017-06-15 8:38 GMT+02:00 Martin Lichtin mailto:lich...@yahoo.com>>:
So far I could not find a way to do this in the new Karaf command framework.
A command is now instantiated each time it is invoked.
It can use OSGi servi
a service), but not the
beans by their name.
oh well..
On 02.06.2017 20:23, Martin Lichtin wrote:
In Karaf 3, a command can be defined in Blueprint as:
where in my case "producerTemplate" comes from a CamelContext created in the
same Blueprint cont
In Karaf 3, a command can be defined in Blueprint as:
where in my case "producerTemplate" comes from a CamelContext created in the
same Blueprint context.
Now in Karaf 4, how would I do the same, i.e. set the property?
- Martin
Having a particular situation at startup where Karaf (4.0.9) is stuck and not
able to install the feature.
It seems to (forever) hang in:
"pool-2-thread-1" #48 prio=5 os_prio=0 tid=0x1c9b5800 nid=0x1680
runnable [0x21ffe000]
java.lang.Thread.State: RUNNABLE
at org.apa
I'm in the process of moving a system from Karaf 3 to 4.0. The 4.0 'features'
changes turn out to be quite painful to upgrade..
In particulur, with Pax-Exam, I have a situation with a feature B, where bundle
B requires a service from bundle A, from feature A:
http://karaf.apache.org/xmlns/featu
The solution was to add "oracle.security.pki" to
org.osgi.framework.bootdelegation (without the .*)
It works now.
____
From: Martin Lichtin
To: "user@karaf.apache.org"
Sent: Sunday, April 9, 2017 12:49 AM
Subject: Karaf Support for Oracle Wal
Having trouble with adding support for Oracle Wallet. Has anyone had success
with it?
One needs to register oracle.security.pki.OraclePKIProvider, therefore add
three JARs
oraclepki.jar, osdt_cert.jar, osdt_core.jar
to "lib/ext" and extend org.apache.karaf.security.providers with the class n
Hi Jochen
Looks like you have the same issue I had back in September?
http://activemq.2283324.n4.nabble.com/Cannot-start-Activemq-5-14-0-in-a-Karaf-OSGi-container-without-internet-access-td4716513.html
I ended up patching the activemq-osgi jar.
- Martin
On 06.11.2016 19:13, jochenw wrote:
Hi
?
In karaf >= 4, the reason should be printed if you use the --verbose flag on
the command.
2016-10-06 18:13 GMT+02:00 Martin Lichtin mailto:lich...@yahoo.com>>:
Hi
I sometimes see this "Refreshing bundles ... " output when installing a
feature. E.g.:
Hi
I sometimes see this "Refreshing bundles ... " output when installing a
feature. E.g.:
Refreshing bundles org.apache.servicemix.bundles.jaxb-impl (80)
Can you help me figure out what is causing the refresh? There must a logic
somewhere.
Ideally, is there a debug log that I can turn on to s
Hi
I have several bundles and features that are -SNAPSHOT versioned, residing in
$HOME/.m2/repository (together with all the other bundles)
Karaf (v3.0.8) should _not_ attempt to look for a newer version, but simply use
what is there. Is this possible?
I have org.ops4j.pax.url.mvn.globalUpdate
Hi All
Do you guys understand what the problem could be here? I see in a Karaf (3.0.6)
the following warning:
2016-08-11 17:57:41,201 | WARN | 22d83aa7]-nio2-thread-14 | ServerSession
| d.common.session.AbstractSession 456 | 30 -
org.apache.sshd.core - 0.14.0 | Exception
A bundle listener can be used, but one needs to use the
"SynchronousBundleListener" interface.
Only with this interface does one receive the 'STOPPING' events.
On 11.07.2016 16:22, Martin Lichtin wrote:
Hi All
What is the best approach to intercept the Karaf "shu
Hi All
What is the best approach to intercept the Karaf "shutdown" command, before it
starts shutting down any bundles?
Karaf does a getBundle(0).stop() on receiving a "shutdown" command.
There's no FrameworkEvent raised on bundle(0).stop afaics.
A bundle listener on bundle 0 should work, but do
hat causing the issue.
On 18.06.2016 10:24, Jean-Baptiste Onofré wrote:
I guess you are using OpenJDK, right ?
It's fixed in 3.0.7 (currently in vote).
Regards
JB
On 06/18/2016 09:22 AM, Martin Lichtin wrote:
After upgrading from Karaf 3.0.3 to 3.0.6, every so often this exception
is occu
After upgrading from Karaf 3.0.3 to 3.0.6, every so often this exception is
occuring:
2016-06-16 09:42:55,343 | WARN | [4866a9bd]-nio2-thread-4 | ClientSessionImpl
| d.common.session.AbstractSession 456 | 30 -
org.apache.sshd.core - 0.14.0 | Exception caught
java.security.Inva
In Karaf version 3.0.6, when trying to upgrade ActiveMQ to version 5.13.3, it
fails with
ERROR: Bundle activemq-karaf [86] Error starting/stopping bundle.
(org.osgi.framework.BundleException: Unresolved constraint in bundle activemq-karaf [86]:
Unable to resolve 86.0: missing requirement [86.0
When profiling against a Karaf (using flight recorder), I see the following
Exception exactly once a second:
java.lang.Throwable.(String) line: 267
java.lang.Exception.(String) line: 52
java.io.IOException.(String) line: 58
java.util.zip.ZipException.(String) line: 58
To access system properties, use for example:
but accessing environment variables is still an open issue:
https://issues.apache.org/jira/browse/ARIES-1311
- Martin
On 17.02.2016 10:32, Frizz wrote:
Do have
Wanted to ask if anyone sucessfully managed a JMX connection to a Karaf, using
only well-known ports (through a firewall)?
By default, JMX uses a random/roaming RMI port, which is a problem when a
firewall is inbetween only allowing fixed ports.
There are documented ways around it, for example:
java:77)
at
org.apache.karaf.management.boot.KarafMBeanServerBuilder$MBeanInvocationHandler.invoke(KarafMBeanServerBuilder.java:63)
at com.sun.proxy.$Proxy13.getAttribute(Unknown Source)
at my.package.JmxAccessPaxTest.test_jmxAccess(JmxAccessPaxTest.java:47)
Martin
From: Achim Nierbeck
To: Martin Lichtin
Cc: "user@karaf
seen this behavior too. AFAIC this is a bug.
Do you happen to have a scenario where it's really reproducible?
Could you open a issue for it?
Thanks, Achim
2015-03-10 14:23 GMT+01:00 Martin Lichtin <mailto:lich...@yahoo.com>>:
I understand that access to MBeans is protected via RBAC mec
several
places:
./etc/org.ops4j.pax.logging.cfg
./bin/stop
./bin/start
./bin/status
With a KARAF_LOG, the location could be managed in one place (./bin/setenv).
On 11.03.2015 11:24, Achim Nierbeck wrote:
How about ${karaf.home}/log?
2015-03-11 11:00 GMT+01:00 Martin Lichtin <mailto:lich...@ya
I was wondering about supporting configuring a specific location for the Karaf
log files.
There are use cases where these files must not be kept under the "data"
directory.
Could it be supported by use of a ${karaf.log} which defaults to
${karaf.data}/log ?
I understand that access to MBeans is protected via RBAC mechanism:
http://karaf.apache.org/manual/latest/users-guide/monitoring.html
However, is this also the case for code running inside Karaf?
E.g. when doing
MBeanServer mbs = ManagementFactory.getPlatformMBeanServer();
it seems I c
gt; From: Achim Nierbeck
>To: "user@karaf.apache.org" ; Martin Lichtin
>
>Sent: Monday, March 9, 2015 1:17 PM
>Subject: Re: How does work in feature files
>
>
>
>Conditional means, this part is conditionally installed in case the webconsole
>is already installed or in
Inside Karaf's "standard" feature descriptor, there is
webconsole
mvn:org.apache.karaf.webconsole/org.apache.karaf.webconsole.instance/3.0.3
mvn:org.apache.karaf.webconsole/org.apache.karaf.webconsole.features/3.0.3
mvn:org.apache.karaf.webconsole/org.apache.karaf.webconsol
Wanted to ask if this is a feature or a bug:
karaf@root()> feature:install 007
Error executing command: No feature named '7' with version '0.0.0' available
I have other, custom commands using string arguments and these now require
quoted values in case of leading zeros.
Hi
While upgrading from 2.3.4 to 3.0.2, I have an issue with configuring
org.ops4j.pax.url.mvn.cfg
I need to access all 'remote' artifacts via a password-protected 'mirror' Maven
repository.
This worked fine in 2.3.4 by configuring
org.ops4j.pax.url.mvn.repositories=http\://user\:pass@repo/a
I've seen a similar issue and at some point opened
https://issues.apache.org/jira/browse/KARAF-2348
With the versions I use it's quite obvious that Pax-Exam does not wait
for the container to shut down completely.
Martin
PS: My workaround is to wait a bit for the ssh port to become available
Every so often, Karaf 2.3.1 startup fails with one or more bundles waiting for
a "namespace".
Bundle org.apache.karaf.diagnostic.command: waiting for dependencies
[(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://karaf.apache.org/xmlns/shell/v1
I'm struggling a bit with shell command argument completers.
My command has two arguments, I need a completer only for the second
argument.
Below configuration does not seem to work (myCompleter is not called):
Is thi
Can features schema 1.1.0 be made available at
http://karaf.apache.org/xmlns/features/v1.1.0 ?
Hi guys
I am having an issue with the "org.osgi.service.jdbc" package dependency (H2
started requiring it).
According to
http://mail-archives.apache.org/mod_mbox/karaf-user/201210.mbox/%3c5085540b.3090...@nanthrax.net%3E
it is bundle org.osgi.compendium/4.3.1 (for Karaf 2.3.1) that offers this
pring-osgi-annotation-1.2.1.pom
(2 KB at 75.6 KB/sec)
...
>
> From: Achim Nierbeck
>To: "user@karaf.apache.org" ; Martin Lichtin
>
>Sent: Monday, May 13, 2013 11:16 AM
>Subject: Re: Karaf has transitive dependencies on old Spri
Hi
I've seen this issue with NMR recently
https://issues.apache.org/jira/browse/SMX4NMR-313 and also see it with Karaf.
Does anyone understand why Karaf depends spring-osgi-* and therefore on oldish
versions of spring artifacts?
The dependency goes like
apache-karaf [2.3.1]
spring-osgi-exten
Good news :) and it would be great (also to make this behaviour consistent), if
the internal bundle ordering would be done for the "uninstall" case as well.
Martin
>
> From: Jamie G.
>To: user@karaf.apache.org; Martin Lichtin
>Sent: W
Hi
can you clarify how start-order is accounted for when used as part of a feature?
For example
b1
b2
b3
As far as I can see, the start-level value has no effect.
It is not taken into account during feature:install or feature:uninstall.
I see that after Kara
68 matches
Mail list logo
