This is my problem...

scenario:
------------
I am publishing objects on to a Topic to which a message driven bean is
bound. The MDB on receiving the object does a HTTP post to a remote server.
The objects published on to the bus are generally done in bursts of 8000.
Everything works fine till when about 40000 messages are published. After
this the MDB seem to hang and the publishing of messages to the remote
server does'nt happen.

set up:
---------
JBoss2.4.3with tomcat3.2.3 on Linux. Runs on a PIII with 256MB RAM.
Persistence manager:FilePersistenceManager.
max message listeners pool size 100.
max mdb instances 400.(chk xml snippet @ end)

must also add that the n/w link is quite bad.

will it help if i increase the RAM?since the memory utilization seems quite high anyways.
will porting/deploying it to later version help?
anything simpler?

<>

<container-configuration>
<container-name>Standard Message Driven Bean</container-name>
<call-logging>false</call-logging>

<container-invoker>org.jboss.ejb.plugins.jms.JMSContainerInvoker</container-
invoker>
<container-interceptors>

org.jboss.ejb.plugins.LogInterceptor

org.jboss.ejb.plugins.SecurityInterceptor
<!-- CMT -->
org.jboss.ejb.plugins.TxInterceptorCMT
org.jboss.ejb.plugins.MetricsInterceptor
org.jboss.ejb.plugins.MessageDrivenInstanceIntercept
or
<!-- BMT -->
org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</i
nterceptor>
org.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT</inte
rceptor>
org.jboss.ejb.plugins.MetricsInterceptor
</container-interceptors>

<instance-pool>org.jboss.ejb.plugins.MessageDrivenInstancePool</instance-poo
l>
<instance-cache></instance-cache>
<persistence-manager></persistence-manager>

<transaction-manager>org.jboss.tm.TxManager</transaction-manager>
<container-invoker-conf>

DefaultJMSProvider

StdJMSPool
100
1
True
</container-invoker-conf>
<container-pool-conf>
400
10
</container-pool-conf>
</container-configuration>

Thanks in advans
david