I have set up a custom alert in Anypoint Cloudhub to raise the alert if the application encounters a mongodb error. I am seeing the error but am not receiving an email.
I am down as the recipient and have the alert turned on but I cannot see an alert (which I think should be an email).
I'm using Mule 3.8.3 in Runtime Manager.
Alert:
Error in log:
********************************************************************************
18:27:45.629 02/27/2017 Worker-0 [test].HTTP_Listener_Configuration.worker.01 ERROR
********************************************************************************
Message : Failed to invoke findOneDocument.
Element : /getRecord/processors/4 # test
--------------------------------------------------------------------------------
Exception stack is:
Failed to invoke findOneDocument. (org.mule.api.MessagingException)
com.mongodb.connection.BaseCluster.createTimeoutException(BaseCluster.java:369)
Are you using the CloudHub connector to generate the custom alert notification? Are you sure the alert contains com.mongodb? Also, are you sure you set a valid email address for the notification? Are you also seeing the Alert in Runtime Manager? Make sure you set a Anypoint Platform user as the alert recipient and that that user has permission to view alerts from this business-group/environment.
Related
I started using Anypoint MQ Subscribe with Max Redelivery Countset to 2.
Application should throw ANYPOINT-MQ:RETRY_EXHAUSTED exception after 2 failed deliveries, but the message was returned back to main queue and picked up again in the next batch.
I am trying to put the messages in DLQ manually after 2 failed deliveries using Try scope.
Any idea, how to put the messages in DLQ manually?
Errors related to anypoint-mq:RETRY_EXHAUSTED or HTTP: RETRY_EXHAUSTED, always occurs when it failed to connect to any point mq or http request to any other service.
When you set retry connection strategy in connector like retry 2 time then connector tries to connect 2 times and after that still no connection then we will get retry exhausted error
To catch that error and see message to DLQ, do categorisation of error in on error propagate use type ANYPOINT-MQ:RETRY_EXHAUSTED Or HTTP:RETRY_EXHAUSTED based on which connector you are using.
Then it will catch that error and then inside on error propagate use any logic like send message to file or dlq whatever but there also if it fails to send to file then put a logger with proper details to track the message without losing it
Thanks
I am getting the Java IO Exception while connecting the Webmethods Designer 9.12.
Connection failed for localhost:5555 (java.io.IOException)
javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
I can able to access the IS admin page and tried looking error in the server log
enter image description here
but didnot get anything in particular. Below is the error screenshot:enter image description here
What are your settings? Should be without SSL, can you check?
Are you able to open http://localhost:5555 in browser?
I currently registered my Quecklink GV500 to cumulocity and I'm able to receive some events and measurements.
But when I try to send command to my Quecklink GV500 registered in Cumulocity but I always hava a FAILED response. For example, I tried to send this command (which is fully supported by the GV500) from SHELL tab: AT+GTTMA=gv500,+,1,0,0,,,,,,FFFF$
And as result I got:
Failure reason: Command currently not supported
I also tried to get the agent logs by using "Log file request" in the "Log" tab of my Device and as result I got:
Failure reason: Cannot build command. Search parameters only allow the
following characters [a-zA-Z0-9_]
Is it normal?
When I look the general information in "Info" tab I have:
Send connection: online
Push connection: inactive
Is it normal that Push connection is marked as inactive?
The tracker-agent in it current state does not use a push connection for receiving operations but does a polling of the operations. Therefore the push connection is always shown as inactive.
If you receive "Failure reason: Command currently not supported" it is an error from the agent not the device. The agent seems not to support shell operations for Queclink.
As for the error on the log file request it seems that there was an unsupported character in the search parameter. Maybe you can share what you entered for the parameters in the UI
Thanks for your answer. For the log file request I let blank value in the search input field. If I try to enter "gl200", I get the following error: Command currently not supported.
So to resume can you confirm that Quecklink devices can't be managed from Cumulocity for the moment? It's supported for which device?
hi trying configure slack notification in test.yaml file , getting the below error ERROR:root:Could not load rule /opt/rules/test.yaml: Error initiating alert ['slack', {'slack_webhook_url': 'https://hooks.slack.com/servichttps://hooks.slack.com/services/abcd'}]: Could not import module slack_webhook_url: need more than 1 value to unpack
alert:
"slack"
slack_webhook_url: "https://hooks.slack.com/servichttps://hooks.slack.com/services/abcd"
is this the correct way to define the slack alert
Make sure you follow the spaces correctly and you are providing all the required arguments:
alert:
- "slack"
slack:
slack_webhook_url: "YOUR URL"
It should work.
I have a receive port with a WCF-CustomIsolated receive location.
On receive port I checked "Enable routing for failed messages".
In pipeline settings I have set ValidateDocument to true.
When a client sends me an incorrect schema, it receives a validation error (that happened in pipeline) and it's OK.
But it's not routed as a fault message to message box.
Could you help me why does it happen?
Why "routing for failed messages" does not work in this case? And in what cases it should work?
Thank you!
On the Receive Location, go the Transport Properties, Messages, Error Handling, and check Suspend request message on failure.
Even though it says "Suspend" checking this in combination with the Routing for Failed Message on the Receive Port will actually create a FailedMessage that you are after. (If Routing for Failed Message isn't enabled it will suspend).
This applies to all the WCF adapters, not just the CustomIsolated one.
You need to subscribe to the error message. You could use a send port or orchestration with a filter set to the receive port, message type and/or message error.