-
Enhancement
-
Resolution: Fixed
-
P4
-
18
-
b07
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8286736 | 17.0.5-oracle | Harold Seigel | P4 | Resolved | Fixed | b01 |
| JDK-8286629 | 17.0.4 | Martin Doerr | P4 | Resolved | Fixed | b03 |
| JDK-8290312 | 11.0.17-oracle | Harold Seigel | P4 | Resolved | Fixed | b03 |
| JDK-8286753 | 11.0.16 | Martin Doerr | P4 | Resolved | Fixed | b03 |
The current warning message:
[11.028s][warning][os,thread] Failed to start thread - pthread_create failed (EAGAIN) for attributes: stacksize: 2048k, guardsize: 0k, detached.
is quite unhelpful and does not give an idea which thread failed to be created.
It would be a useful addition to show if this is a GC thread, a compiler thread, an application thread, etc.
> One more thing, do you think it would be reasonable to retry (e.g. 1-2 times) pthread_create() if it returns EAGAIN?
That is not unreasonable, but may not help depending on exactly why the failure is occurring. If we have hit the ulimit process/thread limit for example, then it won't self-correct unless a thread/process has terminated since the first call. So in a tight loop it may just fail continually.
- backported by
-
JDK-8286629 Improvements related to: Failed to start thread - pthread_create failed (EAGAIN)
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8268605 [warning][os,thread] Failed to start thread - pthread_create failed (EAGAIN) for attributes
-
- Closed
-
-
-
- Resolved
-
- links to
-
Commit
openjdk/jdk11u-dev/2013819b
-
Commit
openjdk/jdk17u-dev/296dc785
-
Commit
openjdk/jdk/e35005d5
-
Review
openjdk/jdk11u-dev/1074
-
Review
openjdk/jdk17u-dev/390
-
Review
openjdk/jdk/4648
-
Review
openjdk/jdk/4788