consumers cannot receive msg from a exist queue

101 views
Skip to first unread message

Jenius_Yang

unread,
Jun 28, 2019, 3:54:18 AM6/28/19
to rabbitmq-users
Hi~ 

since like this: I create a queue a month ago, but I find the consumers disappeared in a sudden, and when I restart my consumer client, they still cannot  consume msg in the queue.

But if I create a new queue with the same method, it works well

why consumers cannot receive msg from a exist queue,and the queue's consumers displayed as 0?

client:amqp-client-3.4.1 
server:rabbitmq 3.4.4 erlang19

Daniil Fedotov

unread,
Jun 28, 2019, 12:10:27 PM6/28/19
to rabbitmq-users
Hi,

It's hard to tell from the information provided.
Can you give more details on how do you configure your client, maybe a code snippet.
Also how do you observe the queue. Is that via the management plugin or rabbitmqctl? What exactly do you see there?

Also version 3.4.1 is quite old and there were so many issues fixed since then, that I'd recommend to upgrade, if you can.

Michael Klishin

unread,
Jun 30, 2019, 5:37:50 PM6/30/19
to rabbitmq-users
RabbitMQ 3.4.x has been out of support for several years now [1][2]. Please upgrade [3].


--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/5491ce00-b835-4352-b1b8-effe542422ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
MK

Staff Software Engineer, Pivotal/RabbitMQ

Jenius_Yang

unread,
Jun 30, 2019, 11:06:34 PM6/30/19
to rabbitmq-users
Hi~ 

Thanks for your reply

I use spring-boot in my client , and use the way of spring-amqp to declare and observe the queue not by either management plugin or rabbitmqctl api。

And If I delete this queue, and rerun, Its work well ,so I dont think my client configuartion has a code snippet.


PS:consumer client configuration as below, and the  "q-user-department-group-prod" is the issue queue

<rabbit:connection-factory id="connectionFactory" host="${mq.host}" username="${mq.username}" password="${mq.password}" port="${mq.port}" virtual-host="/"  channel-cache-size="10" />
    
<rabbit:admin id="rabbitAdmin" connection-factory="connectionFactory"/>
      
<rabbit:template id="rabbitTemplate" exchange="e-default-prod" routing-key=""  connection-factory="connectionFactory"message-converter="jackson2JsonMessageConverter" />  
    
    
<bean id="jackson2JsonMessageConverter" class="org.springframework.amqp.support.converter.Jackson2JsonMessageConverter" />
<rabbit:queue durable="true" auto-delete="false" exclusive="false" name="q-user-specialtoteam-prod"/>
<rabbit:queue durable="true" auto-delete="false" exclusive="false" name="q-company-open-defaultapp-prod"/>
<rabbit:queue durable="true" auto-delete="false" exclusive="false" name="q-company-default-role-prod"/>
<rabbit:queue durable="true" auto-delete="false" exclusive="false" name="q-user-department-group-prod"/>

<rabbit:direct-exchange name="e-user-specialtoteam-prod" durable="true" auto-delete="false">
    <rabbit:bindings>
        <rabbit:binding queue="q-user-specialtoteam-prod" key=""/>
</rabbit:bindings>
</rabbit:direct-exchange>

<rabbit:fanout-exchange name="e-company-create-prod" durable="true" auto-delete="false">
    <rabbit:bindings>
        <rabbit:binding queue="q-company-open-defaultapp-prod"/>
        <rabbit:binding queue="q-company-default-role-prod"/>
    </rabbit:bindings>
</rabbit:fanout-exchange>

<rabbit:direct-exchange name="e-user-department-group-prod" durable="true" auto-delete="false">
    <rabbit:bindings>
        <rabbit:binding queue="q-user-department-group-prod" key=""/>
</rabbit:bindings>
</rabbit:direct-exchange>
<rabbit:listener-container connection-factory="connectionFactory" acknowledge="auto" >
    <rabbit:listener queues="q-company-openclose-prod" ref="companyOpenCloseListener" />
    <rabbit:listener queues="q-user-specialtoteam-prod" ref="userSpecialToTeamMessageListener" />
    <rabbit:listener queues="q-company-default-role-prod" ref="companyDefaultRoleListener" />
    <rabbit:listener queues="q-user-department-group-prod" ref="departmentGroupListener" />
</rabbit:listener-container>

Jenius_Yang

unread,
Jun 30, 2019, 11:10:34 PM6/30/19
to rabbitmq-users
Hi~, MK

we have upgrade to 3.7.x already in some new env, but some old env ,we are not allow to upgrade ,because it taks a great risk for SLA


Best Regards


On Monday, July 1, 2019 at 5:37:50 AM UTC+8, Michael Klishin wrote:
RabbitMQ 3.4.x has been out of support for several years now [1][2]. Please upgrade [3].


On Fri, Jun 28, 2019 at 9:54 AM Jenius_Yang <yjflo...@gmail.com> wrote:
Hi~ 

since like this: I create a queue a month ago, but I find the consumers disappeared in a sudden, and when I restart my consumer client, they still cannot  consume msg in the queue.

But if I create a new queue with the same method, it works well

why consumers cannot receive msg from a exist queue,and the queue's consumers displayed as 0?

