Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lettuce infinite print log - Unexpected exception during request: java.lang.NullPointerException #25857

Closed
wbzj1110 opened this issue Apr 1, 2021 · 5 comments
Labels
for: external-project For an external project and not something we can fix status: invalid An issue that we don't feel is valid

Comments

@wbzj1110
Copy link

wbzj1110 commented Apr 1, 2021

background

spring-boot 2.3.9 RELEASE
default lettuce 5.3.6 RELEASE
redis cluster mode
image

some bean use @PostConstruct and method contain redis action ,This is the key to reproducing the problem。

@Service
@Slf4j
public class TestA   {


    @PostConstruct
    public void init(){
		//redis action
    }

}

expression

log infinite print Unexpected exception during request: java.lang.NullPointerException,as follows:
image

print very quickly。

reasons

lettuce 5.3.6 RELEASE has a bug about use trace,the key code ,as follows:
image

when use full link tracking related modules, lettuce does not first determine whether it is empty, and this is the reason。

solutions

Either one will do

1)、pom add lettuce new version
lettuce fix it later,but in it new version,like 6.1.0.RELEASE,the code as follows:
https://github.com/lettuce-io/lettuce-core/blob/main/src/main/java/io/lettuce/core/protocol/CommandHandler.java#L460

image

2)、user code change
use @order or implement ApplicationRunner rather than use @PostConstruct

suggest

spring-boot 2.3.9 release may use new version of lettuce,at least not lettuce 5.3.6 RELEASE 。

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Apr 1, 2021
@wilkinsona
Copy link
Member

Thanks for letting us know. Unfortunately, Spring Boot 2.3.x is already using the latest release in the Lettuce 5.3.x line and we cannot upgrade to 6.x in a 5.3.x maintenance release. Spring Boot 2.4.x has upgraded to Lettuce 6.0.x and Spring Boot 2.5.x will use Lettuce 6.1.x so I don't think there's anything more that we can do here at this time. If there is a Lettuce 5.3.7 release in the future, then we will upgrade in due course.

You may want to make sure that the Lettuce team are aware of the problem in 5.3.x by searching their issue tracker and opening an issue if the problem has not already been reported. If you find an existing issue or open a new one, please comment here with a link to it so that we can follow along.

@wilkinsona wilkinsona added for: external-project For an external project and not something we can fix status: invalid An issue that we don't feel is valid and removed status: waiting-for-triage An issue we've not yet triaged labels Apr 1, 2021
@wbzj1110
Copy link
Author

wbzj1110 commented Apr 1, 2021

Thanks for letting us know. Unfortunately, Spring Boot 2.3.x is already using the latest release in the Lettuce 5.3.x line and we cannot upgrade to 6.x in a 5.3.x maintenance release. Spring Boot 2.4.x has upgraded to Lettuce 6.0.x and Spring Boot 2.5.x will use Lettuce 6.1.x so I don't think there's anything more that we can do here at this time. If there is a Lettuce 5.3.7 release in the future, then we will upgrade in due course.

You may want to make sure that the Lettuce team are aware of the problem in 5.3.x by searching their issue tracker and opening an issue if the problem has not already been reported. If you find an existing issue or open a new one, please comment here with a link to it so that we can follow along.

redis/lettuce#1701 I will fix this issue,and after lettuce have new 5.3.X version。I will comment again 。thks。
After all, the latest spring-boot realse that adapts to spring-cloud is as follows:
spring-boot 2.3.9 RELEASE
spring-cloud Hoxton.SR10

wbzj1110 added a commit to wbzj1110/spring-boot that referenced this issue Apr 14, 2021
@wbzj1110

This comment has been minimized.

@snicoll

This comment has been minimized.

@wbzj1110

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: external-project For an external project and not something we can fix status: invalid An issue that we don't feel is valid
Projects
None yet
Development

No branches or pull requests

4 participants