The eviction event queue holds event objects that describe reads and writes to the cache. Those are used by the eviction handling code to determine which nodes to evict (e.g. what nodes are LRU).
The queue itself takes memory, but it's a bounded queue so it won't grow beyond 200,000 entries. But these WARN messages are a sign that eviction is overloaded, which can result in excess nodes being left in the cache.
I would reduce your wakeUpIntervalSeconds to 1.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224132#4224132
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224132
I was quite successful using AndroMDA as a basic tool to develop a set of portlets for a project of mine.
The only caveat is that the code generator assumes a liferay portal out of the box, but this can be easily changed thanks to the extensive customization hooks that this tool provides.
The generated code uses JSF for presentation, using the trinidad components and you can choose from a handful of options to implement your service and persistence layers.
For modeling, I've used ArgoUML 0.26, which is pretty usable and offers full support for the UML features needed for proper UI code generation.
In my particular scenario (simple forms, wizards and master/detail reports), AndroMA was able to take care of ~ 90% of UI code, but YMMV...
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224127#4224127
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224127
Hi thanks for the replies. This is a non-clustered destination.
Regarding the db connection problems: why would that occur? The connections are under the control of the jboss messaging. Can you post a recommended postgres-persistence-service.xml -- I have tried ones from the samples and the distributions and so far they all have issues when using with non-clustered durable destinations
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224124#4224124
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224124
Just before the jvm got outofmemory error, we notice in the log many entries like this:
putNodeEvent(): eviction node event queue size is at 98% threshold value of capacity: 200000 You will need to reduce the wakeUpIntervalSeconds parameter.
Our wakeUpIntervalSeconds is set as 3 (seconds). I don't understand what the eviction node even queue is and why it can reach almost 200,000. Does it take memory or it just writes into file system? It is likely this eviction queue causes the outofmemory? Is there anything we can configure treecache or jboss to avoid outofmemory?
Thank you very much for your help.
P.S. We do have a jboss support license. But since jboss and redhat are merged, our login does not work anymore. We are working with redhat people to sort this out. In the meantime, I have to post our questions here.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224123#4224123
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224123
I've seen information pointing to various versions of this, but each version has had its own issues.
My scenario is non-clustered durable destinations are failing with the following message:
javax.jms.JMSException: Failed to route Reference[]:RELIABLE to TestQueue
As part of the triage on this, I just want to ensure that the postgres-persistence-service.xml is exactly right: can someone post it here that is working for durable queues/or topics ?
thanks!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224122#4224122
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224122