堆栈内存溢出
  简体   繁体   English

Mule ESB：如何管理线程名称？

[英]Mule ESB : How the threads names are managed?

 原文  2014-06-30 08:14:26  4   1    java/ multithreading/ websphere/ mule

问题描述

below I posted an extraction of SystemOut.log from a websphere 7.0 with Mule ESB 3.4.0. 下面，我发布了使用Mule ESB 3.4.0从websphere 7.0中提取SystemOut.log的信息。 My Mule flow is a synchronous one. 我的M子流是同步的。 It consumes "Websphere MQ messages" and log the message "Message Consume" for each message and then do business stuff... 它使用“ Websphere MQ消息”，并为每条消息记录消息“ Message Consume”，然后进行业务工作...

My questions : 我的问题：

  • Clearly different threads shared the same name, why ? 显然，不同的线程共享相同的名称，为什么呢？

  • After a long period without message, Mule start to increment the thread name each 4 messages. 长时间不发送消息后，Mule开始每4条消息增加线程名称。 Thread leak or not ? 线程是否泄漏？

The log format is : 日志格式为： 

ThreadId [Date] [ThreadName] : Message

The ThreadId is from websphere and the ThreadName from log4j. ThreadId来自websphere，而ThreadName来自log4j。

The SystemOut.log : SystemOut.log： 

00000018 [25-06-2014 10:56:13] [DispatchThread: 1]: Message Consume
00000019 [25-06-2014 10:56:14] [DispatchThread: 1]: Message Consume
00000018 [25-06-2014 10:56:15] [DispatchThread: 1]: Message Consume
00000019 [25-06-2014 10:56:15] [DispatchThread: 1]: Message Consume
00000019 [25-06-2014 10:56:15] [DispatchThread: 1]: Message Consume
00000018 [25-06-2014 10:56:15] [DispatchThread: 1]: Message Consume
00000019 [25-06-2014 10:56:15] [DispatchThread: 1]: Message Consume
00000018 [25-06-2014 10:56:15] [DispatchThread: 1]: Message Consume
00000018 [25-06-2014 10:56:15] [DispatchThread: 1]: Message Consume
00000019 [25-06-2014 10:56:16] [DispatchThread: 1]: Message Consume
00000019 [25-06-2014 10:56:16] [DispatchThread: 1]: Message Consume
00000018 [25-06-2014 10:56:16] [DispatchThread: 1]: Message Consume
00000018 [25-06-2014 10:56:16] [DispatchThread: 1]: Message Consume
00000019 [25-06-2014 10:56:16] [DispatchThread: 1]: Message Consume
00000019 [25-06-2014 10:56:17] [DispatchThread: 1]: Message Consume
00000018 [25-06-2014 10:56:17] [DispatchThread: 1]: Message Consume
00000019 [25-06-2014 10:56:17] [DispatchThread: 1]: Message Consume
00000018 [25-06-2014 10:56:17] [DispatchThread: 1]: Message Consume
00000019 [25-06-2014 10:56:17] [DispatchThread: 1]: Message Consume
00000018 [25-06-2014 10:56:17] [DispatchThread: 1]: Message Consume
00000018 [25-06-2014 10:56:17] [DispatchThread: 1]: Message Consume
00000019 [25-06-2014 10:56:18] [DispatchThread: 1]: Message Consume
00000018 [25-06-2014 10:56:18] [DispatchThread: 1]: Message Consume
00000019 [25-06-2014 10:56:18] [DispatchThread: 1]: Message Consume
00000019 [25-06-2014 10:56:18] [DispatchThread: 1]: Message Consume
00000018 [25-06-2014 10:56:18] [DispatchThread: 1]: Message Consume
00000018 [25-06-2014 10:56:18] [DispatchThread: 1]: Message Consume
00000019 [25-06-2014 10:56:19] [DispatchThread: 1]: Message Consume
00000026 [25-06-2014 11:40:46] [DispatchThread: 2]: Message Consume
00000027 [25-06-2014 11:46:15] [DispatchThread: 2]: Message Consume
00000028 [25-06-2014 11:47:23] [DispatchThread: 2]: Message Consume
00000029 [25-06-2014 12:02:12] [DispatchThread: 2]: Message Consume
0000002b [25-06-2014 12:35:21] [DispatchThread: 3]: Message Consume
0000002c [25-06-2014 12:35:21] [DispatchThread: 3]: Message Consume
0000002d [25-06-2014 14:02:04] [DispatchThread: 3]: Message Consume
0000002e [25-06-2014 15:47:56] [DispatchThread: 3]: Message Consume
0000002f [25-06-2014 18:02:30] [DispatchThread: 4]: Message Consume
00000030 [25-06-2014 20:01:59] [DispatchThread: 4]: Message Consume
00000031 [26-06-2014 00:22:48] [DispatchThread: 4]: Message Consume
00000032 [26-06-2014 10:02:05] [DispatchThread: 4]: Message Consume
00000033 [26-06-2014 14:23:23] [DispatchThread: 5]: Message Consume
00000034 [26-06-2014 14:23:23] [DispatchThread: 5]: Message Consume
00000035 [26-06-2014 14:31:29] [DispatchThread: 5]: Message Consume
00000036 [26-06-2014 14:31:29] [DispatchThread: 5]: Message Consume
00000037 [26-06-2014 15:12:53] [DispatchThread: 6]: Message Consume
00000038 [26-06-2014 15:12:54] [DispatchThread: 6]: Message Consume
00000039 [26-06-2014 15:15:19] [DispatchThread: 6]: Message Consume
0000003a [26-06-2014 15:15:20] [DispatchThread: 6]: Message Consume
0000003b [26-06-2014 15:26:12] [DispatchThread: 7]: Message Consume
0000003c [26-06-2014 15:26:12] [DispatchThread: 7]: Message Consume
0000003d [26-06-2014 15:30:50] [DispatchThread: 7]: Message Consume
0000003e [26-06-2014 15:30:51] [DispatchThread: 7]: Message Consume
0000003f [26-06-2014 15:54:43] [DispatchThread: 8]: Message Consume
00000040 [26-06-2014 15:54:43] [DispatchThread: 8]: Message Consume
00000041 [26-06-2014 16:02:21] [DispatchThread: 8]: Message Consume
00000042 [26-06-2014 16:06:21] [DispatchThread: 8]: Message Consume
00000043 [27-06-2014 02:31:18] [DispatchThread: 9]: Message Consume
00000044 [27-06-2014 09:04:16] [DispatchThread: 9]: Message Consume
00000045 [27-06-2014 09:05:36] [DispatchThread: 9]: Message Consume
00000046 [27-06-2014 09:06:38] [DispatchThread: 9]: Message Consume

