ADS Configuration issue in HA cluster environment

[Former Member]

Hi All,

We have HA cluster environment in which we have installed primary node, secondary node and additional application server. We have configured ADS in HA cluster but when we execute "fp_test_00" program in SE38 it throws "ADS: com.adobe.ProcessingException: com.adobe.Processin(200101)" exception. As well as RFC destination "FP_ICF_DATA_<SID>" in java system throws "Error during ping operation: Error while silently connecting: org.w3c.www.protocol.http.HttpException: Connection refused: connect"  while we ping destination.

I have checked URL,Port and Logon data all information provided for RFC is fine. Please help me to resolve this issue.

Thanks

[Reagan]

You may start with this SAP note

944221 - Error analysis for problems in form processing

Regards

RB

[Former Member]

Hi Reagan,

Thanks for your reply,I have gone through thie note but I have not found any relevant information regarding my issue.

[Reagan]

Hello Sunny

The note is speaking about ADS: com.adobe.ProcessingException: com.adobe.Processin(200101)" exception. Unfortunately with that amount of information it is difficult to assist you for ADS related issues.

There are few blogs/documents available on SCN describing the ADS setup and one of them are these.

http://scn.sap.com/docs/DOC-52256

http://scn.sap.com/docs/DOC-52257

You can refer to them and see whether the ADS is configured properly.

Regards

RB

[Former Member]

Hi Reagan,

As per the SAP note 944221 i have installed and registered credentials. Please let me know what all information you require to understand this issue.

Thanks

[Matt_Fraser]

Sunny,

It would be helpful to those trying to help you if you could detail which troubleshooting steps you've already followed and what the results were.  For instance, from the Note that Reagan referenced (944221), there is a detailed logical sequence of troubleshooting steps with paths to follow based on the results of each step.  You might start from the very beginning of that Note and list the result of each step you take.

Regards,

Matt

[Matt_Fraser]

Also, perhaps it's a bit late now, but you've really put this into the wrong forum.  This is the area for problems that specifically arise when running SAP on SQL Server, but the database platform is not really relevant to the issues you are describing.  You might get more responses if you put this in or or even .  That said, though, Reagan is one of the best at these kinds of technical issues.

[Reagan]

Hello Sunny

As well as RFC destination "FP_ICF_DATA_<SID>" in java system throws "Error during ping operation: Error while silently connecting: org.w3c.www.protocol.http.HttpException: Connection refused: connect"  while we ping destination.

So the connection from the Java stack to ABAP is not working.

Check whether the destination FP_ICF_DATA_<SID> is created correctly.

It should be http://<hostname>:<HTTP_port>

Creating or Changing the Destination Service (SAP Library - Business Task Management)

If it doesn't work then check the HTTP port configured. Check the ICM trace file (dev_icm)

Regards

RB

[Former Member]

Hi Reagan

As you suggested I have checked the URL(http://hostname:8000) has been used for connection, logon data is also fine. Below I have attached dev_icm trace file and there I can see that system throwing error while "reading data from message server"

dev_icm

Thr 14116] Mon May 19 01:11:29 2014
[Thr 14116] {0000a598} Traffic Control: Nettimeout (30) exceeded by peer: 10.15.212.11:23327 [icxxthr.c 4303]

[Thr 16228] Mon May 19 03:51:29 2014
[Thr 16228] *** ERROR => MsINiRead: NiBufReceive failed (NIECONN_BROKEN) [msxxi.c      2829]
[Thr 16228]
[Thr 16228] *****************************************************************************
[Thr 16228] *
[Thr 16228] *  ERROR       Reading data from the message server (hostname / 3901)
[Thr 16228] *              failed.
[Thr 16228] *              Please check the trace file of the message server.
[Thr 16228] *
[Thr 16228] *  TIME        Mon May 19 03:51:29 2014
[Thr 16228] *  RELEASE     721
[Thr 16228] *  COMPONENT   MS (message handling interface, multithreaded)
[Thr 16228] *  VERSION     4
[Thr 16228] *  RC          -36
[Thr 16228] *  MODULE      msxxi.c
[Thr 16228] *  LINE        2848
[Thr 16228] *  COUNTER     173
[Thr 16228] *
[Thr 16228] *****************************************************************************
[Thr 16228]
[Thr 16228] *** ERROR => MsIReadFromHdl: NiRead (rc=NIECONN_BROKEN) [msxxi.c      1867]
[Thr 16228] JNCMIMsConnBrokenCallback: Message server connection broken
[Thr 16228] IcmJncmConnBrokenCallback called
[Thr 16228] JNCMReconnectAsync: Start Message Server reconnect, command MS_J2EE_RECO(2), allow 3600 sec for reconnect
[Thr 16228] JNCMReconnectAsync: Allow 30 sec for consistent cluster reconnect

