RFC hangs with a call to function module SSFC_PARSE_CERTIFICATE

[Former Member]

Hello ,

We are working on BI 7.0 SP9 .

When we try to test the RFC connection from the WAS Abap to the portal ( WAS JAVA ) using SM59 , the test is hanging but we can read in the bottom of the screen 'Connexion bcv51sf2... OK' !!!

The test connection works sometimes .

But when it’s not working , with the debug mode , I can see that the program SAPLSSFG/LSSFGU19 is hanging in the function module SSF_GET_PARAMETER with a call to the function SSFC_PARSE_CERTIFICATE

CALL FUNCTION 'SSFC_PARSE_CERTIFICATE'

EXPORTING

CERTIFICATE = PABCERT

IMPORTING

SUBJECT = STR_PROFILEID

EXCEPTIONS

SSF_KRN_ERROR = 1

SSF_KRN_NOMEMORY = 2

SSF_KRN_NOSSFLIB = 3

SSF_KRN_INVALID_PAR = 4

OTHERS = 5.

ENDIF.

ENDIF.

ENDFUNCTION.

The variable STR_PROFILEID has the value of the field ID of the table SSF_PSE_H

STR_PROFILEID =’CN=QWO, OU=XXXXX, O=YYYY, C=FR’

Due to this error , we can’t transport BI Web templates because at the end of the import in the method execution of the transport there is a call to the portal with the RFC. And the transport is hanging …

Thanks in advance for you help .

Happy new year. Milan.

[WolfgangJanzen]

I don't really understand: if function module SSFC_PARSE_CERTIFICATE returns a value (SUBJECT => STR_PROFILEID) then it does definetly not hang.

I'd recommend to report this problem to SAP (assigning component BC-SEC-SSF), providing the ability to analyse the problem in the effected system (via a remote connection).

Cheers, Wolfgang (wishing a Happy New Year 2007)

[Former Member]

Hi ,

the function module SSFC_PARSE_CERTIFICATE is hanging.

In debug mode , the variable STR_PROFILEID has the ( old ) value ’CN=QWO, OU=XXXXX, O=YYYY, C=FR’.

We will fix this issue the next year . )) .

Happy new 2007.

[WolfgangJanzen]

According to the ABAP callstack information you have provided in the customer message function module CONVERSION_EXIT_ISOLA_OUTPUT invokes function module SSF_GET_PARAMETER (in your system QWO). That is unusual - did you modify the coding of function module CONVERSION_EXIT_ISOLA_OUTPUT ?!

Cheers, Wolfgang

[Former Member]

Hi Wolfgang ,

"Versions: Function Module CONVERSION_EXIT_ISOLA_OUTPUT

-

---

Version(s) in the development database:

-

---

X activ X 700 02.02.2001 14:01:52 SAP

-

---

There are no versions in the version database."

See below the abap stack .

Stack Dep Event type Event Program Include Line

10 FUNCTION SYSTEM_CALLSTACK SAPLSYUT LSYUTU01 34

9 FORM GET_LAST_PROG SAPLCRFC LCRFCM01 5.251

8 FUNCTION RFCDISPLAY2RFCDES SAPLCRFC LCRFCU06 17

7 FORM CHECK_DESTINATION_MODIFIKATION SAPLCRFC LCRFCU05 2.976

6 MODULE (PAI) RFCDES_INPUT SAPLCRFC LCRFCU05 998

5 FUNCTION RFCDES_DISPLAY SAPLCRFC LCRFCU05 176

4 FORM EDIT SAPMCRFC SM59_FORMS 1.226

3 FORM EVENT_DOUBLE_CLICK SAPMCRFC SM59_FORMS 775

2 FORM HANDLE_USER_COMMAND SAPMCRFC SM59_FORMS 96

1 MODULE (PAI) USER_COMMAND_0100 SAPMCRFC SM59_PAI01 13

10 FUNCTION CONVERSION_EXIT_ISOLA_OUTPUT SAPLLANG LLANGU04 13

