Assertion Failed - Dump when clicking on the links from Portal for WD Comp

[Former Member]

Hi,

We have a WD Component which is integrated to the Portal . When we click on the link in the Portal for the first 2 times, the selection screen is shown correctly ( when debugged, the program stops in WDDOINIT method before the sel.screen is shown).

When we click on the link for the third or fourth time with no time gap, it shows a dump. This is the dump I am getting.

************************************************************************

Runtime Errors ASSERTION_FAILED

Date and Time 01/06/2011 10:13:58

-

---

-

---

Short text

The ASSERT condition was violated.

-

---

-

---

What happened?

In the running application program, the ASSERT statement recognized a

situation that should not have occurred.

The runtime error was triggered for one of these reasons:

- For the checkpoint group specified with the ASSERT statement, the

activation mode is set to "abort".

- Via a system variant, the activation mode is globally set to "abort"

for checkpoint groups in this system.

- The activation mode is set to "abort" on program level.

- The ASSERT statement is not assigned to any checkpoint group.

-

---

How to correct the error

Probably the only way to eliminate the error is to correct the program.

-

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"ASSERTION_FAILED" " "

"CL_NW7_VIEW_ELEMENT_ADAPTER===CP" or "CL_NW7_VIEW_ELEMENT_ADAPTER===CM004"

"DISPATCH_NW7_EVENT"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

-

---

--

-

---

User and Transaction

Client.............. 010

User................ "STECURRY"

Language Key........ "E"

Transaction......... " "

Transactions ID..... "4D250E9ADDFB00BDE10080000A041004"

Program............. "CL_NW7_VIEW_ELEMENT_ADAPTER===CP"

Screen.............. "SAPMHTTP 0010"

Screen Line......... 2

Information on Caller ofr "HTTPS" Connection:

Plug-in Type.......... "HTTPS"

Caller IP............. "10.6.4.220"

Caller Port........... 443

Universal Resource Id. "/sap/bc/webdynpro/sap/ZEM_INV_APP_ASSIGNMENTS/"

-

---

-

---

Information on where terminated

Termination occurred in the ABAP program "CL_NW7_VIEW_ELEMENT_ADAPTER===CP" -

in "DISPATCH_NW7_EVENT".

The main program was "SAPMHTTP ".

In the source code you have the termination point in line 5

of the (Include) program "CL_NW7_VIEW_ELEMENT_ADAPTER===CM004".

-

---

-

---

Source Code Extract

-

---

Line

SourceCde

-

---

1	METHOD dispatch_nw7_event.
2	DATA: l_event_handler TYPE REF TO if_wdr_nw7_event_handler.
3
4	l_event_handler = get_nw7_event_handler( i_event_handler_id ).
>>>>>	assert l_event_handler is not initial.
6
7	" View-based Delta Rendering: tracking of client events
8	raise event on_nw7_handle_event
9	exporting
10	event_handler = l_event_handler
11	event_name = i_event_name.
12
13
14	l_event_handler->handle_event(
15	i_event_name = i_event_name
16	i_event_parameters = i_event_parameters
17	i_update_data = i_update_data
18	i_event_queue = i_event_queue ).
19	ENDMETHOD.

-

---

• - I have cut the dump to make it short and clear.

****************************************************************************************************************************************

One of my colleague ran a HTTP watch trace and I am attaching it as well.

***************************************************************************************************************************************

