Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Won't Fix
    • Affects Version/s: 3.2.2
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Message Flow:

      Client --> Http Consumer SU ----> Bean SU (Message Enricher) ---> Validation SU (using camel) ----> Routing SU (using camel) ----> Http Provider SU ---> Extern Appl

      I am doing load testing having 1000 users with 200 in parallel. Servicemix starts processing some requests successfully (it could be any number of requests not constant) after that it just hangs.

      Here I am attaching SA for the operation.

      NOTE: 1. In above SA , Http Consumer SU is having authMethod="BASIC"
      2. So, that requires users-passwords.properties and groups.properties files (which i am attaching here) need to integrate with servicemix/conf .

      1. ASF.LICENSE.NOT.GRANTED--changepassword-sa-1.0.jar
        6.55 MB
        Rapuru Sandeep Reddy
      2. ASF.LICENSE.NOT.GRANTED--users-passwords.properties
        0.9 kB
        Rapuru Sandeep Reddy
      3. ASF.LICENSE.NOT.GRANTED--groups.properties
        1 kB
        Rapuru Sandeep Reddy
      4. changepassword-09022008-180230
        173 kB
        Rapuru Sandeep Reddy
      5. changepassword-09022008-181250
        177 kB
        Rapuru Sandeep Reddy

        Activity

        Hide
        Gert Vanthienen added a comment -

        Bulk-closing older issues for Apache ServiceMix 3.x since we're no longer actively working on these at the moment.

        Show
        Gert Vanthienen added a comment - Bulk-closing older issues for Apache ServiceMix 3.x since we're no longer actively working on these at the moment.
        Hide
        Soumya Pal added a comment -

        Ah...I guess the anwer lies here

        http://servicemix.apache.org/thread-pools.html

        Cheers,
        Soumya

        Show
        Soumya Pal added a comment - Ah...I guess the anwer lies here http://servicemix.apache.org/thread-pools.html Cheers, Soumya
        Hide
        Soumya Pal added a comment -

        Even I would like to know the above questions posted by user rapuru sandeep.

        I saw when I send multiple requests using a multithreaded testing model...4 at a time get handled.
        How do we actually quantify "at a time" ? in a timely fashion? free threads?

        I am referring to default setting of
        servicemix.corePoolSize = 4
        servicemix.maximumPoolSize = 32
        servicemix.queueSize = 256

        in servicemix.properties file

        Show
        Soumya Pal added a comment - Even I would like to know the above questions posted by user rapuru sandeep. I saw when I send multiple requests using a multithreaded testing model...4 at a time get handled. How do we actually quantify "at a time" ? in a timely fashion? free threads? I am referring to default setting of servicemix.corePoolSize = 4 servicemix.maximumPoolSize = 32 servicemix.queueSize = 256 in servicemix.properties file
        Hide
        Rapuru Sandeep Reddy added a comment -

        I have already attached (changepassword-09022008-181250, changepassword-09022008-180230) thread dump files for your reference.

        I identified that the hang mostly occurs in Camel when the inboundExchangeCount reaches the minimum thread pool size set in servicemix.properties file (Observed in JConsole for Camel endpoint).

        I tried increasing thread pool size to min=30, max=60. And it seems to be working fine for 1000 users with 200 parallel requests.

        Questions:
        1. What is the meaning of "servicemix.corePoolSize" and "servicemix.maximumPoolSize" property value. I do understand that these specifies the thread pool for servicemix but how is it related to exchange count ?

        2. Why does my operation work some times with default pool configuration ?

        3. Can I configure thread pool for each component ? I would probably like to configure separate thread pool for Camel.

        Show
        Rapuru Sandeep Reddy added a comment - I have already attached (changepassword-09022008-181250, changepassword-09022008-180230) thread dump files for your reference. I identified that the hang mostly occurs in Camel when the inboundExchangeCount reaches the minimum thread pool size set in servicemix.properties file (Observed in JConsole for Camel endpoint). I tried increasing thread pool size to min=30, max=60. And it seems to be working fine for 1000 users with 200 parallel requests. Questions: 1. What is the meaning of "servicemix.corePoolSize" and "servicemix.maximumPoolSize" property value. I do understand that these specifies the thread pool for servicemix but how is it related to exchange count ? 2. Why does my operation work some times with default pool configuration ? 3. Can I configure thread pool for each component ? I would probably like to configure separate thread pool for Camel.
        Hide
        Guillaume Nodet added a comment -

        There are a few things you want to check:

        • raise the number of threads for servicemix (this is configured in conf/servicemix.properties)
        • make sure your custom bean is correctly processing the JBI exchange (need to return the DONE status, etc...)

        Please attach the ouput from the kill -3, it may prove useful too.

        Show
        Guillaume Nodet added a comment - There are a few things you want to check: raise the number of threads for servicemix (this is configured in conf/servicemix.properties) make sure your custom bean is correctly processing the JBI exchange (need to return the DONE status, etc...) Please attach the ouput from the kill -3, it may prove useful too.
        Hide
        Rapuru Sandeep Reddy added a comment -

        Tried kill -3 command and we haven't got any sufficient information from that where exactly threads getting hanged.
        And we haven't changed any settings of servicemix. We are just using what ever the default configurations that servicemix provides.

        We have attached two thread dumps files for your reference purposes.

        Show
        Rapuru Sandeep Reddy added a comment - Tried kill -3 command and we haven't got any sufficient information from that where exactly threads getting hanged. And we haven't changed any settings of servicemix. We are just using what ever the default configurations that servicemix provides. We have attached two thread dumps files for your reference purposes.
        Hide
        Thomas Termin added a comment -

        Might be interessting to see where your threads are hanging? Did you try a kill -3 to see all threads?
        How many parallel connections are allowed for the http client(http provider)?

        Show
        Thomas Termin added a comment - Might be interessting to see where your threads are hanging? Did you try a kill -3 to see all threads? How many parallel connections are allowed for the http client(http provider)?

          People

          • Assignee:
            Unassigned
            Reporter:
            Rapuru Sandeep Reddy
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development