HI Kedar, The queue full is resultant of dmaap publish failure for prolonged time. Once the DMAAP errors are resolved, collector will publish the queued events automatically (provided the DMAAP configuration was set correct during startup).
Also based on the URL posted - <dmaaphost> should be replaced with actual DMAAP Host IP (if you are using standalone setup, this IP should be provided during VES Container startup). Some of the details are documented here - https://wiki.onap.org/pages/viewpage.action?pageId=16002279#DCAEmSDeployment(Standaloneinstantiation)-VESCollector Thanks, Vijay From: [email protected] [mailto:[email protected]] On Behalf Of Kedar Ambekar Sent: Monday, December 11, 2017 11:55 PM To: [email protected] Subject: [onap-discuss] Queue full error while trying to submit VES event Hi Team, On DCAE collector, if I try to submit a VES event, I get "queue full" error. What could be wrong ? curl -i -X POST -d "@dataFile.json" --header "Content-Type:application/json" -k http://localhost:8080/eventListener/v5 HTTP/1.1 503 Service Unavailable Server: Apache-Coyote/1.1 X-Rathravane: ~ software is craft ~ Content-Type: application/json;charset=ISO-8859-1 Content-Length: 74 Date: Fri, 08 Dec 2017 14:09:59 GMT Connection: close {"requestError":{"GeneralException":{"Status":503,"Error":"Queue full"}}} http://<dmaaphost>:3904/events/unauthenticated.SEC_MEASUREMENT_OUTPUT<https://urldefense.proofpoint.com/v2/url?u=http-3A__-253cdmaaphost-253e-3A3904_events_unauthenticated.SEC-5FMEASUREMENT-5FOUTPUT&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=6WYcUG7NY-ZxfqWx5MmzVQ&m=lQnKt9Y34WvzGPRvZPW3MH0uIhzyMINNMdrN_3DVt-M&s=uqn_R5-KyrXSQi0QZC_8e3jlkTDiE2tdt0dUciY1vwI&e=> also doesn't work. I see some errors in dmaap and kafka container logs on message router VM. If I restart them, will subscriptions remain intact ? ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_Disclaimer.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=6WYcUG7NY-ZxfqWx5MmzVQ&m=lQnKt9Y34WvzGPRvZPW3MH0uIhzyMINNMdrN_3DVt-M&s=JlY3L-X_227kYpcyOe_vwK4-J9Cj0q0w9IaSW-SR7cY&e=> externally http://tim.techmahindra.com/tim/disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__tim.techmahindra.com_tim_disclaimer.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=6WYcUG7NY-ZxfqWx5MmzVQ&m=lQnKt9Y34WvzGPRvZPW3MH0uIhzyMINNMdrN_3DVt-M&s=nCBtcyKItzqnk_zO4KglyDUwKVVQ_vtm2ZOU9XmTwRU&e=> internally within TechMahindra. ============================================================================================================================
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
