Peek Message does not work

[samzph]

When setting pulsar.peek.message=true in /pulsar-manager/pulsar-manager/application.properties, I still receive the following error:

This is mounted into the container on creation, I've even tried restarting the manager within the container. It seems to not take the setting. I am deploying using the Helm chart with some modifications:

I have confirmed inside the container that the properties are applied.

/pulsar-manager # cat pulsar-manager/application.properties | tail -n 2
# support peek message, default false
pulsar.peek.message=true

This is the command Pulsar Manager is being run with: /usr/lib/jvm/java-1.8-openjdk/jre/bin/java -Dlog4j2.formatMsgNoLookups=true -classpath /pulsar-manager/pulsar-manager/lib/pulsar-manager.jar:/pulsar-manager/pulsar-manager/lib/spring-cloud-starter-netflix-zuul-2.0.2.RELEASE.jar:/pulsar-manager/pulsar-manager/lib/spring-boot-starter-web-2.0.2.RELEASE.jar:/pulsar-manager/pulsar-manager/lib/pagehelper-spring-boot-starter-1.2.4.jar:/pulsar-manager/pulsar-manager/lib/mybatis-spring-boot-starter-2.1.2.jar:/pulsar-manager/pulsar-manager/lib/spring-boot-starter-thymeleaf-2.0.2.RELEASE.jar:/pulsar-manager/pulsar-manager/lib/spring-boot-starter-security-2.0.2.RELEASE.jar:/pulsar-manager/pulsar-manager/lib/spring-boot-starter-json-2.0.2.RELEASE.jar:/pulsar-manager/pulsar-manager/lib/spring-cloud-netflix-zuul-2.0.2.RELEASE.jar:/pulsar-manager/pulsar-manager/lib/spring-cloud-starter-netflix-hystrix-2.0.2.RELEASE.jar:/pulsar-manager/pulsar-manager/lib/spring-cloud-starter-netflix-ribbon-2.0.2.RELEASE.jar:/pulsar-manager/pulsar-manager/lib/spring-cloud-starter-netflix-archaius-2.0.2.RELEASE.jar:/pulsar-manager/pulsar-manager/lib/spring-cloud-starter-2.0.2.RELEASE.jar:/pulsar-manager/pulsar-manager/lib/spring-boot-starter-actuator-2.0.2.RELEASE.jar:/pulsar-manager/pulsar-manager/lib/spring-boot-starter-jdbc-2.0.2.RELEASE.jar:/pulsar-manager/pulsar-manager/lib/spring-cloud-netflix-core-2.0.2.RELEASE.jar:/pulsar-manager/pulsar-manager/lib/spring-boot-starter-aop-2.0.2.RELEASE.jar:/pulsar-manager/pulsar-manager/lib/spring-boot-starter-2.0.2.RELEASE.jar:/pulsar-manager/pulsar-manager/lib/pagehelper-5.1.11.jar:/pulsar-manager/pulsar-manager/lib/postgresql-42.2.5.jar:/pulsar-manager/pulsar-manager/lib/herddb-jdbc-0.19.0.jar:/pulsar-manager/pulsar-manager/lib/hibernate-validator-6.0.9.Final.jar:/pulsar-manager/pulsar-manager/lib/pulsar-broker-2.4.1.jar:/pulsar-manager/pulsar-manager/lib/bkvm-2.0.0-war-no-libs.war:/pulsar-manager/pulsar-manager/lib/bkvm-2.0.0-classes.jar:/pulsar-manager/pulsar-manager/lib/pulsar-websocket-2.4.1.jar:/pulsar-manager/pulsar-manager/lib

[wyldebill]

I am seeing the same thing with all of the "Backlog Operations". They all fail with 500 errors. Are there specific versions of Pulsar Manager that only work with specific versions of Pulsar? I am running Pulsar:2.9.2 and pulsar-manager:v0.3.0 in Docker, standalone.

[alpreu]

If you're running into this issue, you can try @streamvisor as an alternative. It supports live browsing of messages (and automatic deserialization if they have a schema) and it's free :)

[liamgib]

We fixed this by configuring the following env var to true "PULSAR_PEEK_MESSAGE". Once added, the issue was resolved.