9 FORM CONVERSION_EXIT SAPCNVE SAPCNVE 107

8 EVENT SYSTEM-EXIT SAPLDSYA <SYSINI> 20

7 FUNCTION DOKU_OBJECT_EXIST SAPLDSYA LDSYAU09 43

6 FORM FILL_EXCL_TAB RSDBRUNT RSDBRUNT 5.664

5 FORM %_INIT_PBO_LAST RSDBRUNT RSDBRUNT 4.061

4 FORM INIT_PBO RSDBRUNT RSDBRUNT 3.666

3 FORM %_INIT_PBO_NEW RSRFCPIN RSRFCPIN 496

2 MODULE (PBO) %_INIT_PBO RSRFCPIN RSRFCPIN 496

1 EVENT SYSTEM-EXIT RSRFCPIN <SYSINI> 20

5 FUNCTION SSF_GET_PARAMETER SAPLSSFG LSSFGU19 206

4 FORM GET_PARAMETER SSO2GETPARAM SSO2GETPARAM 45

3 EVENT SYSTEM-EXIT RSRFCPIN <SYSINI> 20

2 FORM SEND RSRFCPIN RSRFCPIN 149

1 EVENT START-OF-SELECTION RSRFCPIN RSRFCPIN 116

Best Regards. Milan.

[Frank_Buchholz]

The version 700 02.02.2001 14:01:52 SAP of function CONVERSION_EXIT_ISOLA_OUTPUT is the current one:

FUNCTION CONVERSION_EXIT_ISOLA_OUTPUT.
*"----------------------------------------------------------------------
*"*"Lokale Schnittstelle:
*"       IMPORTING
*"             VALUE(INPUT)
*"       EXPORTING
*"             VALUE(OUTPUT)
*"----------------------------------------------------------------------
  OUTPUT = SAVE_INPUT(1) = INPUT.
  CHECK SAVE_INPUT(1) NA ' *'.
  SELECT SINGLE * FROM T002 WHERE SPRAS = INPUT.
  CHECK SY-SUBRC = 0.
  OUTPUT = T002-LAISO.
ENDFUNCTION.

I don't think that this function is in charge of the problem.

5 FUNCTION SSF_GET_PARAMETER SAPLSSFG LSSFGU19 206

      CALL FUNCTION 'SSFC_PARSE_CERTIFICATE'
        EXPORTING
          CERTIFICATE               = PABCERT
        IMPORTING
          SUBJECT                   = STR_PROFILEID
        EXCEPTIONS
          SSF_KRN_ERROR             = 1
          SSF_KRN_NOMEMORY          = 2
          SSF_KRN_NOSSFLIB          = 3
          SSF_KRN_INVALID_PAR       = 4
          OTHERS                    = 5.
    ENDIF.
  ENDIF.

ENDFUNCTION.

4 FORM GET_PARAMETER SSO2GETPARAM SSO2GETPARAM 45

  CALL FUNCTION 'SSF_GET_PARAMETER'

3 EVENT SYSTEM-EXIT RSRFCPIN <SYSINI> 20

  perform (SY-XFORM) in program (SY-XPROG).

2 FORM SEND RSRFCPIN RSRFCPIN 149

        CALL FUNCTION 'RFC_PING' DESTINATION dest

1 EVENT START-OF-SELECTION RSRFCPIN RSRFCPIN 116

    PERFORM send USING lines.

What happens if you test function SSF_GET_PARAMETER using transaction SE37 (do not change the input parameters)?

Kind regards

Frank Buchholz

[Former Member]

Hi Frank ,

See below the result of the test :

Test for function group SSFG

Function module SSF_GET_PARAMETER

-

---

-

---

Export parameters

Value

-

---

