MDB initialRedeliveryDelay configuration

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

MDB initialRedeliveryDelay configuration

gnanapandithan

I am trying to consume message from websphere MQ using  MDB and configured in ejb-jar.xml . am using below mentioned tech stack. I need to add redelivery delay option in my MDB activation config. I used"initialRedeliveryDelay" option in ejb-jar.xml got exception.

Tech stack
1. TomEE 7.0.3
2. Java EE 7
3. JMS 2.0
4. IBM MQ 8.0

MDB ActivationConfig
http://tomee.apache.org/jms-resources-and-mdb-container.html

code
                                <activation-config-property>
                                        <activation-config-property-name>initialRedeliveryDelay</activation-config-property-name>
                                        <activation-config-property-value>50000</activation-config-property-value>
                                </activation-config-property>


Exception
Caused by: org.apache.openejb.OpenEJBException: Unable to create activation spec: No setter found for the activation spec properties: [initialRedeliveryDelay]
        at org.apache.openejb.core.mdb.MdbContainer.createActivationSpec(MdbContainer.java:256)
        at org.apache.openejb.core.mdb.MdbContainer.deploy(MdbContainer.java:139)
        at org.apache.openejb.assembler.classic.Assembler.startEjbs(Assembler.java:1584)
        ... 14 more
Caused by: java.lang.IllegalArgumentException: No setter found for the activation spec properties: [initialRedeliveryDelay]
        at org.apache.openejb.core.mdb.MdbContainer.createActivationSpec(MdbContainer.java:225)
Reply | Threaded
Open this post in threaded view
|

Re: MDB initialRedeliveryDelay configuration

Romain Manni-Bucau
Hi

Can you share your mdb container config please?

Also maybe execute the setters command of tomee.sh on your activationspec
class.

Le 11 août 2017 02:18, "gnanapandithan" <[hidden email]> a
écrit :

>
> I am trying to consume message from websphere MQ using  MDB and configured
> in ejb-jar.xml . am using below mentioned tech stack. I need to add
> *redelivery delay* option in my MDB activation config. I
> used"initialRedeliveryDelay" option in ejb-jar.xml got exception.
>
> *Tech stack*
> 1. TomEE 7.0.3
> 2. Java EE 7
> 3. JMS 2.0
> 4. IBM MQ 8.0
>
> /MDB ActivationConfig/
> http://tomee.apache.org/jms-resources-and-mdb-container.html
>
> *code*
>                                 <activation-config-property>
>
> <activation-config-property-name>initialRedeliveryDelay</
> activation-config-property-name>
>
> <activation-config-property-value>50000</activation-config-property-value>
>                                 </activation-config-property>
>
>
> *Exception*
> Caused by: org.apache.openejb.OpenEJBException: Unable to create
> activation
> spec: No setter found for the activation spec properties:
> [initialRedeliveryDelay]
>         at
> org.apache.openejb.core.mdb.MdbContainer.createActivationSpec(
> MdbContainer.java:256)
>         at org.apache.openejb.core.mdb.MdbContainer.deploy(
> MdbContainer.java:139)
>         at
> org.apache.openejb.assembler.classic.Assembler.startEjbs(
> Assembler.java:1584)
>         ... 14 more
> Caused by: java.lang.IllegalArgumentException: No setter found for the
> activation spec properties: [initialRedeliveryDelay]
>         at
> org.apache.openejb.core.mdb.MdbContainer.createActivationSpec(
> MdbContainer.java:225)
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/MDB-initialRedeliveryDelay-configuration-tp4682419.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>
Reply | Threaded
Open this post in threaded view
|

Re: MDB initialRedeliveryDelay configuration

gnanapandithan
MDB configuration mean, you need ejb-jar.xml configuration for MDB
Reply | Threaded
Open this post in threaded view
|

Re: MDB initialRedeliveryDelay configuration

gnanapandithan
This post was updated on .