[Thr 16228] Mon May 19 03:51:30 2014
[Thr 16228]
[Thr 16228] *****************************************************************************
[Thr 16228] *
[Thr 16228] *  ERROR       The connection to the specified message server
[Thr 16228] *              (hostname / 3901) failed. Please check the trace file
[Thr 16228] *              of the message server. If a network filter has
[Thr 16228] *              been activated (see message server parameters
[Thr 16228] *              ms/acl_file_...) please check the configuration
[Thr 16228] *
[Thr 16228] *  TIME        Mon May 19 03:51:30 2014
[Thr 16228] *  RELEASE     721
[Thr 16228] *  COMPONENT   MS (message handling interface, multithreaded)
[Thr 16228] *  VERSION     4
[Thr 16228] *  RC          -35
[Thr 16228] *  MODULE      msxxi.c
[Thr 16228] *  LINE        2783
[Thr 16228] *  COUNTER     176
[Thr 16228] *
[Thr 16228] *****************************************************************************
[Thr 16228]
[Thr 16228] *** ERROR => MsIAttachEx: MsINiWrite (rc=-35) [msxxi.c      884]
[Thr 16228] JNCMIMsConnBrokenCallback: Message server connection broken during reconnect
[Thr 16228] JNCMReconnectAsync: cannot reconnect to message server [cmd=MS_J2EE_RECO(2),loop=1],  rc=-35(-35)

dev_server0

[Thr 10444] Mon May 19 03:51:30 2014

M  [Thr 10444] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]

M  [Thr 6832] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 26/sock 4824

    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]

M  [Thr 19208] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 42/sock 8104

    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]

M  [Thr 4680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 50/sock 368

    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]

M  [Thr 10444] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 7128

    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]

M 

M [Thr 6832] Mon May 19 03:51:32 2014

M  [Thr 6832] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]

M 

M [Thr 19208] Mon May 19 03:51:32 2014

M  [Thr 19208] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]

M 

M [Thr 10444] Mon May 19 03:51:32 2014

M  [Thr 10444] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]

M 

M [Thr 4680] Mon May 19 03:51:32 2014

M  [Thr 4680] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]

M  [Thr 6832] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 368

    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]

M  [Thr 19208] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 27/sock 7592

    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]

M  [Thr 10444] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 43/sock 8104

    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]

M  [Thr 4680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 51/sock 4824

    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]

M 

M [Thr 6832] Mon May 19 03:51:35 2014

M  [Thr 6832] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]

M 

M [Thr 10444] Mon May 19 03:51:35 2014

M  [Thr 10444] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]

M  [Thr 10444] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 44/sock 7780

    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]

M 

M [Thr 4680] Mon May 19 03:51:35 2014

M  [Thr 4680] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]

M  [Thr 6832] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 368

    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]

M 

M [Thr 19208] Mon May 19 03:51:35 2014

M  [Thr 19208] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]

M  [Thr 4680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 52/sock 8104

    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]

M  [Thr 19208] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 28/sock 7592

    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]

M 

M [Thr 19208] Mon May 19 03:51:40 2014

M  [Thr 19208] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]

M 

M [Thr 6832] Mon May 19 03:51:40 2014

M  [Thr 6832] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]

M  [Thr 19208] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 53/sock 7128

    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]

M  [Thr 6832] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 45/sock 7952

    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]

M 

M [Thr 4680] Mon May 19 03:51:40 2014

M  [Thr 4680] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]

M 

M [Thr 10444] Mon May 19 03:51:40 2014

M  [Thr 10444] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]

M  [Thr 4680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 29/sock 4824

    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]

M  [Thr 10444] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 8508

    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]

M 

M [Thr 19208] Mon May 19 03:51:49 2014

M  [Thr 19208] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]

M 

M [Thr 10444] Mon May 19 03:51:49 2014

M  [Thr 10444] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]

M 

M [Thr 4680] Mon May 19 03:51:49 2014

M  [Thr 4680] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]

M 

M [Thr 6832] Mon May 19 03:51:49 2014

M  [Thr 6832] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]

M  [Thr 19208] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 30/sock 4824

    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]

M  [Thr 10444] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 54/sock 7592

    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]

M  [Thr 4680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 46/sock 7128

    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]

M  [Thr 6832] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 7952

    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]

Please see these logs and let me how I can resolve this issue.

[Matt_Fraser]

So what does your message server trace file show?  This will be dev_ms on your ABAP host.  Dev_icm shows an attempt to connect to the message server on port 3901, whereas 3601 would be the default.  Dev_ms will show which port the message server is actually listening on.  Are you using SSL for the message server connection?

