Hello Ignite users,
I wonder how contextual logging could be realised with Ignite services.
Imagine service A provides a HTTP REST API and consumes service B. Now when
a HTTP request is incoming thru service A I'd like to know the ID of the
request/session that has caused a log line at service B.
Done, any idea when this bug might be resolved? It's kind of a deal breaker
for our microservice architecture.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Throwing-and-catching-user-exceptions-in-Ignite-Services-tp9143p9183.html
Sent from the Apache Ignite Us
I asked this question on SO roughly 2 weeks ago:
http://stackoverflow.com/questions/40545051/catch-user-exception-in-remote-service-at-caller-level
My intention is to deploy Service A and Service B, then call a method of
Service B inside Service A utilizing the IgniteServices serviceProxy. Each
se
