ESTGlueLogger:EXCEPTION .... caused by .. SAMLBindException

This is appearing over and over in data controller log.

Any thoughts on its origin would be appreciated…

INFO | jvm 1 | 2006/02/07 14:39:18 | DEBUG [Thread : ThreadPoolWorker: Thread-67] : 2006-02-07 14:39:17.859 ESTGlueLogger:EXCEPTION:java.lang.RuntimeException: com.webmethods.caf.wsserver.auth.saml.SAMLBindException: SAML bind exception: SAMLSOAPBinding.send() caught an I/O exception (wrapped: Connection refused: connect)
INFO | jvm 1 | 2006/02/07 14:39:18 | at com.webmethods.caf.wsserver.auth.DefaultAuthInterceptor.performIntercept(DefaultAuthInterceptor.java:212)
INFO | jvm 1 | 2006/02/07 14:39:18 | at com.webmethods.caf.wsserver.auth.DefaultAuthInterceptor.intercept(DefaultAuthInterceptor.java:117)
INFO | jvm 1 | 2006/02/07 14:39:18 | at electric.soap.util.SOAPInterceptors.callInterceptors(Unknown Source)
INFO | jvm 1 | 2006/02/07 14:39:18 | at electric.soap.handlers.interceptor.SOAPInterceptorHandler.handle(Unknown Source)
INFO | jvm 1 | 2006/02/07 14:39:18 | at electric.soap.handlers.logging.SOAPLoggingHandler.handle(Unknown Source)
INFO | jvm 1 | 2006/02/07 14:39:18 | at electric.soap.handlers.setup.SetupHandler.handleRequest(Unknown Source)
INFO | jvm 1 | 2006/02/07 14:39:18 | at electric.soap.handlers.setup.SetupHandler.handle(Unknown Source)
INFO | jvm 1 | 2006/02/07 14:39:18 | at electric.soap.http.handler.HTTPToSOAP.service(Unknown Source)
INFO | jvm 1 | 2006/02/07 14:39:18 | at electric.server.http.ServletServer.service(Unknown Source)
INFO | jvm 1 | 2006/02/07 14:39:19 | at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
INFO | jvm 1 | 2006/02/07 14:39:19 | at electric.servlet.Config.service(Unknown Source)
INFO | jvm 1 | 2006/02/07 14:39:19 | at electric.servlet.HTTPContext.service(Unknown Source)
INFO | jvm 1 | 2006/02/07 14:39:19 | at electric.servlet.ServletEngine.service(Unknown Source)
INFO | jvm 1 | 2006/02/07 14:39:19 | at electric.webserver.WebServer.service(Unknown Source)
INFO | jvm 1 | 2006/02/07 14:39:19 | at electric.net.socket.SocketServer.run(Unknown Source)
INFO | jvm 1 | 2006/02/07 14:39:19 | at electric.net.socket.SocketRequest.run(Unknown Source)
INFO | jvm 1 | 2006/02/07 14:39:19 | at electric.util.thread.ThreadPool.run(Unknown Source)
INFO | jvm 1 | 2006/02/07 14:39:19 | at java.lang.Thread.run(Thread.java:534)
INFO | jvm 1 | 2006/02/07 14:39:19 | Caused by: com.webmethods.caf.wsserver.auth.saml.SAMLBindException: SAML bind exception: SAMLSOAPBinding.send() caught an I/O exception (wrapped: Connection refused: connect)
INFO | jvm 1 | 2006/02/07 14:39:19 | at com.webmethods.caf.wsserver.auth.saml.SamlUtils.getSamlResponse(SamlUtils.java:121)
INFO | jvm 1 | 2006/02/07 14:39:19 | at com.webmethods.caf.wsserver.auth.saml.SamlUtils.getSamlAssertion(SamlUtils.java:64)
INFO | jvm 1 | 2006/02/07 14:39:19 | at com.webmethods.caf.wsserver.auth.saml.SAMLAssertionValidator.validate(SAMLAssertionValidator.java:21)
INFO | jvm 1 | 2006/02/07 14:39:19 | at com.webmethods.caf.wsserver.auth.DefaultAuthInterceptor.performIntercept(DefaultAuthInterceptor.java:199)
INFO | jvm 1 | 2006/02/07 14:39:19 | … 17 more
INFO | jvm 1 | 2006/02/07 14:39:19 | Caused by: java.net.ConnectException: Connection refused: connect
INFO | jvm 1 | 2006/02/07 14:39:19 | at org.opensaml.SAMLSOAPBinding.send(Unknown Source)
INFO | jvm 1 | 2006/02/07 14:39:19 | at com.webmethods.caf.wsserver.auth.saml.SamlUtils.getSamlResponse(SamlUtils.java:117)
INFO | jvm 1 | 2006/02/07 14:39:19 | … 20 more
INFO | jvm 1 | 2006/02/07 14:39:19 |

Was this issue fixed. If so how? We are seeing the same error.

We faced same error in MWS logs while checking server status for Analytical Engine. Turns out that Analytical engine endpoint registry file is pointing to wrong MWS port. Hence reply ping from Analytical engine to MWS was not being received. Modifying this configuration has solved the issue.

Hope this will help in case of data collector issue as well.