I have an issue using dlQMaxResent within my jboss-ejb3.xml. It looks like the value is not respected anymore - from monitoring it seems like default values are applied.
<?xml version="1.1" encoding="UTF-8"?>
<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:s="urn:security:1.1"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd"
impl-version="2.0" version="3.1">
<jboss:enterprise-beans>
<message-driven id="DequeuerBean">
<ejb-name>DequeuerBean</ejb-name>
<activation-config>
<activation-config-property>
<activation-config-property-name>dLQMaxResent</activation-config-property-name>
<activation-config-property-value>2147483647</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>maxSession</activation-config-property-name>
<activation-config-property-value>20</activation-config-property-value>
</activation-config-property>
</activation-config>
</message-driven>
<...>
</jboss:ejb-jar>
Can someone shed some light on this?
Thanks in advance.
Regs,
Rob
In Wildfly you would be implicitly using the HornetQ JCA RA for message inflow which does not support the activation configuration property "dLQMaxResent." Configuration for redelivery behavior is done on the broker itself (i.e. in <address-settings> of <hornetq-server>).