Timothy Kim created AMQ-8606:
--------------------------------
Summary: Cached connection does not return error after rebooting
ActiveMQ and a message is lost
Key: AMQ-8606
URL: https://issues.apache.org/jira/browse/AMQ-8606
Project: ActiveMQ
Issue Type: Bug
Components: STOMP
Affects Versions: 5.16.3
Environment: # cat /etc/os-release
NAME="Red Hat Enterprise Linux"
VERSION="8.4 (Ootpa)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="8.4"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Red Hat Enterprise Linux 8.4 (Ootpa)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:8.4:GA"
HOME_URL="https://www.redhat.com/";
DOCUMENTATION_URL="https://access.redhat.com/documentation/red_hat_enterprise_linux/8/";
BUG_REPORT_URL="https://bugzilla.redhat.com/";
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_BUGZILLA_PRODUCT_VERSION=8.4
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.4"
Reporter: Timothy Kim
+*Background:*+
I am using STOMP to publish messages to a topic in ActiveMQ. In my client
program, written in lua, I keep a publishing connection in a variable and use
it to publish all topic messages. If the connection times out, it catches error
and get a new connection and continues .....
+*Issue:*+
When an ActiveMQ instance is rebooted for whatever the reason, my client
program doesn't know it was rebooted and continue to publishes a topic message
with the connection that was obtained before the reboot. Strangely it doesn't
get any error message. It should fail because the connection is not valid.
When it tries to publish another message, then the client program gets error
message -"{color:#FF0000}broken pipe{color}". For this, I only get to retry the
second message to recover by retrying it. The first message after the reboot is
lost because a topic subscriber doesn't get the message.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
