1 Reply Latest reply on Mar 25, 2009 12:00 PM by S Shetty

    Strange jbr behaviour under heavy load - incoming request co

    S Shetty Newbie

      Hi,

      We are using a jbr provider to process HTTP POST requests.

      The action accepts parameters as a query string and returns an xml response. Under heavy load, we notice the request contains the response xml from the action. And we observe a never ending loop - we see an error response xml being sent in as a request - even when we stop the load test tool.

      Every incoming request is the xml response.

      Below is the service section from the jboss-esb.xml file.

       <service category="CMTE" name="Search Content" description="Search Content" invmScope="GLOBAL">
       <property name="maxThreads" value="1000"/>
       <listeners>
       <jbr-listener name="Cmte Search Content Gateway"
       busidref="cmte_cnni_search_content_http_end_point" is-gateway="true" maxThreads="1000">
       <property name="jbr-maxThreads" value="1000"/>
       </jbr-listener>
       </listeners>
       <actions mep="RequestResponse">
       <action name="print-before" class="org.jboss.soa.esb.actions.SystemPrintln">
       <property name="printfull" value="true"/>
       <property name="outputstream" value="false"/>
       </action>
      
       <action name="SearchContent" class="se.cmte.search.SearchContentAction"
       process="process" />
       </actions>
       </service>
      


      This works fine when we have 100 clients connecting simultaneously and we dont see this behaviour. However, when we upped this to 1000 client connections we see this behaviour.

      Any help appreciated.

      Thanks

      :)
      SShetty

        • 1. Re: Strange jbr behaviour under heavy load - incoming reques
          S Shetty Newbie

          I am now logging the messages to the service. When I look at the messages logged.

          Typically the message contains a reply-to epr which is an invm thread epr.
          e.g.

          19:50:04,110 ERROR [STDERR] [ message: [ JBOSS_XML ]
          header: [ To: InVMEpr [ PortReference < <wsa:Address invm://434d544520434e4e4953656172636820436f6e74656e74/false?false#10000/>, <wsa:ReferenceProperties jbossesb:passByValue : false/>, <wsa:ReferencePro
          perties jbossesb:type : urn:jboss/esb/epr/type/invm/> > ] ReplyTo: InVMEpr [ PortReference < <wsa:Address invm://thread-872/>, <wsa:ReferenceProperties jbossesb:passByValue : false/> > ] ]
          context: [ ]
          body: [ objects: {org.jboss.soa.esb.message.defaultEntry=topic=news&category=entertainment, org.jboss.soa.esb.message.defaultEntry-set-stack=java.lang.Exception: setPayload stack trace for 'org.jboss.so
          a.esb.message.defaultEntry'.} ]
          fault: [ ]
          attachments: [ Named:{}, Unnamed:[] ]
          properties: [ {org.jboss.soa.esb.message.time.dod=Tue Mar 24 19:50:04 CDT 2009, HttpVersion=HTTP/1.1, connection=keep-alive, org.jboss.soa.esb.message.time.dob=Tue Mar 24 19:50:03 CDT 2009, accept=text/
          html, image/gif, image/jpeg, *; q=.2, */*; q=.2, MethodType=POST, Path=/cnni/process.do, content-length=33, user-agent=Java/1.5.0_16, content-type=application/x-www-form-urlencoded, host=10.185.42.22:91
          00} ] ]
          


          However, when the problem surfaces, the the message contains a from instead. And this appears to the be service itself. Which doesnt make sense.

          19:50:04,111 ERROR [STDERR] [ message: [ JBOSS_XML ]
          header: [ To: InVMEpr [ PortReference < <wsa:Address invm://434d544520434e4e4953656172636820436f6e74656e74/false?false#10000/>, <wsa:ReferenceProperties jbossesb:passByValue : false/>, <wsa:ReferencePro
          perties jbossesb:type : urn:jboss/esb/epr/type/invm/> > ] From: InVMEpr [ PortReference < <wsa:Address invm://434d544520434e4e4953656172636820436f6e74656e74/false?false#10000/>, <wsa:ReferenceProperties
           jbossesb:passByValue : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/invm/> > ] ]
          context: [ ]
          


          Any ideas what might be causing this.