<body> <table cellpadding="0" cellspacing="0" border="0" width="100%"> <tr> <td> <h1> Error when processing your request </h1> <br> <h2> What has happened? </h2> <p> The URL https://uswasspq.deloitte.com:/sap/bc/webdynpro/sap/ZEM_INV_APPROVER_MAIN//_{ucfLOADING was not called due to an error. </p> </td> </tr> <tr> <td> &nbsp; </td> </tr> <tr> <td class="emphasize"> <strong> Note </strong> <br> <ul> <li> The following error text was processed in the system SPQ : <b> User session (HTTP/SMTP/..) closed after timeout </b> </li> </ul> <ul> <li> The error occurred on the application server usuxc204_SPQ_01 and in the work process 1 . </li> </ul> <ul> <li> The termination type was: ERROR_MESSAGE_STATE </li> </ul> <ul> <li> The ABAP call stack was: <br> Method: PREPROCESS_REQUEST of program CL_WDR_CLIENT_ABSTRACT_HTTP===CP<BR>Method: IF_HTTP_EXTENSION}HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP<BR>Method: EXECUTE_REQUEST_FROM_MEMORY of program CL_HTTP_SERVER================CP<BR>Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME<BR>Module: %_HTTP_START of program SAPMHTTP<BR> </li> </ul> </td> </tr> <tr> <td> &nbsp; </td> </tr> <tr> <td> <p> &nbsp; </p> <h2> What can I do? </h2> <ul> <li> If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system SPQ in transaction ST22. </li> </ul> <ul> <li> If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server usuxc204_SPQ_01 in transaction SM21. </li> </ul> <ul> <li> If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 1 in transaction ST11 on the application server usuxc204_SPQ_01 . In some situations, you may also need to analyze the trace files of other work processes. </li> </ul> <ul> <li> If you do not yet have a user ID, contact your system administrator. </li> </ul> <br/> <p class="note"> Error code: ICF-IE-https -c: 010 -u: STHUGHES -l: E -s: SPQ -i: usuxc204_SPQ_01 -w: 1 -d: 20110208 -t: 131808 -v: ERROR_MESSAGE_STATE -e: User session (HTTP/SMTP/..) closed after timeout </p> <br/> <p> HTTP 500 - Internal Server Error <br/> <p> Your SAP Internet Communication Framework Team </p> </td> </tr> </table> </body> </html>

After this error a URL is called form the WebDynpro to the following html page.

https://uswasspq.deloitte.com/sap/bc/webdynpro/sap/zem_inv_approver_main/dps_Error_Page.html ( this is the friendly message we have put so that the user does not see the dump on his screen.

************************************************************************************************************************************

I tried invalidating the nodes in the WDDOEXIT at the view level but it did not help. This is a show stopper for the project to go live.

Thanks,

Guru.

[Former Member]

Please try this OSS note correction.

Note 1559475 - WDA: Short dump ASSERTION_FAILED in DISPATCH_NW7_EVENT

good luck,

Anirut W.

[Former Member]

Please try this OSS note correction.

Note 1559475 - WDA: Short dump ASSERTION_FAILED in DISPATCH_NW7_EVENT

good luck,

Anirut W.

[former_member463524]

Hi,

In the dump itself it specifies the problem with time out.

You can conatct your basis team to increase the response time.

Regards,

Meera

[former_member463524]

Hi,

In the dump itself it specifies the problem with time out.

You can conatct your basis team to increase the response time.

Regards,

Meera

[Former Member]

Hi,

We are experiencing the exact same issue. Our next plan was to open a message with SAP. Were you able identify the root cause and were you able to solve the issue?

[Former Member]

Please check this note "Note 1559475 - WDA: Short dump ASSERTION_FAILED in DISPATCH_NW7_EVENT"

It may solve your problems.

Regards

Pablo

[Former Member]

Check this thread [/thread/1301110 [original link is broken]|/thread/1301110 [original link is broken]]

[Former Member]

Check this thread [/thread/1301110 [original link is broken]|/thread/1301110 [original link is broken]]

[Former Member]

Hi Guru

Did you happen to fix this issue, I am running into the same issue in our environment ?

Can you please advice.

Thanks

Sri

[Former Member]

Hi Guru,

It is not readable the way you posted and that might be the reason that you do not get reactions.

Can you please confirm the following.

1. Is this problem occurs with out portal when you run the application standalone in SAP GUI.

2. What is going on wddoinit method or wddomodify method, any resource handling there ?