Handling try-with-resources issue in Sonarqube if resource shouldn't be closed immediately

Question

I have a method that initializes a Session object (Cassandra Session, which according to best practices should be shared across application threads as it is quite expensive to initialize one) and returns it back to the caller. Sonarqube suggests closing my Session object in finally block or by using try-with-resources construct.

It doesn't make sense to do it my case as a session should be closed only when the application is shutting down.

Such check makes sense only if my resource should be closed immediately after usage, like connection, file, etc.

How do I get rid of that type of error, please advise.

Does this help: stackoverflow.com/questions/39109228/… ? Alternatively, couldn't you just turn into the SQ user interface and ignore that warning there for that one file? — GhostCat
– GhostCat, Commented May 25, 2018 at 19:41
Yes, I guess I can always ignore a rule, I was thinking maybe there is a better way to handle such case. — Ihor M.
– Ihor M., Commented May 25, 2018 at 19:44

Ihor M. · Accepted Answer · 2018-05-26 17:24:13Z

0

@SuppressWarnings("squid:S2095")

This is how I ended up handling that error.

answered May 26, 2018 at 17:24

Ihor M.

3,2187 gold badges54 silver badges87 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Handling try-with-resources issue in Sonarqube if resource shouldn't be closed immediately

1 Answer 1

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Linked

Related