Details
-
New Feature
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Not a Bug
-
1.0.5
-
None
Description
Some of our APIs issue log that look like below example. messagequeue is the api code that is reporting the error... But it would be better if the calling process to that api was show in the log instead of the api name itself... easy to find out where the issue is coming from
Dec 5 15:40:47 ip-172-30-0-40 messagequeue[19253]: 47.294400 |0|0|0| W 31 CAL0071: InetStreamSocket::read: EOF during readToMagic: socket read error: Success; InetStreamSocket: sd: 11 inet: 172.30.0.129 port: 8630; Will retry.