> >
> > Hi,
> > I have wrote a very simple example which has a behaviour I do not expect:
> >
> > If I call LogManager.getLogger(..) from two threads, only one of the
> > loggers logs what I'd expect but if I add an additional call to
> > LogManager.getLo
.getLogger(..) before the threads are started, I see what I'd
> expect so it looks like there is a problem in multi threaded
> initialization.
>
> You can fine the code and the configuration here:
>
> -
>
> https://github.com/lburgazzoli/lb-chronicle/blob/master/chronicle-
pect so it looks like there is a problem in multi threaded initialization.
You can fine the code and the configuration here:
-
https://github.com/lburgazzoli/lb-chronicle/blob/master/chronicle-examples/chronicle-logger-log4j2/src/main/java/com.github.lburgazzoli.openhft.examples.chronicle.log
, Matt Sicker wrote:
> I think you can use different values for @PluginElement than you do for
> @Plugin which helps in the XML/JSON format. I'd have to look into this
> more.
>
>
> On 31 August 2014 10:23, lb wrote:
>
> > I think you should explicit state
9:03 PM, Matt Sicker wrote:
> Good to hear it! Is there anything about the documentation you found
> unclear in that regard?
>
>
> On 30 August 2014 01:44, lb wrote:
>
> > Yes that was the problem, I forgot to mark it as plugin. Now it works,
> > thank you
>
Yes that was the problem, I forgot to mark it as plugin. Now it works,
thank you
On Friday, August 29, 2014, Matt Sicker wrote:
> Is VanillaLogAppenderConfig also marked as a @Plugin and everything?
>
>
> On 28 August 2014 05:13, lb > wrote:
>
> > I'm writing a
I'm writing a custom appender and I have a problem setting up PluginElement:
The xml definition is the following one:
${sys:java.io.tmpdir}/chronology-log4j2/conf-binary-vanilla-chronicle
false
false
false
128
And the PluginFactory method is:
@PluginFactory
publ