Mule Thread Configuration : ule子线程配置： 

<configuration doc:name="Configuration">
    <default-threading-profile maxBufferSize="300" maxThreadsActive="20" maxThreadsIdle="10" threadTTL="60000" poolExhaustedAction="RUN" />
</configuration>

Mule MQ Configuration : Mule MQ配置： 

<spring:bean id="connectionFactory" class="com.ibm.mq.jms.MQXAQueueConnectionFactory">
    <spring:property name="channel" value="${wmq.channel}" />
    <spring:property name="queueManager" value="${wmq.queue.manager}" />
    <spring:property name="transportType" value="1" />
    <spring:property name="connectionNameList" value="${wmq.host.list}" />
</spring:bean>
<jms:websphere-connector name="wmqConnector" username="${wmq.username}"
    password="${wmq.password}" connectionFactory-ref="connectionFactory">
    <reconnect-forever blocking="false" frequency="60000" />
</jms:websphere-connector>

Note 1 : WebSphere MQ is configured for high availability with two servers in "wmq.host.list". 注1： WebSphere MQ已配置为具有“ wmq.host.list”中的两个服务器以实现高可用性。

Note 2 : The class used by the connection is the XA one. 注2：连接使用的类是XA。 But there are no transaction specified in the flow. 但是流中没有指定事务。

Note 3 : The log is from our production, I can not reproduce locally. 注3：日志来自我们的生产，我无法在本地复制。

Many thanks for your help. 非常感谢您的帮助。

François 弗朗索瓦

1 个解决方案

解决方案1
 1 已采纳  2014-06-30 15:29:09

Mule uses the native thread pool of some transports, like JMS, instead of creating its own. Mule使用某些传输（例如JMS）的本机线程池，而不是创建自己的线程池。

In your case, the DispatchThread: x threads are coming from the WMQ client. 在您的情况下， DispatchThread: x线程来自WMQ客户端。 These threads are fully managed by this client, ie they are created, named and possibly destroyed by the WMQ client, not by Mule. 这些线程由此客户端完全管理，即它们是由WMQ客户端而不是Mule创建，命名和破坏的。

The fact that this number increases doesn't necessary mean thread leak: use VisualVM or jConsole to determine if the number of threads is actually increasing. 这个数目增加的事实并不一定意味着线程泄漏：使用VisualVM或jConsole来确定线程数目实际上是否在增加。

暂无
暂无

声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 如何读取mule esb中的参数 - How to read parameter in mule esb 如何将JRebel与Mule ESB集成？ - How to integrate JRebel with Mule ESB? 如何在Mule ESB上发送电子邮件 - How to send an email on Mule ESB 如何检查Mule esb中是否存在文件 - How to check if file exists in Mule esb 如何使用请求路径在Mule ESB中进行路由 - How to route in Mule ESB using request path 如何在Mule ESB中将文件转换为字节数组？ - How to convert a file to a byte array in Mule ESB? 了解Mule ESB如何适应JDBC和REST - Understanding how Mule ESB fits in with JDBC and REST Mule ESB-如何获取MimeMessage而不是MimeBodyPart？ - Mule ESB - How to get MimeMessage instead of MimeBodyPart? 如何在Mule ESB中访问流量变量？ - how to Access flow variables in Mule ESB…? 如何将参数传递到Mule ESB流xml中？ - How to pass parameters into Mule ESB flow xml?
相关标签
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM