We are not able to configure the Attributes:
<attribute name="FullSize">75000</attribute>
| <attribute name="PageSize">2000</attribute>
| <attribute name="DownCacheSize">2000</attribute>
because of following exception:
ObjectName: jboss.mq.destination:name=rawEventTopic,service=Topic
| State: FAILED
| Reason: org.jboss.deployment.DeploymentException: No Attribute found with name: FullSize
| I Depend On:
| jboss.mq:service=DestinationManager
| jboss.mq:service=SecurityManager
| Depends On Me:
| HFNSI.bi:name=HFNSIEventBridgeService,type=HFNSIEventBridgeService
|
Is there any way to avoid the growing Heap Usage and the OutOfMemory?
Thanks
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221044#4221044
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221044
anonymous wrote : As additional evidence, I set a hostname for the remote machine, and added it's IP address and host name in both the client and server's local lookup table (/etc/hosts). When I try to connect, everything works exactly as expected.
You found the fix. The host running JBoss AS must have its IP address and host name in its /etc/hosts file. In addition, the client system also needs that information in its /etc/hosts file.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221042#4221042
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221042
Hello Community,
we have a 4.0.5 which is configured as a JMS-Server with null-persistence. The server is flooded at Runtime with a very large number of ObjectMessages. Our problem is the growing usage of Heap in Runtime which causes an OutOfMemory Exception.
we configured MessageSoftening
<mbean code="org.jboss.mq.server.MessageCache"
| name="jboss.mq:service=MessageCache">
| <attribute name="HighMemoryMark">50</attribute>
| <attribute name="MaxMemoryMark">60</attribute>
| <attribute name="CacheStore">jboss.mq:service=PersistenceManager</attribute>
| </mbean>
|
and use the
| org.jboss.mq.pm.none.PersistenceManager
We are not able to configure the Attributes:
75000
2000
2000
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221040#4221040
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221040
When the messaging service starts, it runs the DDL statements to create the tables it needs. If these fail because the tables already exist, you get these DEBUG log entries. I can think of two ways to turn them off:
1) Change the code to not log the messages
2) Change the logging level to INFO for the messaging loggers.
And to answer you other question, yes most people running JBoss AS simply ignore these log entries. In general, if the stack trace does not show up in the console log, it is OK to ignore.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221034#4221034
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221034