Dear Karaf Team,
We moved to Karaf 3.0.2 framework and standard features with the 3.0.2
karaf-maven-plugin. The tar.gz done by the assembly still does not seem to
contain our feature.
Expanding the .tar.gz then starting "karaf" on a machine which does not have
access to any maven repository do
PS: Just found that the "system" sub-directory does contain all our jars and
configuration files
[@@ OPEN @@]
-Message d'origine-
De : CLEMENT Jean-Philippe [mailto:jean-philippe.clem...@fr.thalesgroup.com]
Envoyé : lundi 20 octobre 2014 17:29
À : user@karaf.apache.org
Objet : RE: Mave
Hi,
I have been trying unsuccessfully to have a karaf distribution connect
to elastic search via flume using the FlumeLog4jAppender.
I followed the steps listed here
http://blog.nanthrax.net/2012/12/create-custom-log4j-appender-for-karaf-and-pax-logging/
for adding a custom appender and appl
Hi Jean-Philippe,
what's the scope of the features XML or kar dependency ?
Can you share your pom ?
Did you take a look in the assembly archetype ? Does your pom look like
this ?
Regards
JB
On 10/20/2014 05:28 PM, CLEMENT Jean-Philippe wrote:
Dear Karaf Team,
We moved to Karaf 3.0.2 framew
Forgot to mention
Please let me know what knobs can I turn on to further debug this thing.
I tried remote debugging karaf with flume4jappender it looks like the
appender class is not called out at all. How can I further debug whats
happenning?
--
View this message in context:
http://karaf
Hi
Is the fragment bundle attached to the host bundle. You can tell by listing
all bundles with la. The fragment bundle should be in resolved state.
If you do a bundle: info on the host or fragment it should also tell you if
the fragment is attached.
If not try a refresh on the host bundle.
Regard
The fragment seems to show as resolved -- so if it is working we should
have seen it connecting to the hostname specified in the appender
configuration -- which is not happening. How can I find out if its
reaching the point of instantiating the appender specified class and
actually trying to ap
The good news,
Your setup is good as the list of bundles already shows the fragment bundle
to be attached to the right host bundle.
Does the appender require something special? Any certain classes from
log4j?
You could try to debug into the appender and try to see if it is actually
called. If not i