aspose file tools*
The moose likes JBoss/WildFly and the fly likes  [DLQHandler] Message resent too many times Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark " [DLQHandler] Message resent too many times" Watch " [DLQHandler] Message resent too many times" New topic
Author

[DLQHandler] Message resent too many times

taylor mark
Greenhorn

Joined: Jan 27, 2005
Posts: 7
Hi,

I am using jboss-3.2.1 and to deploying message driven bean.
It is working fine if I MDB don't throw any error.
I am getting the following error when an exception is throw in MDB.

14:25:17,171 WARN [DLQHandler] Message resent too many times; sending it to DLQ; message id=ID:6-11068538999531


I read jboss documentation and unable to figure out the problem. Jboss sending message 10 times if MDB throws an exception
and finally getting the above warning.
By default jboss sends message 10 times if MDB throws an exeption. I tried to control this but not working.
In standardjboss.xml file I used MaxTimesRedelivered = 1 (i.e I want to send message only once if there is any error in MDB).
I don't want to send message 10 times if there is any error in MDB.
Please can any one help me?

Here is my standardjboss.xml and jboss.xml files.


standardjboss.xml file
**************************

<jboss>
...........
...............
<container-configuration>
<container-name>Standard Message Driven Bean</container-name>
<call-logging>false</call-logging>
<invoker-proxy-bindings>
<invoker-proxy-binding>
<name>message-driven-bean</name>
<invoker-mbean>default</invoker-mbean>
<proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
<proxy-factory-config>
<JMSProviderAdapterJNDI>QueuehostJMSProvider</JMSProviderAdapterJNDI>
<ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
<MinimumSize>10</MinimumSize>
<KeepAliveMillis>30000</KeepAliveMillis>
<MaximumSize>50</MaximumSize>
<MaxMessages>1</MaxMessages>
<MDBConfig>
<ReconnectIntervalSec>10</ReconnectIntervalSec>
<DLQConfig>
<DestinationQueue>queue/DLQ</DestinationQueue>
<MaxTimesRedelivered>1</MaxTimesRedelivered>
<TimeToLive>0</TimeToLive>
</DLQConfig>
</MDBConfig>
</proxy-factory-config>
</invoker-proxy-binding>
</invoker-proxy-bindings>


<container-interceptors>
<interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
<interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
<interceptor>org.jboss.ejb.plugins.RunAsSecurityInterceptor</interceptor>
<!-- CMT -->
<interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
<interceptor transaction="Container" metricsEnabled="true">org.jboss.ejb.plugins.MetricsInterceptor</interceptor>
<interceptor transaction="Container">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor>
<!-- BMT -->
<interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor>
<interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT</interceptor>
<interceptor transaction="Bean" metricsEnabled="true">org.jboss.ejb.plugins.MetricsInterceptor</interceptor>
<interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
</container-interceptors>

<instance-pool>org.jboss.ejb.plugins.MessageDrivenInstancePool</instance-pool>
<instance-cache></instance-cache>
<persistence-manager></persistence-manager>
<container-pool-conf>
<MaximumSize>100</MaximumSize>
</container-pool-conf>

</container-configuration>

</container-configurations>

</jboss>


jboss.xml
**************
<jboss>
...............
................
<message-driven>
<ejb-name>TestMDB</ejb-name>
<destination-jndi-name>queue/testQueue1</destination-jndi-name>

<invoker-bindings>
<invoker>
<invoker-proxy-binding-name>message-driven-bean</invoker-proxy-binding-name>
</invoker>
</invoker-bindings>
</message-driven>

</jboss>
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: [DLQHandler] Message resent too many times