2142843 - load-balanced Java - badKey and No endpoint with name - SAP Work Manager 6.1 - SMP 3.0 SP04 Agentry: | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2142843 - load-balanced Java - badKey and No endpoint with name - SAP Work Manager 6.1 - SMP 3.0 SP04 Agentry:

Symptom

  • SAP Load balance Java connection
  • Recently started using SMP 3.0 SP 04 for Work Manager-based app development
  • The app starts up fine if we use the USER_AUTH logon method in the javaBE.ini but has a problem when the LOGON_METHOD uses: USER_AUTH_GROUP

~~~~~~~~events.log~~~~~~~~~~~~

03/10/2015 17:42:11, 0,        21,       150, Thr       4800, Loading Development application definitions
03/10/2015 17:42:42, 1,         3,         9, Thr       4800, HTTPXML-2, Chickaming HTTPXML, xmlAllowXSLTScript, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey
03/10/2015 17:42:42, 1,         3,         9, Thr       4800, HTTPXML-2, Chickaming HTTPXML, xmlResolveExternals, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey
03/10/2015 17:42:42, 1,         3,         9, Thr       4800, HTTPXML-2, Chickaming HTTPXML, xmlValidateOnParse, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey
03/10/2015 17:42:42, 0,        24,         4, Thr       4800, Loaded HTTP-XML Back End (HTTPXML v7.0.4.17) from ag3httpxmlbe.dll
03/10/2015 17:42:42, 1,         3,         9, Thr       4800, Java-1, Chickaming Java, initialHeapSize, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey
03/10/2015 17:42:42, 1,         3,         9, Thr       4800, Java-1, Chickaming Java, maxHeapSize, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey
03/10/2015 17:42:42, 1,         3,         9, Thr       4800, Java-1, Chickaming Java, reduceOSSignalUse, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey
03/10/2015 17:42:45, 1,        20,        18, Thr       4800, JAVA EXCEPTION CAUGHT: com.syclo.agentry.AgentryException: For input string: ""

~~~~~~~~~~end~~~~~~~~~~~~~~~

~~~~~~~servername-smp-server.log~~~~~~

 400#INFO#System.out##anonymous#SMPServerStatusManager###SMPServerStatusManager: The SMP server has initialized and is ready. |
2015 03 10 17:46:32#0-400#WARN#com.sap.mobile.platform.server.proxy.configuration.service.AbstractEndpointConfigurationService##anonymous#http-bio-8084-exec-2####null#null#null#warn#Proxy#smpAdmin#null#d8b8cb3a-465f-4788-be05-50da11874d81#null#1426038392744#null#com.sap.mobile.platform.server.proxy.configuration.service.AbstractEndpointConfigurationService:getEndpoint#No endpoint with name com.sap.agentry.<YourAppID> was found#null#667#null#0#null |
2015 03 10 17:46:32#0-400#WARN#com.sap.mobile.platform.server.proxy.configuration.service.AbstractEndpointConfigurationService##anonymous#http-bio-8084-exec-2####null#null#null#warn#Proxy#smpAdmin#null#d8b8cb3a-465f-4788-be05-50da11874d81#null#1426038392781#null#com.sap.mobile.platform.server.proxy.configuration.service.AbstractEndpointConfigurationService:getEndpoint#No endpoint with name com.sap.agentry.<YourAppID> was found#null#667#null#1#null |

~~~~~~~~~~~~end~~~~~~~~~~~~~~~~~


Read more...

Environment

SAP Work Manager 6.1

Product

SAP Work Manager 6.1.0

Keywords

Startup, SMP3.0, SAPWM , KBA , MOB-SYC-SAP , Syclo Mobility for SAP backend , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.