Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Users List" <log4j-user@logging.apache.org>
MIME-Version: 1.0
In-Reply-To: <CO2PR05MB2456DE66DF50456865B32268B2180@CO2PR05MB2456.namprd05.prod.outlook.com>
References: <CO2PR05MB2456DE66DF50456865B32268B2180@CO2PR05MB2456.namprd05.prod.outlook.com>
From: =?UTF-8?Q?Mikael_St=C3=A5ldal?= <mikael.staldal@magine.com>
Date: Mon, 8 Aug 2016 10:20:06 +0200
Message-ID: <CANEH4Wz-j0Vxck3_UOp3r67yhMpQpgW4QF6eiaEaM6sUhHB7-A@mail.gmail.com>
Subject: Re: Kafka appender expecting String but getting Byte?
To: Log4J Users List <log4j-user@logging.apache.org>
Content-Type: multipart/alternative; boundary=001a1134fd1c76402005398b15ca
archived-at: Mon, 08 Aug 2016 08:20:20 -0000

--001a1134fd1c76402005398b15ca
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Log4j always passes the LogEvent as a byte[] to Kafka, so using the
Kafka StringSerializer
will not work.

You should not specify *key.serializer* or *value.serializer* in the Kafka
appender config, they are automatically set to ByteArraySerializer by
Log4j. I will improve the documentation on that.

I think that *key.class.type* and *value.class.type *are Spring specific
and thus not relevant here.

On Fri, Aug 5, 2016 at 8:03 PM, Meadowlark Bradsher <mbradsher@guidewire.co=
m
> wrote:

> Hello,
>
> I am attempting to use a kafka log appender. The topic is written to Kafk=
a
> but the appender breaks during the messaging.
>
> org.apache.kafka.common.errors.SerializationException: Can't convert
> value of class [B to class org.apache.kafka.common.serialization.StringSe=
rializer
> specified in value.serializer
>
> I had seen only one SO post about this error which seems to point to
> Spring as the culprit but I am not using Spring.
>
> http://stackoverflow.com/questions/32368372/spring-
> integration-kafka-sending-a-basic-string
>
> I am running this in IntelliJ without any Spring configuration. The
> log4j2.xml file is as follows (with modification to the Kafka host).
>
> <?xml version=3D"1.0" encoding=3D"UTF-8"?>
> <Configuration status=3D"WARN">
>   <Appenders>
>     <Console name=3D"Console" target=3D"SYSTEM_OUT">
>       <PatternLayout pattern=3D"%d{HH:mm:ss.SSS} [%t] %-5level %logger{36=
} -
> %msg%n"/>
>     </Console>
>    <Kafka name=3D"Kafka" topic=3D"log-test">
>       <PatternLayout pattern=3D"%date %message"/>
>         <Property name=3D"bootstrap.servers">localhost:9092</Property>
>         <Property name=3D"key.class.type">java.lang.String</Property>
>         <Property name=3D"value.class.type">java.lang.String</Property>
>         <Property name=3D"key.serializer">org.apache.kafka.common.
> serialization.StringSerializer</Property>
>         <Property name=3D"value.serializer">org.apache.kafka.common.
> serialization.StringSerializer</Property>
>     </Kafka>
>   </Appenders>
>   <Loggers>
>     <Root level=3D"DEBUG">
>       <AppenderRef ref=3D"Kafka"/>
>     </Root>
>     <Logger name=3D"org.apache.kafka" level=3D"INFO" >
>       <AppenderRef ref=3D"Kafka"/>
>     </Logger>
>     <!-- avoid recursive logging/ haven't tried OFF yet -->
>   </Loggers>
> </Configuration>
>
>
> The test I am doing is
>
>
>
> private static final Logger logger =3D LogManager.getRootLogger();
>
> logger.info("{\"f1\": \"value1\"}");
>
>
>
> I just downloaded the source to log4j2 to see if this will help me
> understand what is happening but perhaps this obvious to someone in this
> community?
>
>
>
> Any pointers would be very helpful and appreciated.
>
>
>
>
>
> Thanks
>
> Meadowlark Bradsher
>
>
>
>
>
>
>
>


--=20
[image: MagineTV]

*Mikael St=C3=A5ldal*
Senior software developer

*Magine TV*
mikael.staldal@magine.com
Grev Turegatan 3  | 114 46 Stockholm, Sweden  |   www.magine.com

Privileged and/or Confidential Information may be contained in this
message. If you are not the addressee indicated in this message
(or responsible for delivery of the message to such a person), you may not
copy or deliver this message to anyone. In such case,
you should destroy this message and kindly notify the sender by reply
email.

--001a1134fd1c76402005398b15ca--