[Bug] Thread.stacksize is ignored by wisp

[oraluben]

Description Wisp provides thread-like semantics, which can be blocked on ObjectMonitor, Socket IO and so on. But it is not compatible with the semantics of Thread.stacksize, but directly uses the global default value (-Dcom.alibaba.wisp.stacksize, 512K by default). Ref: alibaba/dragonwell8#240

Steps to Reproduce Steps to reproduce the behavior:

1. Save below snippet '...'
2. Compile it with javac '....'
3. Execute with VM options '....'
4. See error

Expected behavior A clear and concise description of what you expected to happen.

JDK version The output of java -version command

Execution environment

• OS and version:
• CPU model:
• Number of CPU cores:
• Size of physical memory:
• Inside Linux container?
  • Linux container name (docker, pouch, etc):
  • Linux container version:

[oraluben]

Fixed in e5b0152a3331c1cb1ff43e52e9eeaff2b5465fce.