-
2. Re: WARN [org.hornetq.core.server] HQ222113: On ManagementService stop, there are 25 unexpected registered MBeans:
jbertram Oct 8, 2014 11:56 AM (in response to ravi.teja)The warning here is more informational than anything. I don't think there is any real functional impact. Have you noticed any functional impact to your application or the broker?
It looks like a lot of the MBeans that are listed in the warning message don't appear in your configuration file. Did you create a bunch of diverts through the admin API or something?
-
3. Re: WARN [org.hornetq.core.server] HQ222113: On ManagementService stop, there are 25 unexpected registered MBeans:
ravi.teja Oct 8, 2014 12:06 PM (in response to jbertram)Hi acxjbertr ,
Thank you for quick reply .
We are having almost some 35 diverts and all are with the configuration <exclusive>false</exclusive> and with the configuration
<address-settings>
<!--default for catch all-->
<address-setting match="#">
<dead-letter-address>jms.queue.DLQ</dead-letter-address>
<expiry-address>jms.queue.ExpiryQueue</expiry-address>
<redelivery-delay>0</redelivery-delay>
<max-size-bytes>10485760</max-size-bytes>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
<address-full-policy>BLOCK</address-full-policy>
</address-setting>
</address-settings>
In production the server works very good for 3 or 4 days . Then the messages are not consumed by the MDB . We have to kill the HQ server and delete all the .hq files in the journal folder and restart it . Then it works for few days .
Because of the above mentioned problem we went to implement the <address-full-policy> PAGE . But as we have several message selectors i stuck to configure it with the below mentioned message
-
4. Re: Re: WARN [org.hornetq.core.server] HQ222113: On ManagementService stop, there are 25 unexpected registered MBeans:
jbertram Oct 8, 2014 12:54 PM (in response to ravi.teja)We are having almost some 35 diverts and all are with the configuration <exclusive>false</exclusive> and with the configuration
There are only 2 diverts in the configuration you attached:
<diverts> <divert name="test-divert"> <routing-name>test-divert</routing-name> <address>jms.topic.TestTopic</address> <forwarding-address>jms.queue.DLQ</forwarding-address> <exclusive>false</exclusive> </divert> <divert name="test-divert2"> <routing-name>test-divert-2</routing-name> <address>jms.topic.TestTopic</address> <forwarding-address>jms.queue.TestQueue</forwarding-address> <exclusive>false</exclusive> </divert> <!-- Having some more diverts--> </diverts>
Can you clarify where the extra 33 diverts are coming from? Did you attach the proper config file(s)?
Also, I recommend you acquire several thread dumps when your MDB(s) stops consuming messages as well as the delivering count, message count, and consumer count for the relevant queue. That would help us debug the issue.
Lastly, please explain what is happening with the clients and the broker during the 3-4 days that it's operating normally. Are the producers sending a lot of messages? Are the consumers able to keep the queue(s) drained or do messages build up?
-
5. Re: Re: Re: WARN [org.hornetq.core.server] HQ222113: On ManagementService stop, there are 25 unexpected registered MBeans:
ravi.teja Oct 8, 2014 1:14 PM (in response to jbertram)Hi acxjbertr ,
1) Please find the attachment as HQ configuration end-to-end .
2) Could you help me how to get the message count ,delivery count for the relevant queue . So that i could provide you the details .
3) producers sending a lot of messages and all the messages are persisted , if the .hq files are full in the data/journal folder then it gets crash or stuck.
We have all the messages are autoacknowledgement .
-
hornetq-configuration.xml 12.3 KB
-
hornetq-jms.xml 5.5 KB
-
-
6. Re: Re: Re: WARN [org.hornetq.core.server] HQ222113: On ManagementService stop, there are 25 unexpected registered MBeans:
jbertram Oct 8, 2014 2:01 PM (in response to ravi.teja)1) Please find the attachment as HQ configuration end-to-end .
Thanks. That makes more sense. However, you haven't answered my question about whether or not you've seen any functional impact.
2) Could you help me how to get the message count ,delivery count for the relevant queue . So that i could provide you the details .
The documentation covers this. Using JMX is probably simplest. You can use JConsole to look at the MBean for the queue from which your MDB is consuming and get the metrics I mentioned.
3) producers sending a lot of messages and all the messages are persisted , if the .hq files are full in the data/journal folder then it gets crash or stuck.
What do you mean by "full"? Do you mean that your filesystem runs out of space? As I understand it, HornetQ should continue creating new journal files to accommodate new messages as long as there's space on the filesystem. Do you see any errors or exceptions in the HornetQ log? Is the behavior the same when using either PAGE and BLOCK as the address-full-policy?
-
7. Re: Re: Re: WARN [org.hornetq.core.server] HQ222113: On ManagementService stop, there are 25 unexpected registered MBeans:
ravi.teja Oct 9, 2014 1:21 AM (in response to jbertram)Hi acxjbertr ,
Justin Bertram wrote:
1) Thanks. That makes more sense. However, you haven't answered my question about whether or not you've seen any functional impact.
Yes , It is giving a functional impact that the server crashes after few days and didn't consume any messages
2) What do you mean by "full"? Do you mean that your filesystem runs out of space? As I understand it, HornetQ should continue creating new journal files to accommodate new messages as long as there's space on the filesystem. Do you see any errors or exceptions in the HornetQ log? Is the behavior the same when using either PAGE and BLOCK as the address-full-policy?
The filesystem will not runs out of space . We have configure <journal-min-files>10</journal-min-files> and BLOCK as the address-full-policy in hornetq-configuration.xml . When we send a some million of messages to address it will be diverted to appropriate queues , after few days ../data/journal folder is a having 10 hornetq-data-x.hq files and each file is having the size of 10 MB . In this case the HQ server didn't recieve any of the message and gets crash .
As mention above problem we have implemented the PAGE as the address-full-policy . But we are facing the problem with messages-selectors while implementing PAGE as address-full-policy .
Could you suggest good idea to resolve this issue ..? Please
-
8. Re: Re: Re: WARN [org.hornetq.core.server] HQ222113: On ManagementService stop, there are 25 unexpected registered MBeans:
jbertram Oct 9, 2014 11:59 AM (in response to ravi.teja)Yes , It is giving a functional impact that the server crashes after few days and didn't consume any messages
You originally started this thread about a warning message you observed when shutting down your server. The warning message said, "On ManagementService stop, there are 25 unexpected registered MBeans..." Are you saying that this is causing your server to crash after a few days? It seems to me like you're talking about 2 different things on this thread. Please clarify what issue you actually want to address. Do you want to deal with the warning message or the "crash" you observe when using BLOCK? There's nothing I can do about the message selector support with PAGE at this point so that's just something you're going to have to accept if you choose that configuration.
-
9. Re: Re: Re: WARN [org.hornetq.core.server] HQ222113: On ManagementService stop, there are 25 unexpected registered MBeans:
ravi.teja Oct 13, 2014 12:24 AM (in response to jbertram)Hi acxjbertr
I thought that The warning message said, "On ManagementService stop, there are 25 unexpected registered MBeans..." is causing the server to crash after a few days and this is what i want to address the issue and i will open another thread to the second issue for implementing the filter and paging with message selector to configure in hornetq server .
-
10. Re: Re: Re: WARN [org.hornetq.core.server] HQ222113: On ManagementService stop, there are 25 unexpected registered MBeans:
jbertram Oct 13, 2014 10:32 AM (in response to ravi.teja)My understanding was that you saw that warning message during the HornetQ shutdown process. In other words, the warning was a by-product of the shutdown rather than the cause. Can you clarify this point?
-
12. Re: WARN [org.hornetq.core.server] HQ222113: On ManagementService stop, there are 25 unexpected registered MBeans:
jbertram Oct 14, 2014 10:30 AM (in response to ravi.teja)I don't think the cause of the warning message has any functional impact so I would recommend you simply ignore it at this point. I'm not sure what the root cause of it is. I'd need a reproducible test-case to investigate further.
-
13. Re: Re: Re: WARN [org.hornetq.core.server] HQ222113: On ManagementService stop, there are 25 unexpected registered MBeans:
ravi.teja Oct 16, 2014 1:49 PM (in response to jbertram)Hi acxjbertr
I downloaded hornetq-2.4 and started running . It is running successfully.
I done configuration chages in run.sh file as below
java $JVM_ARGS -classpath $CLASSPATH -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=3333 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false org.hornetq.integration.bootstrap.HornetQBootstrapServer $FILENAME
When i run the jconsole to monitor hornetq , i am able to connect but nometrics is showing up to monitor . Please find the screens shots attached .
Could you please suggest anything i was missing configuration .
-
14. Re: Re: Re: WARN [org.hornetq.core.server] HQ222113: On ManagementService stop, there are 25 unexpected registered MBeans:
jbertram Oct 16, 2014 3:36 PM (in response to ravi.teja)1 of 1 people found this helpfulTry clicking on the "Attributes" sub-item below the "ActivityTrackerQueue". I think you'll see the metrics you're looking for.