[ 
https://issues.apache.org/jira/browse/KAFKA-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377135#comment-16377135
 ] 

Jason Gustafson edited comment on KAFKA-6196 at 2/26/18 4:41 PM:
-----------------------------------------------------------------

Thanks for the report. Marking this as a dup since it seems to be the same 
issue.


was (Author: hachikuji):
Thanks for the patch. Marking this as a dup since it seems to be the same issue.

> Kafka Transactional producer with broker on windows
> ---------------------------------------------------
>
>                 Key: KAFKA-6196
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6196
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients, consumer, producer 
>    Affects Versions: 0.11.0.0, 1.0.0
>         Environment: OS : Windows 10 Pro 64-bit,
> RAM : 10GB
> Processor : Intel Core i3-3240, x64-based processor
>            Reporter: Abhishek Verma
>            Priority: Blocker
>              Labels: windows
>         Attachments: consumer logs.txt, consumer.java, producer logs.txt, 
> producer.java, topic dump log.txt, transaction state dump log.txt
>
>
> While using Kafka Transactional Producer and Consumer transactional state in 
> "__transaction_state" topic is not getting updated as "CompleteCommit" or 
> "CompleteAbort" and in destination topic (which I named as "topic") is not 
> getting either ABORT or COMMIT in "endTxnMarker" field (means end marker 
> message is not generated).
> I have attached producer and consumer console logs, Log dump segment for 
> "__transaction_state" and "topic" topic. with producer and consumer code I am 
> using.
> If my brokers are on windows machine Kafka transaction is not getting 
> committed but on Linux machine it is working properly.
> In producer console log it is saying that transaction is completed 
> successfully but not reflecting in transactional state topic.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to