2457806 - The upgrade from 7.0x to a higher release is stopped due to wrong log configuration on the source AS Java

The Upgrade Process from 7.0x to 7.1 (or higher) has been stopped.

In the MTI_SAP_COM~TC~JE~LOG~CONFIGURATOR~MIGRATION_ENGINE_DATA_MC_0x.LOG SUM logs might be observed the similar entries:

==============================================

<! NAME[/usr/sap/SRA/SUM/sdt/log/SUM/MTI_SAP_COM~TC~JE~LOG~CONFIGURATOR~MIGRATION_ENGINE_DATA_MC_03.LOG]/ >

<! PATTERN[MTI_SAP_COM~TC~JE~LOG~CONFIGURATOR~MIGRATION_ENGINE_DATA_MC_03.LOG]/ >

<! FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %-40l [%t] %s: %m)]/ >

<! ENCODING[UTF8]/ >

<! LOGHEADER[END]/ >

Mar 24, 2017 8:29:41 AM com.sap.sdt.jmtx.migrationtool [Thread[main,5,main]] Info: Executing migration controller com.sap.migration.engine.log_configurator.LogConfiguratorDataController. CSN component for this controller - BC-JAS-ADM-LOG-LCF.

Mar 24, 2017 8:30:13 AM com.sap.engine.core.configuration [Thread[main,5,main]] Warning: A thread is waiting for a connection more than 30seconds. Please set the trace level to 1 (call.trace.level = 1) in the ConfigurationManager properties and restart this process to get more informations.

...

==============================================

NetWeaver AS Java 7.0 (incl. all EHPs),

NetWeaver DUAL stack (AS ABAP + AS JAVA) 7.0x,

Software Update Manager SUM

thread, waiting, connection, trace level call.trace.level, ConfigurationManager properties,  executing migration controller com.sap.migration.engine.log_configurator.LogConfiguratorDataController SUM upgrade stop , KBA , BC-JAS-ADM-LOG , Logging , BC-UPG-TLS-TLJ , Upgrade tools for Java , Problem