Hi, We are in the process of writing test cases for following ESB properties.
ClientApiNonBlocking - By default, Axis2 will spawn a new thread to handle each outgoing message. To change this behavior, remove this property from the message. Removal of this property could be vital when queuing transports like JMS are involved. ConcurrentConsumers - The minimum number of threads for message consuming. The value specified for this property is the initial number of threads started. As the number of messages to be consumed increases, number of threads are also increased to match the load until the total number of threads equals the value specified for the transport.jms.MaxConcurrentConsumers property. We are in a doubt as how to count the number of threads handling each request/response as per the definition. I did enable synapse logs to see whether it writes any thread ID in the logs but had no luck. Is there any way to identify thread IDs for each out going messages / messages consuming in ESB? Regards -- Dimuthu De Lanerolle Software Engineer WSO2 Inc. lean . enterprise . middlewear. http://wso2.com/ Tel. : +94 11 2145345 Fax : +94 11 2145300 email : [email protected]
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
