通过 RMI 保持相同的线程名称
进行 RMI 调用时是否有任何简洁的方法来保持相同的线程名称？目前，如果我有一个进行 RMI 调用的命名线程，则在 RMI 调用的服务器端，Thread.currentThread().getName() 返回一些不明确的内容，例如“RMI TCP Connection” (4)-10.0.0.2"。
当然，我可以向所有 RMI 方法添加一个参数 String CallingThreadName 并使每个 RMI 方法实现的第一行 Thread.currentThread().setName(callingThreadName) >，但这并不是最好的方法。有没有办法至少获得通过 RMI 连接传输的线程名称背后的一些含义？
Is there any tidy way to keep the same thread name when making an RMI call? At the moment if I have a named thread that makes an RMI call, on the server side of the RMI call, Thread.currentThread().getName() returns something un-illuminating like "RMI TCP Connection(4)-10.0.0.2".
Of course, I could go and add to all my RMI methods a parameter String callingThreadName and make the first line of each RMI method implementation Thread.currentThread().setName(callingThreadName), but that's hardly the neatest way of doing so. Is there any way to get at least some of the meaning behind the thread name transferred over the RMI connection?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您要做的就是在查看日志文件时将不同进程中的操作关联起来。执行此操作的最佳方法是将唯一的 transaction_id 添加到仅用于此目的的 RPC。这使您可以跟踪通过系统的流量。
What you are tryig to do is correlate the actions in different processes while looking at log files. The best way to do this is to add a unique transaction_id to your RPC that is used just for that purpose. This allows you to track the flow through the system.
Java RMI 规范明确指出，不保证客户端调用如何映射到服务器线程。所以你不能对此做出任何假设。具体来说，您不应该尝试使用线程标识符来关联客户端。
The Java RMI Specification specifically states that there are no guarantees about how client calls are mapped to server threads. So you can make no assumptions about it. Specifically, you shouldn't be trying to use a thread identifier to correlate clients.