Navigation Menu

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

Unable to initialize WebAsyncTask with executorName [SPR-12457] #17062

Closed
spring-projects-issues opened this issue Nov 20, 2014 · 1 comment
Closed
Assignees
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) status: backported An issue that has been backported to maintenance branches type: bug A general bug
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

Chris Chua opened SPR-12457 and commented

Looks like a typo in:

this(timeout, null, executorName, callable);
Assert.notNull(executor, "Executor name must not be null");

The assertion checks executor rather than executorName and always throws because executor is always null when using this particular constructor.

I've created a pull request on #698 . But perhaps this should be checking Assert.notEmpty ? I can make that change in the PR as well.


Affects: 3.2.9, 3.2.12

Referenced from: commits 8854c33, aadb93f, f6e1856

Backported to: 4.0.9, 3.2.13

@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

Fixed through a general revision of WebAsyncTask, rearranging its constructor interdependencies.

Juergen

@spring-projects-issues spring-projects-issues added type: bug A general bug status: backported An issue that has been backported to maintenance branches in: web Issues in web modules (web, webmvc, webflux, websocket) labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 4.1.3 milestone Jan 11, 2019
This was referenced Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) status: backported An issue that has been backported to maintenance branches type: bug A general bug
Projects
None yet
Development

No branches or pull requests

2 participants