[
https://issues.apache.org/activemq/browse/SM-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45452#action_45452
]
pratibha commented on SM-1552:
------------------------------
One more thing I found that it is not the ResponseGenerator bean which causes
problem. But When I put two beans in an operation that time it hangs.
I tried increasing the thread pool like this:
servicemix.corePoolSize = 60
servicemix.maximumPoolSize = 100
servicemix.queueSize = 256
Still it hangs
> the operation hangs while load testing
> --------------------------------------
>
> Key: SM-1552
> URL: https://issues.apache.org/activemq/browse/SM-1552
> Project: ServiceMix
> Issue Type: Bug
> Reporter: pratibha
> Attachments: common.zip, errorhandler-sa-1.0.jar, smxesb.properties,
> updateprofile.zip
>
>
> When I hit request for updating user profile:
> <request xmlns="http://www.finicity.com";>
> <updateUserProfile>
> <userName>appuser1</userName>
> <firstName>pratibha</firstName>
> <lastName>ghogale</lastName>
> <emailAddress>[EMAIL PROTECTED]</emailAddress>
> </updateUserProfile>
> </request>
> This works only for 15 parallel requests. If I give more than that it always
> throws Exchange not found.
> I use following thread pool configuration:
> servicemix.corePoolSize = 16
> servicemix.maximumPoolSize = 32
> servicemix.queueSize = 256
> I have attached two files three files:
> 1)updateprofile-sa-1.0.jar : Put it in servicemix-3.2.2/hotdeploy
> 2)errorhandler-sa-1.0.jar: Put it in servicemix-3.2.2/hotdeploy
> 3)smxesb.properties : Put it in servicemix-3.2.2/conf
> Here updateprofile-sa-1.0.jar is the jar for updating user profile. If any
> error occurs during update profile it send message to jms queue created in
> other operation created by errorhandler-sa-1.0.jar. smxesb.properties is
> used only for configuring the URLs.
> For update profile I use http://0.0.0.0:8193/updateUserProfile/
> The request for update profile is sent to two applications which are
> configured in http-ptovider Su. The addresses are
> director.url =
> http://192.168.2.64:8080/webapp/control/httpEsbEvent
> portal.url =
> http://192.168.2.71/index.php?option=com_finicityapirequest&task=esbrequest
> You can change these addresses.
> Also I am using BASIC authentication and authorization:
> The users are as follows:
> director=directorpass
> portal=portalpass
> qa=qapass
> Hit the request with qa as user. That is qa user is hitting a request
> updateprofile for enduser appuser1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