client:amqp-client-3.4.1 
server:rabbitmq 3.4.4 erlang19

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitm...@googlegroups.com.

To post to this group, send email to rabbitm...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/5491ce00-b835-4352-b1b8-effe542422ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Michael Klishin

unread,
Jul 1, 2019, 4:14:34 AM7/1/19
to rabbitmq-users
Jenius,

I'm sorry but we have no guidance to provide for RabbitMQ 3.4.x. It has been out of support for several years.

Please upgrade to 3.7.15 first (see some relevant links in my earlier response).

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.

To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Michael Klishin

unread,
Jul 1, 2019, 4:15:38 AM7/1/19
to rabbitmq-users
Blue/Green deployment is the least invasive upgrade option [1].


To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.

To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Jenius_Yang

unread,
Jul 1, 2019, 4:27:21 AM7/1/19
to rabbitmq-users
Hi~ MK

Blue/Green deployment is great!  But is there any similar  scene that you encounter, maybe its helpful, I indeed wanna find out why,  maybe it also have problems in other higher version?
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitm...@googlegroups.com.

To post to this group, send email to rabbitm...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/a0a3de27-dadf-46a3-b5a4-9cb091f4cf0d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Michael Klishin

unread,
Jul 1, 2019, 4:30:03 AM7/1/19
to rabbitmq-users
It's not something that is commonly reported or we have seen in our own long running environments. There have been 41 release
since 3.4.4, so the answer is "possibly but it's not a commonly reported problem with 3.7.15".

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.

To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
Message has been deleted
Message has been deleted
Message has been deleted

Michael Klishin

unread,
Jul 2, 2019, 7:43:13 AM7/2/19
to rabbitmq-users
"idle since" is an implementation detail. It means the queue process has not been "active" since a certain timestamp.

The metrics you have provided suggest that the queue has no consumers. Use logs [1] and perhaps tcpdump/Wireshark [2] to find out why.
A queue without consumers obviously won't be delivering anything.


On Tue, Jul 2, 2019 at 10:08 AM Jenius_Yang <yjflo...@gmail.com> wrote:
Hi~ MK 

I have reproduce this  again . when I use metrics, it shows below:
{
    "memory":26296784,
    "message_stats":{
        "ack":4941,
        "ack_details":{
            "rate":0
        }
,
        "deliver":4945,
        "deliver_details":{
            "rate":0
        }
,
        "deliver_get":4945,
        "deliver_get_details":{
            "rate":0
        }
,
        "publish":24871,
        "publish_details":{
            "rate":0
        }
,
        "redeliver":3,
        "redeliver_details":{
            "rate":0
        }

    }
,
    "messages":19930,
    "messages_details":{
        "rate":0
    }
,
    "messages_ready":19930,
    "messages_ready_details":{
        "rate":0
    }
,
    "messages_unacknowledged":0,
    "messages_unacknowledged_details":{
        "rate":0
    }
,
    "idle_since":"2019-07-02 15:43:14",
    "consumer_utilisation":"",
    "policy":"ha-all",
    "exclusive_consumer_tag":"",
    "consumers":0,
    "slave_nodes":[
        "rab...@10.171.160.71"
    ]
,
    "synchronised_slave_nodes":[
        "rab...@10.171.160.71"
    ]
,
    "down_slave_nodes":[

    ]
,
    "state":"running",
    "messages_ram":19930,
    "messages_ready_ram":19930,
    "messages_unacknowledged_ram":0,
    "messages_persistent":19930,
    "message_bytes":2998129,
    "message_bytes_ready":2998129,
    "message_bytes_unacknowledged":0,
    "message_bytes_ram":2998129,
    "message_bytes_persistent":2998129,
    "backing_queue_status":{
        "q1":0,
        "q2":0,
        "delta":[
            "delta",
            "undefined",
            0,
            "undefined"
        ]
,
        "q3":0,
        "q4":19930,
        "len":19930,
        "target_ram_count":"infinity",
        "next_seq_id":24871,
        "avg_ingress_rate":0.0799623546233337,
        "avg_egress_rate":0,
        "avg_ack_ingress_rate":0,
        "avg_ack_egress_rate":0,
        "mirror_seen":0,
        "mirror_senders":8
    }
,
    "incoming":[

    ]
,
    "deliveries":[

    ]
,
    "consumer_details":[

    ]
,
    "name":"q-user-department-group-prod",
    "vhost":"/",
    "durable":true,
    "auto_delete":false,
    "arguments":{

    }
,
    "node":"rab...@10.171.160.70"
}

what is "idle_since" mean ?



--
MK

Staff Software Engineer, Pivotal/RabbitMQ

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Jenius_Yang

unread,
Aug 2, 2019, 4:54:58 AM8/2/19
to rabbitmq-users
Hi~ MK thanks for your reply

I find the two rabbitmq nodes ntp time not sychronize, the master is 3 hours earlier than slave, and time on slave node is sync with our ntp server,

and the queues can still produce and consumes just as normal, but i cannot use ./rabbitmqctl list_queues consumers or via management UI to see consumers

Does ntp not  sychronize effect this. consumers show as below from UI:

consumer show as zero.jpg

Reply all
Reply to author
Forward
0 new messages