blocks|key|304110|text|你考虑过Apache共用池吗？对于这种情况，它应该足够好。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|304111|entityMap|0|LINK|mutability|MUTABLE|url|http://commons.apache.org/pool/^0|4|9|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Have you considered <a href="http://commons.apache.org/pool/" rel="nofollow">Apache Commons Pool</a>? It should be good enough for this scenario.

blocks|key|384183|text|公地池和公地Exec结合怎么样？|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|384184|entityMap|0|LINK|mutability|MUTABLE|url|http://commons.apache.org/pool/|1|http://commons.apache.org/exec/^0|0|3|0|4|6|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

How about <a href="http://commons.apache.org/pool/" rel="nofollow">Commons Pool</a> combined with <a href="http://commons.apache.org/exec/" rel="nofollow">Commons Exec</a> ?

blocks|key|383665|text|外部进程的启动成本很高，而不是创建Java+Process。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|383666|如果您的exe正在用协议实现某种服务器进行通信，您只需启动该协议并使用该协议即可。但这样的话这个问题就不会出现了。|383667|如果它是一个简单的工具，例如处理一个文件的东西，您需要每次启动它，并依赖于(或调整)操作系统的/文件系统的缓存机制。没有办法暂停或重用它。|383668|entityMap^0|M|7|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|P|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|K|$]]

It is the starting of the external process that is expensive, not the creation of the Java object <code>Process</code>. 

If your exe is implementing a server of some kind with a protocol to communicate you would just start it and use that protocol. But then this question would not have arosen.

If it is a simple tool, e.g. something that processes a file, you need to start it each time and rely (or tweak) on the operating system's / file system's cache mechanisms. There is no way to pause or reuse it.

blocks|key|304182|text|由于您在命令行上传输参数，并且执行的子进程不能回收，也不能在内存中保持持久性，所以您的请求似乎不太有用--您可以保存的唯一东西是创建进程框架，但只能在一定程度上保存。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|304183|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Since you transfer the parameters on the command line, and the executed subprocess cannot be recycled, nor stays persistent in memory, your request does not appear very useful - the only thing you can save is the creation of the process frame, but only to a certain degree.

blocks|key|383700|text|这取决于some.exe是否支持这一点。例如，命令ls+(或dir)执行其操作并停止。没有办法告诉它“再做一次”-你需要一种方式，与进程和进程必须有一些接口(通常是stdio)，您可以使用它远程控制。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|383701|如果外部进程无法执行，则必须在每个请求中创建一个新进程，或者必须在其他地方运行该进程，并将结果保存在缓存中一段时间，因此几个用户请求不必运行该进程就可以获得相同的数据。|383702|因此，如果每个用户和每分钟收到100个请求，并且数据有一分钟的时间是可以的，那么您可以每分钟运行一次进程，并重用旧的结果。|383703|entityMap^0|4|8|P|2|U|3|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|K|$]]

That depends on whether <code>some.exe</code> supports this. For example, the command <code>ls</code> (or <code>dir</code>) does its thing and stops. There is no way to tell it "do it again" - you need a way to communicate with the process and the process must have some interface (usually stdio) which you can use to remote control it.

If your external process can't do it, then you must create a new process per request or you must run the process somewhere else and keep the results in a cache for some time, so several user requests get the same data without you having to run the process.

So if you get 100 requests per user and minute and it's okay for the data to be one minute old, then you could run the process once per minute and reuse the old results.

I understand the following is the typical code to launch an exe from java

<pre><code>Runtime rt = Runtime.getRuntime();
Process proc = rt.exec("some.exe"); 
</code></pre>

or with parameter 

<pre><code>Process process = new ProcessBuilder("some.exe","param1","param2").start();
</code></pre>

I have a web application which wraps an exe and users can execute these on request. As I understand the above two approaches will always create a new process on every request. I want to avoid this. 

Is there way, wherein I keep a pool of reusable loaded instances and use them in the typical concurrent scenario. I want avoid a situation wherein each user request launches a new process.

Launching an exe from java

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我理解以下是从java启动exe的典型代码Runtime rt = Runtime.getRuntime();Process proc = rt.exec("some.exe"); 或具有参数Process process = new ProcessBuilder("some.exe","param1","param2...

问从java启动exe
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问从java启动exeEN