<message-driven>
    <ejb-name>AccountTransferOutboundMDB</ejb-name>
    <ejb-class>gov.utah.dts.messageDrivenBean.AccountTransferOutboundMDB</ejb-class>
     <transaction-type>Container</transaction-type>
     <message-destination-type>javax.jms.Topic</message-destination-type>
   <activation-config>
      <activation-config-property>
              <activation-config-property-name>destinationType</activation-config-property-name>
              <activation-config-property-value>javax.jms.Topic</activation-config-property-value>
      </activation-config-property>
      <activation-config-property>
            <activation-config-property-name>destination</activation-config-property-name>
              <activation-config-property-value>java:/topic/whm_dev_ATROutboundTopic</activation-config-property-value>
      </activation-config-property>
      <activation-config-property>
            <activation-config-property-name>subscriptionDurability</activation-config-property-name>
              <activation-config-property-value>Durable</activation-config-property-value>
      </activation-config-property>
      <activation-config-property>
            <activation-config-property-name>clientID</activation-config-property-name>
              <activation-config-property-value>MYCATR</activation-config-property-value>
      </activation-config-property>
      <activation-config-property>
            <activation-config-property-name>subscriptionName</activation-config-property-name>
              <activation-config-property-value>ATROutbound</activation-config-property-value>
      </activation-config-property>
    </activation-config>

<activation-config-property>
                                <activation-config-property-name>initialRedeliveryDelay</activation-config-property-name>
                                <activation-config-property-value>50000</activation-config-property-value>
                        </activation-config-property>
 
</message-driven>


Reply | Threaded
Open this post in threaded view
|

Re: MDB initialRedeliveryDelay configuration

Romain Manni-Bucau
No it was really the container one, likely from your tomee.xml. Then we can
validate the class you use and if the option is available or not.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-08-11 7:36 GMT+02:00 gnanapandithan <[hidden email]>:

>
>
>
>
>
>
>
>
>
>
>
>
>
> <message-driven>
>     <ejb-name>AccountTransferOutboundMDB</ejb-name>
>
> <ejb-class>gov.utah.dts.messageDrivenBean.AccountTransferOutboundMDB</
> ejb-class>
>      <transaction-type>Container</transaction-type>
>      <message-destination-type>javax.jms.Topic</message-destination-type>
>    <activation-config>
>       <activation-config-property>
>
> <activation-config-property-name>destinationType</
> activation-config-property-name>
>
> <activation-config-property-value>javax.jms.Topic</
> activation-config-property-value>
>       </activation-config-property>
>       <activation-config-property>
>
> <activation-config-property-name>destination</activation-
> config-property-name>
>
> <activation-config-property-value>java:/topic/whm_dev_
> ATROutboundTopic</activation-config-property-value>
>       </activation-config-property>
>       <activation-config-property>
>
> <activation-config-property-name>subscriptionDurability</
> activation-config-property-name>
>
> <activation-config-property-value>Durable</activation-
> config-property-value>
>       </activation-config-property>
>       <activation-config-property>
>
> <activation-config-property-name>clientID</activation-
> config-property-name>
>
> <activation-config-property-value>MYCATR</activation-
> config-property-value>
>       </activation-config-property>
>       <activation-config-property>
>
> <activation-config-property-name>subscriptionName</
> activation-config-property-name>
>
> <activation-config-property-value>ATROutbound</activation-
> config-property-value>
>       </activation-config-property>
>     </activation-config>
>
> <activation-config-property>
>
> <activation-config-property-name>initialRedeliveryDelay</
> activation-config-property-name>
>
> <activation-config-property-value>50000</activation-config-property-value>
>                         </activation-config-property>
>
> </message-driven>
>
>
>
>
>
>
>
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/MDB-initialRedeliveryDelay-configuration-
> tp4682419p4682423.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>
Reply | Threaded
Open this post in threaded view
|

Re: MDB initialRedeliveryDelay configuration

gnanapandithan
I am using JCA concept for MQ connectivity. I refereed below mentioned example program.

http://tomee.apache.org/tomee-and-webspheremq.html
 
Reply | Threaded
Open this post in threaded view
|

Re: MDB initialRedeliveryDelay configuration

Romain Manni-Bucau
Maybe check with the setters command of tomee.sh the available action spec,
it is surely not available in your version.

Le 11 août 2017 19:01, "gnanapandithan" <[hidden email]> a
écrit :

> I am using JCA concept for MQ connectivity. I refereed below mentioned
> example program.
>
> http://tomee.apache.org/tomee-and-webspheremq.html
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/MDB-initialRedeliveryDelay-configuration-
> tp4682419p4682439.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>