Hi, I have been able to successfully call an HTTPS-based webservice.
A couple of seconds after the successful termination of the SequenceMediator, the CPU utilization of the ESB process augments to 100% and I am forced to stop the ESB Windows Service. The log file contains a huge amount of "SSLIOSession I/O session 2 [interested ops: [r]; ready ops: [r]][SSL handshake status: NEED_WRAP][0][0][0][0]: -1 bytes read" messages. This kind of message is added continuously to the log file leading to the 100% CPU. Underneath you'll find an extract of the log file: 2008-03-11 12:44:32,352 [192.168.13.175-INFOR2] [HttpClientWorker-1] DEBUG SequenceMediator End : Sequence <anonymous> 2008-03-11 12:44:47,258 [192.168.13.175-INFOR2] [I/O dispatcher 3] DEBUG SSLIOSession I/O session 2 [interested ops: [r]; ready ops: [r]][SSL handshake status: NEED_WRAP][0][0][0][0]: -1 bytes read 2008-03-11 12:44:47,258 [192.168.13.175-INFOR2] [I/O dispatcher 3] DEBUG SSLIOSession I/O session 2 [interested ops: [r]; ready ops: [r]][SSL handshake status: NEED_WRAP][0][0][0][0]: Close I would be pleased if someone could have a look at this issue. Regards, Stefan Lecho. -- View this message in context: http://www.nabble.com/ESB-uses-100--of-CPU-tp15977377p15977377.html Sent from the WSO2 ESB Users mailing list archive at Nabble.com. _______________________________________________ Esb-java-user mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
