以编程方式检查 ThreadStackSize？

发布于 2025-01-07 11:15:21 字数 943 浏览 3 评论 0原文

有没有办法以编程方式检查 ThreadStackSize？

我在 Jboss 7 的 jboss.conf 文件中有以下代码。

 # Java Additional Parameters
wrapper.java.additional.1=-XX:MaxPermSize=512m
wrapper.java.additional.2=-Dorg.jboss.resolver.warning=true
wrapper.java.additional.3=-Dsun.rmi.dgc.client.gcInterval=3600000
wrapper.java.additional.4=-Dsun.rmi.dgc.server.gcInterval=3600000
wrapper.java.additional.5=-Djboss.modules.system.pkgs=org.jboss.byteman
wrapper.java.additional.6=-Dorg.tanukisoftware.wrapper.WrapperManager.mbean=false
wrapper.java.additional.7=-Dlogging.configuration=file:%JBOSS_HOME%/standalone/configuration/logging.properties
wrapper.java.additional.8=-Djava.util.logging.manager=org.jboss.logmanager.LogManager
wrapper.java.additional.9=-Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl

**wrapper.java.additional.10=-XX:ThreadStackSize=256k**

有没有办法确认 ThreadStackSize 是否已以编程方式设置为 256k？

原文

Is there a way to check the ThreadStackSize programmatically?

I have the following code in Jboss 7's jboss.conf file.

 # Java Additional Parameters
wrapper.java.additional.1=-XX:MaxPermSize=512m
wrapper.java.additional.2=-Dorg.jboss.resolver.warning=true
wrapper.java.additional.3=-Dsun.rmi.dgc.client.gcInterval=3600000
wrapper.java.additional.4=-Dsun.rmi.dgc.server.gcInterval=3600000
wrapper.java.additional.5=-Djboss.modules.system.pkgs=org.jboss.byteman
wrapper.java.additional.6=-Dorg.tanukisoftware.wrapper.WrapperManager.mbean=false
wrapper.java.additional.7=-Dlogging.configuration=file:%JBOSS_HOME%/standalone/configuration/logging.properties
wrapper.java.additional.8=-Djava.util.logging.manager=org.jboss.logmanager.LogManager
wrapper.java.additional.9=-Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl

**wrapper.java.additional.10=-XX:ThreadStackSize=256k**

Is there a way to confirm if the ThreadStackSize has been set to 256k programmatically?

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

我们只是彼此的过ke 2025-01-14 11:15:21

问题在于 -XX 参数是特定于实现的，因此核心 Java 类无法直接将这些信息作为简单的 getMaxStackSize() 公开。

java.lang.management 包中有很多有用的指标，例如 MemoryPoolMXBean。我还没有尝试特别寻找堆栈大小，但如果您深入挖掘，您可能会找到它。

回复收藏 0 原文

半寸时光 2025-01-14 11:15:21

请阅读此处：在运行时更新 java 线程的堆栈大小

你也许可以尝试抓住 stackSize变量，看看这是否会给您带来任何有用的东西。保持警惕：

/*
 * The requested stack size for this thread, or 0 if the creator did
 * not specify a stack size.  It is up to the VM to do whatever it
 * likes with this number; some VMs will ignore it.
 */

Have a read here: Update a java thread's stack size at runtime

You could probably try to grab the stackSize variable using reflection and see if that gives you anything useful. Be wary:

/*
 * The requested stack size for this thread, or 0 if the creator did
 * not specify a stack size.  It is up to the VM to do whatever it
 * likes with this number; some VMs will ignore it.
 */

回复收藏 0 原文

~没有更多了~