Hi there,
I'm with a group that provisions our own instance of Karaf. We've run into
an issue that might be a bug, so I wanted to ask here first.
It has to do with a *first-time deployment and start-up* of the Karaf
container. We un-tar the instance but before starting it we put our
application J
I've confirmed that
featuresBootAsynchronous=false
felix.fileinstall.active.level = 80
are indeed the settings that are being used. Oddly enough when I ran it
again I couldn't reproduce the error on my build environment. However when I
set up the same deployment method in a Docker container, i
JIRA ticket here. Thanks!
https://issues.apache.org/jira/browse/KARAF-4723
Guillaume Nodet-2 wrote
> Could you raise a JIRA for that please ?
> I think I've just unwillingly reproduced the issue and I have a fix for
> it.
>
> 2016-09-10 0:51 GMT+02:00 afbagwe <
>
We've recently switched to using the branding.properties file in the etc
folder which has worked great so far. However when we start Karaf server as
a background process and attempt to connect with the client is still uses
the default Karaf branding page for the console interface instead of our
own
We are using 4.0.6.
So I can take a pristine tar.gz of Karaf 4.0.6, drop my branding.properties
in the etc folder and get it to show up when I run the server in console
mode. However if I do:
./start
./client
(enter default Karaf password)
the console comes up with the default branding instead o
Awesome! Thank you :)
--
View this message in context:
http://karaf.922171.n3.nabble.com/Branding-properties-file-not-picked-up-by-Karaf-client-tp4048143p4048148.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Is there any way to take advantage of Log4J2 composition rules inside of
Karaf?
https://logging.apache.org/log4j/2.x/manual/configuration.html#CompositeConfiguration
I'm using Karaf and configuring with the pax-logging CFG file and pointing
to a log4j2.xml file in my etc/ folder. Works great, exc
I'm trying to write a features XML file that will be included in a KAR for
deployment.
While my individual features are functional, when I perform the command:
kar:install file:/path/to/kar
everything gets loaded into Karaf, but all the features are automatically
started. While this is fine for som
Yes, as I mentioned I have tried using the "install" attribute.
Here is one part of my features file:
transaction
camel-core
mvn:com.eclipsesource.minimal-json/minimal-json/0.9.4
mvn:org.apache.camel/camel-hazelcast/${camel.version}
mvn:com.hazelcast/hazelcast/${haz
Yes. Here's the content of features.xml file inside the KAR...
http://karaf.apache.org/xmlns/features/v1.4.0";
name="hazelcast-1.0.0-SNAPSHOT">
mvn:org.apache.karaf.features/standard/4.1.1/xml/features
This feature set provides Hazelcast to be used
independently or through Camel.
Will rename, thanks. :)
Side question. I was not able to track down the difference between
"dependency" and "prerequisite" boolean attributes on the feature tag. Or
how the former differs from the same attribute on the bundle tag.
Can you provide an explanation or a link to such?
Thanks again!
Hey guys. I'm seeing a problem I didn't have in Karaf 4.1.2
When I try to install the camel-cxf package I get the following error that
causes the Karaf client to crash to the command line:
2017-11-28T08:53:13,838 | ERROR | Karaf local console user karaf | ShellUtil
| 42 -
We use a log4j2.xml file in our Karaf configuration (that we point to from
the pax logging cfg file). When we tested it with Karaf 4.1.5, we got the
following error doing log:tail
28-Feb-2018 13:00:12.613 [ERROR] nsole user admin | ShellUtil|
76 - org.apache.karaf.shell.core - 4.1.5 |
Here's the XML config we are using:
%d{dd-MMM- HH:mm:ss.SSS} [%-5.5p]
%-16.16t | %-20.20c{1} | %X{bundle.id} -%X{bundle.name} - %X{bundle.version}
| %m%n
Whenever I perform the client log commands. There's no indication of a
problem immediately after startup if I examine the log outside of Karaf.
-A
jbonofre wrote
> Hi
>
> We didn't change the Pax Logging (Log4j2) version between 4.1.4 and 4.1.5.
>
> Maybe we introduced a regression due to KA
Hi JB.
It looks like this problem is still present in the newly released Karaf
4.2.0
Thanks,
-A
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
Any idea when this might be fixed? We'd like to upgrade our Karaf version but
our project managers don't want to have to change their log4j2 files to a
different format.
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
Yes, I did! :)
https://issues.apache.org/jira/browse/KARAF-5790
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
Awhile back I posted a thread about a problem with the logger when invoked
from the shell script, documented here:
http://karaf.922171.n3.nabble.com/Karaf-4-1-5-and-log-configuration-td4052606.html
https://issues.apache.org/jira/browse/KARAF-5790
Although the issue has been marked as closed, iss
My apologies. It looks like this was brought up in an earlier thread.
(http://karaf.922171.n3.nabble.com/Problem-with-log4j2-xml-and-log-display-td4054619.html)
The resolution is to make certain there is a logger created for
org.apache.sshd in the config.
Still, it would probably be a good idea t
20 matches
Mail list logo
