spring-projects / spring-projects/spring-data-mongodb

DefaultDbRefResolver swallows exceptions [DATAMONGO-1111]

Open
#2,028 0 comments 0 reactions 1 assignee View on GitHub

@odrotbohm is already working on this.

Since Dec 30, 2020.

in: core type: bug
Dominant language
Java
Stars
1.7k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Description

Pablo Díaz-López opened DATAMONGO-1111 and commented

While doing some caching at DBRef resolve (workaound for DATAMONGO-1071), we found that in MongoExceptionTranslator is swallowing the stacktrace of an exception we throw.. In fact it also swallows the exception if for example the proxy of a DBRef lazy field cannot be instantiated, which will throw a MappingInstantiationException.

As I read from javadoc MongoExceptionTranslator should work this way, the problem seems to be at DefaultDbRefResolver.resolve(), because it sets the translatedException as cause which can be null if not translated.


Affects: 1.6.1 (Evans SR1)

1 votes, 2 watchers

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.