While deploying mule application in Anypoint studio getting below error :
org.mule.runtime.core.api.retry.policy.ConnectNotifier: Failed to connect/reconnect:
Message Source Reconnection. Root Exception was: An error occurred while executing the operation:
AUTHORIZE AGAINST BROKER. Cause: Can not login into broker - 429 - Too Many Requests ({
"status" : "failure",
"statusMessage" : "Rate limit exceeded"
}).. Type: class com.mulesoft.mq.restclient.api.exception.RestException
On queue in Anypoint platform at MQ option, we have used below configurations.
Message TTL - Default 7 Days so we kept as is
Default Acknowledgement Timeout - Default 2 Minutes so we kept as is
This issue is related to the fact that there maybe a client app which is using wrong authentification. Trying to authenticate several times with a wrong client id/ client secret blocks all request for the organisation for AMQ.
It usually means that there are too many concurrent operations from clients using the same credentials. It could be one application or more than one.
Just in case also ensure that the application is using the last release of the Anypoint MQ connector.
Related
I am frequently getting the below mentioned errors, the dll version used in the project is - 1.0.488.0
System.TimeoutException: Timeout performing GET
StackExchange.Redis.RedisConnectionException: No connection is available to service this operation: GET
No connection is available to service this operation: EXISTS
Can anyone help me out in figuring what the issue can be?
Have also created an issue on StackExchange's Github repo for the same
Issue created on Github for the same
It looks like your connection broke. And when it did, any commands already sent to Redis would have timed out on the client application, even though they could have executed on the server. If you upgrade to a later version of the StackExchange.Redis client, you will get richer diagnostics information about what the state of the threadpool, CPU etc was on the client application side.
I am unable to remove the rabbitmq service from list of services in Bluemix. Every time i request to delete the service, i get the following error message:
The service broker reported an error during deprovisioning: Service
broker error: instance_id cf518624-b238-4fa1-8e9e-f7ca2897687e not
found Oct 20, 2015, 1:04:33 PM
There were some problems with third party services giving that error message when creating or deleting a service. The issue is currently under investigation, even if some services now are working. Please try again and if the issue is still present you could open a ticket from the portal or sending an e-mail to support#bluemix.net.
To check the status of the platform please refer to Bluemix Support - Status. As you can see in the tab on the right "Updates" there is an open incident on this problem (Error provisioning and deprovisioning Third Party Services).
I am trying to configure wso2 esb with rabbitmq. I've read this article.Whenever i sent a message from the sender , It reached out the queue named Q1 as well as ESB console. But it doesn't reach queue named Q2.
Does anybody has a solution ?
thanks
According to the provided end-point all messages should publish to the queue test via test exchange. You can introduce rabbitmq.queue.routing.key property to your endpoint and bind your test queue to test exchange using that route key.
If you have already configured axis2.xml/proxy service correctly according to the documentation[1], there can be a configuration issue at your RabbitMQ server side.You can confirm that writing a simple java client according to the article[2] or refer this tutorial[2].
Or you may remove test-queue/test-exchange from RabbitMQ server and try your endpoint.
[1]. http://docs.wso2.org/display/ESB460/RabbitMQ+AMQP+Transport
[2]. http://www.rabbitmq.com/tutorials/tutorial-one-java.html
I have an iOS client that connects to several ActiveMQ topics and queues via STOMP protocol. When I connect to the server, I send the following message:
2012-10-30 10:19:29,757 [MQ NIO Worker 2] TRACE StompIO
CONNECT
passcode:*****
login:system
2012-10-30 10:19:29,758 [MQ NIO Worker 2] DEBUG ProtocolConverter
2012-10-30 10:19:29,775 [MQ NIO Worker 2] TRACE StompIO
CONNECTED
heart-beat:0,0
session:ID:mbp.local-0123456789
server:ActiveMQ/5.6.0
version:1.0
And then, I subscribe to several topics using the following message:
2012-10-30 10:19:31,028 [MQ NIO Worker 2] TRACE StompIO
SUBSCRIBE
activemq.subscriptionName:user#mail.com-/topic/SPOT.SPOTCODE
activemq.prefetchSize:1
activemq.dispatchAsync:true
destination:/topic/SPOT.SPOTCODE
client-id:1234
activemq.retroactive:true
I'm facing two problems with the ActiveMQ server. Each time I connect, the Number of Consumers column in the web interface gets incremented, so I have just one real consumer but the count is around 50 consumers. But the most problematic issue is that when I plug another iOS device into my laptop to test the messaging environment, i get the following error when connecting to ActiveMQ:
WARN | Async error occurred: javax.jms.JMSException: Durable consumer is in use for client: ID:mbp.local-0123456789 and subscriptionName: user#mail.com-/topic/SPOT.SPOTCODE
This seems to be that disconnecting from ActiveMQ via STOMP is not working propertly, because this logging attempt is made when the other device is not running the app. I've tried the following things in order to solve the issue:
Always logoff when attempting to subscribe to the topics.
Subscribe
I'm currently using v5.6.0 executing the server on my laptop.
IF you read the STOMP page on the ActiveMQ site you will notice that client-id and activemq-subscriptionName must match in order to use STOMP durable subscribers. These value should be different for each of you client's otherwise you will see the same errors because of the name clashes.
This is a problem which has had me baffled for weeks now on a client's Live environment.
The WCF service is hosted on Windows Server 2003, and has both HTTP and MSMQ endpoints.
When placing the service in the test environment, the service cleanly starts and stops, and messages are passed without problems. However on the Live environment, the service starts fine, but does not exit cleanly.
When attempting to stop the service, the machine takes a long time to respond and eventually displays an error saying that the service could not be stopped. Inspecting the error on the event log, it says that it was unable to write to the MSMQ queue (access denied), however, the service is able read and remove messages from the queue. If one then refreshes the service manager, the service is in fact stopped.
The MSMQ queue is hosted on a different physical machine, and we have been unable to reproduce the error on the test environment.
We are not sure if it is related or not, but the service will also occasionally stop pulling messages from the queue. This has been solved by restarting the service. Again, we have not been able to reproduce the error.
Recently we experienced another error with the HTTP based client where upon midnight one night, the service suddenly started rejecting connections with the following exception:
The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'Negotiate,NTLM'. ---> System.Net.WebException: The remote server returned an error: (401) Unauthorized.
Even more curious, is that simply restarting the service seems to correct the problem.
If anyone has seen anything like this before or has any comments, it would be much appreciated!
Speaking to a colleague, apparently setting the ServiceModelEx throttling options all to "1" help with the lock ups on MSMQ based WCF services.