6 Replies Latest reply on Aug 14, 2009 4:43 AM by arjun purushothaman

    JBossesb server Error processing courier,backing off 32000 M

    arjun purushothaman Newbie

      Hi

      I have below items in jbossesb server 4.2.2 GA
      1) 9 services.
      2) 14 listeners.

      I have configured MySQL datasource instead of the
      default HSQL (namely esb, jms and juddi).

      ESB services I have deployed stop picking up messages from FTP.

      I am getting "Error processing courier, backing off 32000 Milliseconds" when I give xml file as input with FileZilla.

      May I know the solution to this problem.

        • 1. Re: JBossesb server Error processing courier,backing off 320
          Kevin Conner Master

          We don't have an ESB 4.2.2 so I am guessing you mean AS 4.2.2.

          Which version of the ESB are you using? What does the DEBUG show in the log file?

          Kev

          • 2. Re: JBossesb server Error processing courier,backing off 320
            arjun purushothaman Newbie

            Hi Kevin,

            We are using JBoss AS 4.2.2 GA and ESB 4.4 GA.
            We have around 11 services and more than 11 listeners in our single jboss-esb.xml file.
            Is there any limitation for number of services permitted in a single ESB.
            If so, is there a way to increase that number in any configuration.

            So actually what is happening is when we deploy our .ESB, it is deploying without any issue. But when we provide any input (through FTP), ESB is taking time to process the message and sometimes becoming un resonsive.

            Please find the log below.

            11:51:55,203 INFO [ServiceInvoker] Unresponsive EPR: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/ESBInboundDummyQ/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] for message: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/ESBInboundDummyQ/>, <wsa:ReferenceP
            roperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ]
            11:52:14,875 WARN [MessageAwareListener] Error processing courier, backing off for 2000 milliseconds
            11:52:25,875 INFO [ServiceInvoker] Unresponsive EPR: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/ESBInboundDummyQ/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] for message: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/ESBInboundDummyQ/>, <wsa:ReferenceP
            roperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ]



            Please help us in resolving this issue.

            Thanks in Advance,
            Arjun

            • 3. Re: JBossesb server Error processing courier,backing off 320
              Kevin Conner Master

              There is no limit to the number of services you can deploy however there are resource limits for each deployment.

              The ones which may be affecting you are the JMS connection pool and the naming connection pool.

              You can set both of these in jbossesb-properties.xml to larger values but make sure that the naming maximum is larger than the jms maximum if you are really using ESB 4.4 (there is a bug in that version which leads to deadlocked resource resource contention).

              The properties you are after are org.jboss.soa.esb.namingcontext.poolsize (in "core") and org.jboss.soa.esb.jms.connectionPool (in "transports").

              Kev

              • 4. Re: JBossesb server Error processing courier,backing off 320
                arjun purushothaman Newbie

                Hi Kevin,

                Thanks for your prompt reply. I very much appreciate it.

                We increased the value of "org.jboss.soa.esb.jms.connectionPool" to 100 in "jbossesb-properties.xml" and it resolved the"backing off" issue and now the files are being processed without any delay.

                Regarding the property "org.jboss.soa.esb.namingcontext.poolsize", there is no such property name in "jbossesb-properties.xml" file(inside jbossesb.sar). Since you have pointed out that there is bug in ESB 4.4 version (if namingcontext value is less than jms pool size) related to the value of it, we are worried about it.

                Thanks & Regards,
                Arjun

                • 5. Re: JBossesb server Error processing courier,backing off 320
                  Kevin Conner Master

                  It is not in the file but it does exist and defaults to 20.

                  Just add that property in the "core" section and set it to a larger amount, 101 or above.

                  Kev