I am using Tracer for logging in and out messages. When i enabled logging out messages, it is logging successfully but in my Rest Client I am not getting the response.Can anybody help me to fix this.
Related
We are facing this strange PubSub behaviour when our MDM server is idle over a period of time. We create a topic and a subscription during the server start-up, and our server is programmed to pull the subscription messages from the topic asynchronously using the Receive() function. We are creating the PubSub client using the service account credentials.
What we have observed is that, when we run our MDM server on a MAC machine, we see this RPC error intermittently in our server logs:
{
"error": "rpc error: code = Unauthenticated desc = Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.",
"file": "/opt/bigfix/src/bigfix/mdm-android/internal/pubsub/subscriber.go:50",
"func": "bigfix/mdm-android/internal/pubsub.GetPubSubMessages",
"level": "error",
"module": "mqpublisher",
"msg": "Error receiving Pub/Sub messages",
"time": "2022-03-03T04:50:25Z"
}
Note that this error is caught on the line subscription.Receive() in our code. And, any device enrollment messages post this RPC error, aren’t getting delivered to our PubSub client. When we try to pull the pending messages from the topic in Google console, we are able to see all the undelivered messages there. When we restart our server, PubSub connection is made afresh and all these pending commands are pushed to our PubSub client.
We tried to fix the issue in 2 ways:
The version of PubSub package that we were using was 1.6.1, and we tried to upgrade it to the latest version which is 1.18.0, but the problem still persists
Tried to wrap subscription.Receive() with a retry function so that it can keep retrying upon errors, but still the problem persists.
And no matter if we receive this RPC error or not, our MDM server is not able to pull any messages from the topic when it is idle over a period of time. This behaviour is seen only when our server runs on a MAC machine, and works fine in other operating systems.
Kindly guide us as to fix this issue.
Thanks,
Porkodi
I'm using apache camel xml based paho routes for the subscription, publication process. While online, everything works fine. But I'm not able to receive the offline message.
I have set the following.,
Constant Client ID
Clean Session is FALSE,
Both subscribed & published with QoS 2
With the standalone Program, it's getting all the offline messages. With the camel route it's not happening.
Finally, I was able to solve this one manually.
Camel PAHO Client is not populating the callback function before performing the broker connection. They are doing it only when the connection is made.
So, once the connection is success then the broker just sends all the offline messages. In this case, our client does not have callback handlers to handle these messages. So they are lost.
Other clients (IoThub Client) which uses the PAHO internally is doing it right by setting the callback and initiating the connection.
I have a Camel route which Consumes messages from a Queue and stores the message into a Database. Now I wanted to shut down running camel route manually in a graceful manner. I have a RestEndpoint to be triggered whenever I need to stop Camel route. This endpoint should stop the route. But if there is any in-flight message or transaction running during the shutdown it has to be completed successfully without consuming any new messages from from("") endpoint of camel route and shut down after completing inflight message or transaction. Can anyone help me how Can I code this?
Below are the few options to control/monitor camel routes
CamelContext API's
Control bus component
JMX API's
You can go through below two sites to get started
http://camel.apache.org/controlbus.html
https://dzone.com/articles/apache-camel-monitoring
shutdownRunningTask(ShutdownRunningTask.CompleteCurrentTaskOnly)
I see lots of exceptions[ClientAbortException: java.net.SocketException: Broken pipe] in
my catalina log while trying to send the response back but i am not able to tie this exception
to a particular request with a particular Inbound Message ID, Is there any way by which i can know, while sending
which response this exception is occuring in cxf ?
Try enabling SOAP logging. If you enable SOAP logging as follows, you will see SOAP requests and/or responses including HTTP headers. CXF also assigns a message ID for each request/response.
#WebService
#org.apache.cxf.annotations.Logging
public interface AssetServices {
....
}
I was trying to send emails to my client from my application after few sent mails all mails bounces back with a message saying "You have reached a limit for sending mail. Your message was not sent." And one more thing when i see my developer console gmail api it still showing 0% usage.what is this issue? is this a bug or something else?
There's an extra limit on sending because it's a vector for abuse--it doesn't show up in the developers console but it's the same as sending via SMTP or the web interface.
This seems to have a good overview:
http://www.labnol.org/internet/email/gmail-daily-limit-sending-bulk-email/2191/