"b.eckenfels" wrote : Are you shure you have a Problem with retained messages.
If you do not have a PM, then all undelivered Messages in the queues will be
kept in Memory. So check your queue length (and DLQ) how many of those messages
are not delivered at the time of your OOM.
|
| Have you
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 endless growing usage of Heap on the server which causes an
OutOfMemory Exception.
we configured MessageC
We are not able to configure the Attributes:
75000
| 2000
| 2000
because of following exception:
ObjectName: jboss.mq.destination:name=rawEventTopic,service=Topic
| State: FAILED
| Reason: org.jboss.deployment.DeploymentException: No Attribute found w
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
Hello community,
i have configured my application for singleton message driven bean, But jboss
instantiate my MDB several times if there are too many messages in the topic.
The more messages are in the topic the more MDB instances are created by jboss.
What should i do to get this problem solved
Hello jaikiran,
i have the same problem and tried to configure the jboss as singleton. But it
doesn't function. Looking at the "Singleton Message Driven Bean" in jboss.xml
i found out that the both Configurations (single and standard message driven
bean) are the same. The link in faq to the ex
please ignor the above post. Some xml tags are deleted. the following is the
correct one:
i am developing an Event Driven architecture using j2ee (MDB) on JBoss. In this
Architecture the incoming business events (raw events) will be fetched by a
MDB, wich forward the raw events to Event Stream
Hello community,
i am developing an Event Driven architecture using j2ee (MDB) on JBoss. In this
Architecture the incoming business events (raw events) will be fetched by a
MDB, wich forward the raw events to Event Stream Processor. My Problem is that
JBoss instantiate multiple instances of my
JDK 5.0 was the reason of the Problem. It was too recent for the older JBOSS
version JBoss-2.4.0_Tomcat-3.2.3. After i changed to jdk 1.3.1 and built the
application again with the jdk 1.3.1, it ran without any problem. It is very
Important to build it again with the jdk 1.3.1 and deploy it then
