on 05-26-2008 10:01 AM
Hello,
when I try to check in a big document (in my case I made my own document which is about 100 MB) in cProjects the current cProject webpage turns to "This page could not be displayed...".
The exact path where I tried to check in the document is:
Projects -> Structure -> Documents -> New Document
To see if its an abap coding error I set a breakpoint at Web Dynpro Comp. "DPR_Document" View: "VI_UPLOADDETAIL" Method: "ONACTIONUPLOAD". Further I tried it in the Method "new_doc_create( )" of the component-controller.
The point is:
The abap coding which is called if you click on the "Check in"-button is NOT called if the document is about 100 or more MB. (I don't tried it with smaller documents e.g. 60 MB, but never mind about this because document with a size of 100 or more MB should work too.)
Furthermore I had a look at the trace file which can be found at SMICM -> Goto -> Trace File -> Display All. Every time I tried to check in such a big document three error messages appear there with the following content:
[Thr 1396738992] *** ERROR => request too big {00047108} [http_plg_mt.c 1969]
[Thr 1396738992] Address Offset REQUEST:
[Thr 1396738992]
[Thr 1396738992] 0x4d78895c 000000 504f5354 202f7361 702f6263 2f776562 POST /sap/bc/web
[Thr 1396738992] 0x4d78896c 000016 64796e70 726f2f73 61702f63 70726f6a dynpro/sap/cproj
[Thr 1396738992] 0x4d78897c 000032 65637473 2f3f7361 702d636f 6e746578 ects/?sap-contex
[Thr 1396738992] 0x4d78898c 000048 7469643d 53494425 xxxxxxxx xxxx2533 tid=SID%xxxxxx%3
[Thr 1396738992] 0x4d78899c 000064 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxxxxxxxx%3
[Thr 1396738992] 0x4d7889ac 000080 6130314f 4e6d6551 61724445 767a6978 a01ONmeQarDEvzix
[Thr 1396738992] 0x4d7889bc 000096 525a7a45 48536763 58637863 76325738 RZzEHSgcXcxcv2W8
[Thr 1396738992] 0x4d7889cc 000112 45786f73 302d5835 6a2d4e45 57204854 Exos0-X5j-NEW HT
[Thr 1396738992] 0x4d7889dc 000128 54502f31 2e310d0a 61636365 70743a20 TP/1.1..accept:
[Thr 1396738992] 0x4d7889ec 000144 696d6167 652f6769 662c2069 6d616765 image/gif, image
[Thr 1396738992] 0x4d7889fc 000160 2f782d78 6269746d 61702c20 696d6167 /x-xbitmap, imag
[Thr 1396738992] 0x4d788a0c 000176 652f6a70 65672c20 696d6167 652f706a e/jpeg, image/pj
[Thr 1396738992] 0x4d788a1c 000192 7065672c 20617070 6c696361 74696f6e peg, application
[Thr 1396738992] 0x4d788a2c 000208 2f782d73 686f636b 77617665 2d666c61 /x-shockwave-fla
[Thr 1396738992] 0x4d788a3c 000224 73682c20 6170706c 69636174 696f6e2f sh, application/
[Thr 1396738992] 0x4d788a4c 000240 766e642e 6d732d65 7863656c 2c206170 vnd.ms-excel, ap
[Thr 1396738992]
[Thr 1398135728] Mon May 26 09:19:17 2008
[Thr 1398135728] *** ERROR => request too big {00087109} [http_plg_mt.c 1969]
[Thr 1398135728] Address Offset REQUEST:
[Thr 1398135728]
[Thr 1398135728] 0x4d7688ec 000000 504f5354 202f7361 702f6263 2f776562 POST /sap/bc/web
[Thr 1398135728] 0x4d7688fc 000016 64796e70 726f2f73 61702f63 70726f6a dynpro/sap/cproj
[Thr 1398135728] 0x4d76890c 000032 65637473 2f3f7361 702d636f 6e746578 ects/?sap-contex
[Thr 1398135728] 0x4d76891c 000048 7469643d 53494425 xxxxxxxx xxxx2533 tid=SID%xxxxxx%3
[Thr 1398135728] 0x4d76892c 000064 xxxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxxxxxxxx%3
[Thr 1398135728] 0x4d76893c 000080 6130314f 4e6d6551 61724445 767a6978 a01ONmeQarDEvzix
[Thr 1398135728] 0x4d76894c 000096 525a7a45 48536763 58637863 76325738 RZzEHSgcXcxcv2W8
[Thr 1398135728] 0x4d76895c 000112 45786f73 302d5835 6a2d4e45 57204854 Exos0-X5j-NEW HT
[Thr 1398135728] 0x4d76896c 000128 54502f31 2e310d0a 61636365 70743a20 TP/1.1..accept:
[Thr 1398135728] 0x4d76897c 000144 2a2f2a0d 0a726566 65726572 3a206874 */*..referer: ht
[Thr 1398135728] 0x4d76898c 000160 74703a2f xxxxxxxx xxxxxxxx 7764662e tp://xxxxxx.wdf.
[Thr 1398135728] 0x4d76899c 000176 7361702e 636f7270 3a353030 36362f73 sap.corp:50066/s
[Thr 1398135728] 0x4d7689ac 000192 61702f62 632f7765 6264796e 70726f2f ap/bc/webdynpro/
[Thr 1398135728] 0x4d7689bc 000208 7361702f 6370726f 6a656374 732f3f73 sap/cprojects/?s
[Thr 1398135728] 0x4d7689cc 000224 61702d63 6f6e7465 78746964 3d534944 ap-contextid=SID
[Thr 1398135728] 0x4d7689dc 000240 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx %xxxxxx%xxxxxxxx
[Thr 1398135728]
[Thr 1395682224] Mon May 26 09:19:18 2008
[Thr 1395682224] *** ERROR => request too big {0008710c} [http_plg_mt.c 1969]
[Thr 1395682224] Address Offset REQUEST:
[Thr 1395682224]
[Thr 1395682224] 0x4d7688ec 000000 504f5354 202f7361 702f6263 2f776562 POST /sap/bc/web
[Thr 1395682224] 0x4d7688fc 000016 64796e70 726f2f73 61702f63 70726f6a dynpro/sap/cproj
[Thr 1395682224] 0x4d76890c 000032 65637473 2f3f7361 702d636f 6e746578 ects/?sap-contex
[Thr 1395682224] 0x4d76891c 000048 7469643d 53494425 xxxxxxxx xxxx2533 tid=SID%xxxxxx%3
[Thr 1395682224] 0x4d76892c 000064 xxxxxxxx xxxxxxxx xxxxxxxx xxxx2533 xxxxxxxxxxxxxx%3
[Thr 1395682224] 0x4d76893c 000080 6130314f 4e6d6551 61724445 767a6978 a01ONmeQarDEvzix
[Thr 1395682224] 0x4d76894c 000096 525a7a45 48536763 58637863 76325738 RZzEHSgcXcxcv2W8
[Thr 1395682224] 0x4d76895c 000112 45786f73 302d5835 6a2d4e45 57204854 Exos0-X5j-NEW HT
[Thr 1395682224] 0x4d76896c 000128 54502f31 2e310d0a 61636365 70743a20 TP/1.1..accept:
[Thr 1395682224] 0x4d76897c 000144 2a2f2a0d 0a726566 65726572 3a206874 */*..referer: ht
[Thr 1395682224] 0x4d76898c 000160 74703a2f 2fxxxxxx xxxxxxxx xxxx662e tp://xxxxxx.wdf.
[Thr 1395682224] 0x4d76899c 000176 7361702e 636f7270 3a353030 36362f73 sap.corp:50066/s
[Thr 1395682224] 0x4d7689ac 000192 61702f62 632f7765 6264796e 70726f2f ap/bc/webdynpro/
[Thr 1395682224] 0x4d7689bc 000208 7361702f 6370726f 6a656374 732f3f73 sap/cprojects/?s
[Thr 1395682224] 0x4d7689cc 000224 61702d63 6f6e7465 78746964 3d534944 ap-contextid=SID
[Thr 1395682224] 0x4d7689dc 000240 2533xxxx xxxxxxxx 33xxxxxx xxxxxxxx %xxxxxx%3xxxxxxx
[Thr 1395682224]
As you can see this error sais that the request is too big. A look into the coding of this cProjects webpage (where you can check in documents (look above)) the document is sent with the http method POST. Usually every webserver has an option where you can restrict the size for uploading files. But in that case the won't be an error out of a piece of c-coding (-> http_plg_mt.c).
Has anybody have an idea about a solution?
Edited by: Johannes Gilbert on May 26, 2008 12:25 PM
The first step to be able to upload files larger than 100 MB you have to change the profil parameter "icm/HTTP/max_request_size_KB". You won't be able to change it via RZ11. To have a change a system administrator has to change the value and restart the system.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
this is handled by the profile parameters of the R/3 System. Look at
icm/HTTP/max_request_size_KB or something like this.
Best regards, Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
10 | |
5 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.