APPFOUND	<SYST>
SSFTOOLKIT	SAPSECULIB
STR_FORMAT	PKCS7
STR_PAB	/usr/sap/QWO/DVEBMGS01/sec/SAPSYS.pse
STR_PAB_PASSWORD
STR_PROFILEID	CN=QWO, OU=XXXX, O=YYYY, C=FR
STR_PROFILE	/usr/sap/QWO/DVEBMGS01/sec/SAPSYS.pse
STR_PROFILEPW
STR_HASHALG	SHA1
STR_ENCRALG	DES-CBC
B_INCCERTS	X
B_DETACHED
B_DISTRIB	X

-

---

But my problem now , it's that 1 of the 2 RFC is working fine and the other one after 1 good rfc test , is hanging now at the end of the function 'CONVERSION_EXIT_ISOLA_OUTPUT' line 14 !!!

See below the ABAP stack just before the hanging .

1 FUNCTION CONVERSION_EXIT_ISOLA_OUTPUT.

2 *"----

---

3 ""Lokale Schnittstelle:

4 *" IMPORTING

5 *" VALUE(INPUT)

6 *" EXPORTING

7 *" VALUE(OUTPUT)

8 *"----

---

9 OUTPUT = SAVE_INPUT(1) = INPUT.

10 CHECK SAVE_INPUT(1) NA ' *'.

11 SELECT SINGLE * FROM T002 WHERE SPRAS = INPUT.

12 CHECK SY-SUBRC = 0.

13 OUTPUT = T002-LAISO.

14 ENDFUNCTION.

Stack Dep Event type Event Program Include Line

10 FUNCTION CONVERSION_EXIT_ISOLA_OUTPUT SAPLLANG LLANGU04 14

9 FORM CONVERSION_EXIT SAPCNVE SAPCNVE 107

8 EVENT SYSTEM-EXIT SAPLDSYA <SYSINI> 20

7 FUNCTION DOKU_OBJECT_EXIST SAPLDSYA LDSYAU09 43

6 FORM FILL_EXCL_TAB RSDBRUNT RSDBRUNT 5.664

5 FORM %_INIT_PBO_LAST RSDBRUNT RSDBRUNT 4.061

4 FORM INIT_PBO RSDBRUNT RSDBRUNT 3.666

3 FORM %_INIT_PBO_NEW RSRFCPIN RSRFCPIN 496

2 MODULE (PBO) %_INIT_PBO RSRFCPIN RSRFCPIN 496

1 EVENT SYSTEM-EXIT RSRFCPIN <SYSINI> 20

As i said in the first post , the RFC test is hanging sometimes but now it seems that it's not hanging everytime at the same line of the abap code , if i can trust the debugger !

...and after another RFC test , now all the RFC to the portal are working ...

It seems that when it's hanging , it's at the end of the functions ( SYSTEM_CALLSTACK

or CONVERSION_EXIT_ISOLA_OUTPUT or SSF_GET_PARAMETER ) .

A memory or OS problem ?

Best Regards. Milan.

[WolfgangJanzen]

The following callstack is surprising:

5 FUNCTION SSF_GET_PARAMETER SAPLSSFG LSSFGU19 206

4 FORM GET_PARAMETER SSO2GETPARAM SSO2GETPARAM 45

3 EVENT SYSTEM-EXIT RSRFCPIN <SYSINI> 20

2 FORM SEND RSRFCPIN RSRFCPIN 149

1 EVENT START-OF-SELECTION RSRFCPIN RSRFCPIN 116

I'll check on it and then post my findings.

Cheers, Wolfgang

[WolfgangJanzen]

Hmm - that coding is only executed when you've enabled the option "send SAP logon ticket" (actually it's an "SAP Authentication Assertion Ticket" that can be requested for outbound calls). That option is available for RFC destinations of type "T" (TCP/IP connections) and type "G" (HTTP connections to External Server) - in both cases the NWAS Java is the recipient system (where you need to configure your JAAS login module stack to contain an "Assertion Ticket Evaluation" login module).

Well, Sebastian has tried to reproduce the problem in your system but did not succeed. There seem to be some weird side-effects causing the problem. We definetly need to be able to reproduce the problem in order to narrow-down the potential causes. Any additional information or brilliant idea is welcome ... (open invitation to the community).

Cheers, Wolfgang