Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

error.log *INFO* [HealthCheck Default Login Accounts] org.apache.commons.httpclient.HttpMethodDirector I/O exception

Avatar

Level 1

Hello AEM Forms experienceleague community,

 

after installation of AEM Forks 6.5.0 ( Version 6.5.0, GM )  and configuration the following message fills out the  error.log:

"

D:\Adobe\Adobe_Experience_Manager_Forms\crx-repository\logs 03.05.2021 14:57:00.836 *INFO* [sling-default-2-health-com.adobe.granite.repository.hc.impl.DefaultLoginsHealthCheck] org.apache.commons.httpclient.HttpMethodDirector I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect
03.05.2021 14:57:00.836 *INFO* [sling-default-2-health-com.adobe.granite.repository.hc.impl.DefaultLoginsHealthCheck] org.apache.commons.httpclient.HttpMethodDirector Retrying request
03.05.2021 14:57:01.852 *INFO* [sling-default-2-health-com.adobe.granite.repository.hc.impl.DefaultLoginsHealthCheck] org.apache.commons.httpclient.HttpMethodDirector I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect
03.05.2021 14:57:01.852 *INFO* [sling-default-2-health-com.adobe.granite.repository.hc.impl.DefaultLoginsHealthCheck] org.apache.commons.httpclient.HttpMethodDirector Retrying request
03.05.2021 14:57:02.868 *INFO* [sling-default-2-health-com.adobe.granite.repository.hc.impl.DefaultLoginsHealthCheck] org.apache.commons.httpclient.HttpMethodDirector I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect
03.05.2021 14:57:02.868 *INFO* [sling-default-2-health-com.adobe.granite.repository.hc.impl.DefaultLoginsHealthCheck] org.apache.commons.httpclient.HttpMethodDirector Retrying request
03.05.2021 14:57:04.602 *INFO* [sling-default-1-health-org.apache.sling.discovery.oak.SynchronizedClocksHealthCheck] org.apache.sling.discovery.oak.SynchronizedClocksHealthCheck execute: no topology connectors connected to local instance.
03.05.2021 14:57:11.040 *INFO* [HealthCheck Default Login Accounts] org.apache.commons.httpclient.HttpMethodDirector I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect
03.05.2021 14:57:11.040 *INFO* [HealthCheck Default Login Accounts] org.apache.commons.httpclient.HttpMethodDirector Retrying request
03.05.2021 14:57:12.055 *INFO* [HealthCheck Default Login Accounts] org.apache.commons.httpclient.HttpMethodDirector I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect
03.05.2021 14:57:12.055 *INFO* [HealthCheck Default Login Accounts] org.apache.commons.httpclient.HttpMethodDirector Retrying request
03.05.2021 14:57:13.071 *INFO* [HealthCheck Default Login Accounts] org.apache.commons.httpclient.HttpMethodDirector I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect
03.05.2021 14:57:13.071 *INFO* [HealthCheck Default Login Accounts] org.apache.commons.httpclient.HttpMethodDirector Retrying request

 

Could someone help to solve cause of this message?  I am very new with this product and will be very thankfull to get solution for this issue.,

 

 Thanks ,

Anait

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

@AnaitKhatchikian 

JFYI- this health check does not perform any HTTP connection and these are just INFO level logs for the health check module so can be ignored. You may suppress the msgs to avoid noises in the logs, in case you don't want to disable the bundle by:

  • Go to Felix console : "/system/console/configmgr"
  • Search for Apache Sling Logging Logger Configuration
  • Click on +icon to create a new logging configuration.
  • Set Log Level to "WARN" - So that you get relevant warnings ONLY for this class- "org.apache.commons.httpclient.HttpMethodDirector"
  • Under Logger enter the classname org.apache.commons.httpclient.HttpMethodDirector
  • Save the changes

View solution in original post

5 Replies

Avatar

Employee Advisor

@AnaitKhatchikian  Check healthcheck bundle in console and it should stop this

Avatar

Correct answer by
Employee Advisor

@AnaitKhatchikian 

JFYI- this health check does not perform any HTTP connection and these are just INFO level logs for the health check module so can be ignored. You may suppress the msgs to avoid noises in the logs, in case you don't want to disable the bundle by:

  • Go to Felix console : "/system/console/configmgr"
  • Search for Apache Sling Logging Logger Configuration
  • Click on +icon to create a new logging configuration.
  • Set Log Level to "WARN" - So that you get relevant warnings ONLY for this class- "org.apache.commons.httpclient.HttpMethodDirector"
  • Under Logger enter the classname org.apache.commons.httpclient.HttpMethodDirector
  • Save the changes

Avatar

Level 1
Hello PulkitJain, Thanks für solution! In my installtion I do not have Felix console... Would it help now, after instIation, when i change settinh of org.apache.sling.commons.log.level in the file D:\Adobe\Adobe_Experience_Manager_Forms\crx-repository\launchpad\sling.properties from INFO to WARN?

Avatar

Level 1

this part of settings in D:\Adobe\Adobe_Experience_Manager_Forms\crx-repository\launchpad\sling.properties shows as following:

 

sling.fileinstall.dir=${sling.home}/install
org.apache.felix.http.shared_servlet_context_attributes=true
felix.startlevel.bundle=20
aem.jpms.java.xml={dollar}{aem.jre.java.xml},javax.xml.catalog;uses\:\="javax.xml.namespace";version\="1.0.0"
org.apache.sling.launcher.system.capabilities.extra=osgi.contract;osgi.contract\=JavaServlet;version\:Version\=" 3.1";uses\:\="javax.servlet,javax.servlet.http,javax.servlet.descriptor,javax.servlet.annotation"
sling.framework.install.startlevel=1
sling.installer.dir=${sling.launchpad}/installer
org.apache.sling.commons.log.level=INFO

Avatar

Employee Advisor
@AnaitKhatchikian You can but you are changing whole server log so any other issue that you might want to track with 'warn' will also not be shown.