[
https://issues.apache.org/activemq/browse/SM-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45380#action_45380
]
pratibha commented on SM-1552:
------------------------------
The whole flow is like this:
1)One application sends xml request for updating user profile to bus at
http://0.0.0.0:8193/updateUserProfile/
2)http consumer consumes the message and sends to message Enricher service
which is a bean. The bean retrieves the security subject fro the message and
attach that as a property to the message. Then it sends the message to
validateService.
3)In validationSu which is a camel Su I am validating the message against the
xsd and then sending the message to a service RService.
4)There is one more camel SU, Routing SU which takes message from RService and
sends the message to jmsProviderService which has a topic called
updateprofileTopic.
5)Once the message is successfully sent to topic, success response is sent to
client using a bean ResponseGenerator.
6)There are two jms consumerssubscribed to this topic. DirectorConsumer and
Portal Consumer. Both of them subscribes on one condition. The message is
consumed by DirectorConsumer if the userpricnciple is not director, this is
added to make sure that the message should not go to the same application which
has made the request to the bus. Similarly for Portal Consumer, if the message
is not from portal it is consumed.
7)Message from DirectorConsumer is passed to Director application
8)Message from Portal Consumer is Passed to Portal Application.
9)In Both the camel SUs I am using errorHandler and Exception to catch
exception at any time.
10)I am also intercepting the messages to identify errorrs and sending then to
errorHandler operation. This depends on the error codes that I get.
> 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.
