Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

GrpcExceptionHandler doesn't catch an exception in SpringBootTest

See original GitHub issue

I’m trying to test the GrpcAdvice and GrpcExceptionHandler with the SpringBootTest. I have created the GrpcCoreExceptionHandler

@GrpcAdvice
public class GrpcCoreExceptionHandler
{

	@GrpcExceptionHandler(IllegalArgumentException.class)
	public StatusException handleResourceNotFoundException(IllegalArgumentException e) {
		Status status = Status.INVALID_ARGUMENT.withDescription(e.getMessage()).withCause(e);
		Metadata metadata = new Metadata();
		return status.asException(metadata);
	}
}

and have an integration test which invokes one of the methods in our gRPC PersonService Here is the SpringBootTest setup:

@SpringBootTest(properties =
{
		"grpc.server.inProcessName=PersonServiceIntegrationTest", "grpc.server.port=-1"
})
@RunWith(SpringRunner.class)
@Transactional("spTransactionManager")
public class PersonServiceIntegrationTest
{
	@Autowired
	private PersonService subject;

	@SpyBean
	private PersonDao personDao;

	@Test
	public void getPerson_whenExceptionBeenThrown_returnsErrorResponse()
	{
		doThrow(IllegalArgumentException.class).when(personDao).getPerson(any(), any());
		StreamRecorder<PersonProto> responseObserver = StreamRecorder.create();
		UserPersonIdProto userPersonId = UserPersonIdProto.newBuilder().build();

		subject.getPerson(userPersonId, responseObserver);

		Throwable error = responseObserver.getError();
		assertNotNull(error);
	}

}

In current setup the ExceptionHandler is not invoking and Exception is propagating farther to a spring RunAfterTestExecutionCallbacks layer.

But if i start the application locally and make a call with the Postman or any other gRPC client i can see that exception will be handled with the GrpcExceptionHandler. So, it looks like there is some conflict with between the SpringBootTest configuration and GrpcAdvice initilization.