Issues starting transactions

I am using a Pulsar 2.8.0 container starting in standalone mode. I am following this page to enable transactions https://pulsar.apache.org/docs/en/next/txn-use/ (specifically, setting transactionCoordinatorEnabled to true and running bin/pulsar initialize-transaction-coordinator-metadata -cs 127.0.0.1:2181 -c standalone).

When I try to start a transaction with version 2.8.1, I get an exception Transaction manager is not started or not enabled with stack trace:

   at [e-mail](Unit unitVar0)
   at FSharp.Control.Tasks.TaskBuilder.tryWith[a](FSharpFunc`2 step, FSharpFunc`2 catch)
--- End of stack trace from previous location ---
   at [e-mail](Unit unitVar0)
   at FSharp.Control.Tasks.TaskBuilder.StepStateMachine`1.nextAwaitable()
--- End of stack trace from previous location ---
  ...

Here is a quick repro:

private async static Task TestPulsarContainer(string connectionString)
{
	string topicName = "testTopic";
	PulsarClient pulsarClient = await new PulsarClientBuilder().EnableTransaction(true).ServiceUrl(connectionString).BuildAsync();
	IProducer<byte[]> producer = await pulsarClient.NewProducer().Topic(topicName).CreateAsync();
	IConsumer<byte[]> consumer = await pulsarClient.NewConsumer().Topic(topicName).SubscriptionName("testSubscription").SubscribeAsync();

	string testMessage = "Test message";
	MessageId messageId = await producer.SendAsync(Encoding.UTF8.GetBytes(testMessage));
	Message<byte[]> message = await consumer.ReceiveAsync();

	// Exception occurs when creating the transaction.
	Transaction transaction = await pulsarClient.NewTransaction().BuildAsync();
	MessageBuilder<byte[]> messageBuilder = producer.NewMessage(Encoding.UTF8.GetBytes("test"), txn: transaction);
	await producer.SendAsync(messageBuilder);
	await consumer.AcknowledgeAsync(message.MessageId, transaction);
	await transaction.Commit();
}

Any ideas on if this is a config issue or a client issue?

[tgrieger-sf]

I got the transactions working. Instead of updating the values and running the transaction initialization command, I run this script at startup:

#!/bin/sh
sed -i 's/transactionCoordinatorEnabled=false/transactionCoordinatorEnabled=true/g' /pulsar/conf/broker.conf
sed -i 's/transactionCoordinatorEnabled=false/transactionCoordinatorEnabled=true/g' /pulsar/conf/standalone.conf
/pulsar/bin/pulsar standalone

Thanks for looking into it, @Lanayx

[tgrieger-sf]

There are no messages happening in the output of the container (if that’s the broker’s log) when that exception occurs. There is output when the topics and subscriptions are created.