Hi, we are planing to use an esb technology in a productive application and so we have started with this topic and evaluating service mix 3.0. Therefore I have created two simple prototypes with the following components:
SA1 --- Quartz Timer (LW-SU) -> Groovy Script (LW-SU) -> XPathSplitter (EIP-SU) -> XsltComponent (LW-SU) -> ContentBasedRouter (EIP-SU) -> FileWriter (LW-SU) | SOAP Provider (HTTP-SU) SA2 --- FilePoller (LW-SU) | SOAP Consumer (HTTP-SU) -> XsltComponent (LW-SU) -> Groovy Script (LW-SU) The SA1 is reading some entries database entries in the groovy script and sends them to the SA2 endpoints (filepoller/soap endpoint), which performs an update of the job table. Both service assembies are deployed into the 'deploy' directory of the standalone container, so I use the default configuration of the servicemix 3.0 distribution. All works fine, if I send some jobs through the esb, but if I start a small load test (250 jobs) the processing stops in different steps, so I can see in a tracing component that some jobs 'hanging' e.g. in the XPathSplitter or Groovy Script Component. Only round about 30 jobs are processed successfully, the other are lost in the esb! Very strange is, that I can see files of the load test in the directory that were not processed, but if I enter a new job to the database it would be recognized and processed! So at this point of view the evaluation is collapsed, because we can not use it into a productive application. Maybe it is only a configuration problem, but I have no idea, on which screw I have to adjust. So I am thankful for each tip or hint. Stephan -- View this message in context: http://www.nabble.com/Severe-issues-while-load-testing-tf2845236s12049.html#a7945081 Sent from the ServiceMix - User mailing list archive at Nabble.com.