[Former Member]

Hi Matt,

Below is the log of dev_ms

---------------------------------------------------
trc file: "dev_ms", trc level: 1, release: "721"
---------------------------------------------------

[Thr 11672] Mon Mar 31 03:54:47 2014
[Thr 11672] ms/http_max_clients = 500 -> 500
[Thr 11672] MsSSetTrcLog: trc logging active, max size = 52428800 bytes
systemid   562 (PC with Windows NT)
relno      7210
patchlevel 0
patchno    136
intno      20020600
make       multithreaded, Unicode, 64 bit, optimized
pid        11416

[Thr 11672] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 11416) [msxxserv.c   2299]
[Thr 11672] load acl file = \\HOSTNAME\sapmnt\SID\SYS\global\ms_acl_info.DAT
[Thr 11672] MsGetOwnIpAddr: my host addresses are :
[Thr 11672]   1 : [IP-ADDRESS] PRIMARY_NODE_HOSTNAME.corp.ad.company.com (HOSTNAME)
[Thr 11672]   2 : [127.0.0.1] PRIMARY_NODE_HOSTNAME.corp.ad.company.com (LOCALHOST)

[Thr 11672] Mon Mar 31 03:54:55 2014
[Thr 11672]   3 : [IP-ADDRESS] IP-ADDRESS (NILIST)

[Thr 11672] Mon Mar 31 03:54:59 2014
[Thr 11672]   4 : [IP-ADDRESS] HOSTNAME (NILIST)

[Thr 11672] Mon Mar 31 03:55:04 2014
[Thr 11672]   5 : [IP-ADDRESS] HOSTNAME-L1 (NILIST)

[Thr 11672] Mon Mar 31 03:55:09 2014
[Thr 11672]   6 : [IP-ADDRESS] HOSTNAME-C1 (NILIST)
[Thr 11672]   7 : [IP-ADDRESS] PRIMARY_NODE_HOSTNAME.corp.ad.company.com (NILIST)
[Thr 11672] MsHttpInit: full qualified hostname = PRIMARY_NODE_HOSTNAME.corp.ad.company.com
[Thr 11672] HTTP logging is switch off
[Thr 11672] MsHttpOwnDomain: own domain[1] = corp.ad.company.com
[Thr 11672] *** I listen to port 3600 (3600) ***
[Thr 11672] *** I listen to internal port 3900 (3900) ***
[Thr 11672] CUSTOMER KEY: >O1431865683<
[Thr 11672] build version=721.2013.08.20
[Thr 11672] LOGIN: PRIMARY_NODE_HOSTNAME_SID_00 [IP-ADDRESS] (DIA UPD ENQ BTC UP2 )

[Thr 11672] Mon Mar 31 04:03:13 2014
[Thr 11672] LOGOUT: PRIMARY_NODE_HOSTNAME_SID_00 [IP-ADDRESS] (DIA UPD ENQ BTC UP2 )
[Thr 11672] MsSExit: received SIGINT (2)
[Thr 11672] ***LOG Q02=> MsSHalt, MSStop (Msg Server 11416) [msxxserv.c   7792]

Please let me know if you need any other information

[Matt_Fraser]

This logfile is from March 31 (is this the most recent log?), and shows the message server shutting down a few minutes after starting up.  It would seem that your message server isn't running, and hasn't been since March 31, which is a problem.  How are you even able to logon to your ABAP host to run SE38?  It also shows that it is using the standard ports 3600 and 3900 for external and internal communication, respectively, so your instance number is 00, and that the ICM is not running on this same instance.  The ICM trace indicated that the ICM was connecting to a gateway with an instance number of 01, so I'm guessing here, but I think you have two different instances running on the cluster (perhaps on the different nodes?) for the same system, and you have message server on one instance and ICM on the other. 

I get a little hazy here, because we don't use clustering at my site, so I don't have a lot of direct experience with it.  However, I'm thinking two things:  first, that the ICM is perhaps looking for a message server on the wrong port, because it's thinking it will be on instance 01, which it isn't; second, that the message server is shutting down shortly after startup, although no actual error is shown, so something external appears to be triggering the shutdown.  If the message server is not running, that's the first problem to solve.

Ok, time for another log to investigate:  dev_disp.  Also, it may not hurt to post your instance profile(s), and perhaps default and start profiles, just to help us understand your environment better.  I commend you on all the editing out of your hostnames and IP addresses, but I have to admit it's making it hard to follow which system's logs we're looking at.

[Former Member]

Sunny,

Below note fixes your issue

1105975 - org.omg.CORBA.COMM_FAILURE: Could not connect to host

Thanks

Manikiran C