There is a spring boot application that connects with a SOAP-based service. Our application has an MQ listener that receives messages from a local queue. Once a message is dequeued from that queue, it makes an API call to service.
All the communication to SOAP-based service is done via 2 way SSL.
Now we’re facing a problem while connecting with the SOAP-based service. There is a missing client certificate chain error received intermittently at the SOAP-based service end.
In our JmsConfig class, we’ve set concurrency on listener factory to 10 as highlighted below for having concurrent executions and parallel processing of messages from queue.
When we further call SOAP service from spring boot application once messages are consumed, missing client certificate chain error is coming in SOAP service logs for most of the messages. In a bulk load of 1k messages in the queue and with concurrent executions thereafter, around 850 messages failed at SOAP service end and only 150 passed.
Error is coming only while concurrency is set programmatically as shown via the above code snippet. If I comment out the setConcurrency call, all 1k messages get processed at SOAP service end without any certificate chain error.
Could you please have a look at our configuration and share some thoughts on why the concurrency is causing this error.
It's just like a fortune cookie, but instead of a cookie, it's pie. And we'll call it ... tiny ad:
Sauce Labs - World's Largest Continuous Testing Cloud for Websites and Mobile Apps