Hi Tim, Sorry I could not reply soon because of some errors from nabble forum on last Friday.
> So are all client IPs represented proportionally in the EOFExceptions? No, just only one consumer represented EOFException in ActiveMQ's log. That consumer is running on the same machine with the broker, so its IP is 127.0.0.1/0:0:0:0:0:0:0:1 in log file. > You would have to explicitly enable websockets, and your clients would > have > to explicitly use them, so it sounds like you're not using them. That's > fine, it just means that JIRA doesn't apply to you. I understand that Jira ticket does not apply to me. But I would like to know how to enable websockets for my broker? Can I do that in ActiveMQ config activemq.xml? > How many threads fall into each of the three categories? I have no idea which threads fall into which category by looking into log file. I also attach it. > Keep in mind that the broker starts threads when clients connect (to read > data from the sockets), so having more threads on the active broker isn't > entirely unexpected. But the size of the difference might indicate that > clients are opening connections for each message or something similar. > Since you haven't told us anything about your client workload, I can't say > for sure whether the the difference in thread count is expected or is a > cause for concern. An 'active' broker would receive ~140 messages per hour. And it keep receiving messages all day. More info: after 2-3 days, OutOfMemoryError would occurred. We restart both brokers daily to avoid that error. Thanks and best regards, Siebo -- View this message in context: http://activemq.2283324.n4.nabble.com/org-apache-activemq-broker-TransportConnection-Transport-Transport-Connection-to-tcp-XX-XX-XXX-XXX-5n-tp4722840p4725184.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
