Quantcast
Channel: SCN : All Content - Web Dynpro ABAP
Viewing all articles
Browse latest Browse all 3667

CX_FQDN error uncaught_exepction

$
0
0

Hi ,

 

I am executing my webdynpro application from se80 , getting cx_fqdn uncaught_exception error .

 

I have changed the profile from RZ10 ( INSTANACE PROFILE ) set saplocalhost = sapserver, saplocalhostfull = sapserver,

icm/host_name_full = sapserver .

 

I have restarted the application server 3/4 times . I can see the profile details thru RZ11 for the same.

 

When I debug the application by external debugger , gets error at method check , line no. 10.

 

It shows lv_host = sapserver , lv_port = 8001 . , at line split lv_host at ':' into lv_host lv_port ,

 

it raise exception type cx_fqdn . How to avoid this exception . My lv_host = sapserver and port = 8001 . Is this wrong port or hot name ?

 

Please guide me to resolve this .

 

Details screen shot :

 

The URL http://sapserver:8001/sap/bc/webdynpro/sap/zz_00_sflight was not called due to an error.

Note

u2022     The following error text was processed in the system DM0 : Die URL enthält keine vollständige Domainangabe (sapserver statt sapserver.).

u2022     The error occurred on the application server sapserver_DM0_01 and in the work process 0 .

u2022     The termination type was: RABAX_STATE

u2022     The ABAP call stack was:

Method: CHECK of program CX_FQDN=======================CP

Method: LATE_CONSTRUCTOR of program CL_WDR_UCF====================CP

Method: HANDLE_REQUEST of program CL_WDR_UCF====================CP

Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP

Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP

Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME

Module: %_HTTP_START of program SAPMHTTP

What can I do?

u2022     If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system DM0 in transaction ST22.

u2022     If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server sapserver_DM0_01 in transaction SM21.

u2022     If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server sapserver_DM0_01 . In some situations, you may also need to analyze the trace files of other work processes.

u2022     If you do not yet have a user ID, contact your system administrator.

Error code: ICF-IE-http -c: 800 -u: SAPUSER -l: E -s: DM0 -i: sapserver_DM0_01 -w: 0 -d: 20090818 -t: 160133 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION

HTTP 500 - Internal Server Error

Your SAP Internet Communication Framework Team

 

 

Best Regards

Milind Nikumbh.

 


Viewing all articles
Browse latest Browse all 3667

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>