4 Replies Latest reply on Apr 9, 2008 12:13 PM by adrian.brock

    JBossJMSMessageEndpointFactory ActivationConfigProperties?

    asylumx

      Hello!

      I've got a queue set up with an EJB3 MDB implemented to catch the messages. Sometimes, this MDB ends up being long running, and the queue decides to resend the message due to timeout. In response to that, I'm looking for a way to configure this queue to allow for a longer timeout, but I'm not sure what activationConfigProperty to set in order to achieve this end.

      I'm using org.jboss.ejb.plugins.inflow.JBossJMSMessageEndpointFactory for the proxy factory. Where can I find a list of all the available activationConfigProperties for this factory?

      By the way, I have tried acking the message early in the MDB, thinking that would prevent the queue from caring anymore whether the process finished or not, but that doesn't seem to help.

      Thanks for your time!

        • 1. Re: JBossJMSMessageEndpointFactory ActivationConfigPropertie

           

          "asylumx" wrote:
          Hello!

          I've got a queue set up with an EJB3 MDB implemented to catch the messages.
          ...
          I'm using org.jboss.ejb.plugins.inflow.JBossJMSMessageEndpointFactory for the proxy factory.


          If your using EJB3 then your not using that proxy factory.
          You're also in the wrong forum, try the EJB3 forum.


          Where can I find a list of all the available activationConfigProperties for this factory?


          In the documentation perhaps?

          e.g. This is what I get when I type "jboss jms activation config properties" into
          google and hit "I'm feeling lucky".
          http://wiki.jboss.org/wiki/ConfigJMSMessageListener


          By the way, I have tried acking the message early in the MDB


          CLIENT ACK is not supported in an MDB. N/Acking is controlled by the ejb
          container based on the result of the invocation of your MDB usually with a transaction.

          • 2. Re: JBossJMSMessageEndpointFactory ActivationConfigPropertie
            asylumx

            Yeah, I tried that link already. It doesn't even mention the "keepAlive" property that is in the default configuration for that factory. So much for that.

            The queue is redelivering the message to the MDB based on some kind of timeout. If what you say is true, the the EJB container is controlling the ack and is not acking until the transaction is complete, then that helps explain what is going on. Thank you.

            • 3. Re: JBossJMSMessageEndpointFactory ActivationConfigPropertie

               

              "asylumx" wrote:
              Yeah, I tried that link already. It doesn't even mention the "keepAlive" property that is in the default configuration for that factory. So much for that.


              That's because whoever added that feature didn't update the WIKI :-(


              The queue is redelivering the message to the MDB based on some kind of timeout.

              Transaction timeout.



              • 4. Re: JBossJMSMessageEndpointFactory ActivationConfigPropertie

                 

                "adrian@jboss.org" wrote:
                "asylumx" wrote:
                Yeah, I tried that link already. It doesn't even mention the "keepAlive" property that is in the default configuration for that factory. So much for that.


                That's because whoever added that feature didn't update the WIKI :-(


                It's irrelevant to this question though since keepAlive controls
                unused sessions getting closed not active sessions timing out.