Skip to content
This repository has been archived by the owner on Nov 27, 2018. It is now read-only.

CMB long pool question #52

Open
adamdembek opened this issue Oct 19, 2016 · 0 comments
Open

CMB long pool question #52

adamdembek opened this issue Oct 19, 2016 · 0 comments

Comments

@adamdembek
Copy link

We are testing cmb-2.2.46 in Kubernetes environment.

We started two cmb containers and Kubernetes balance the traffic to those containers from our application.

Our FE application sends receiveMessage with WaitTimeSeconds 20 to one of the CMB

this.sqs.receiveMessage({
"QueueUrl": this.queueUrl,
"MaxNumberOfMessages": this.maxNumberOfMessages,
"VisibilityTimeout": 30,
"WaitTimeSeconds": 20 }

I see that when another application send something to this queue through second cmb container the FE receiveMessage still waits until WaitTimeSeconds.

I see that cmb-xm2el that got the SendMessage request tries to send longpoll_notification_sent to cmb-6a2ad (172.10.71.7)

2016-10-19 02:30:41,378 [Thread-13] [8a0876f2-0d96-406f-9381-596657905d4a] DEBUG CQSLongPollSender$LongPollSenderThread - event=longpoll_notification_sent endpoint=172.10.71.7:5555 queue_arn=arn:cmb:cqs:csv:422904998957:fe-b70g6_3000

But logs in cmb-6a2ad do not show anything until the timeout.

2016-10-19 02:30:46,975 [qtp1166726978-74] [561cc829-15c5-4e16-98d5-29ee17e9f0c6] DEBUG CMBControllerServlet - event=on_timeout queue_url=http://cmb:6059/422904998957/fe-b70g6_3000

The telnet 172.10.71.7 5555 between two containers is working.

What else can be wrong in our configuration that cmb-6a2ad did not receive longpoll_notification_sent ?

In properties we have

cmb.cqs.longpoll.enable=true
cmb.cqs.longpoll.port=5555

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant