Question
American Express Services Europe Ltd
GB
Last activity: 30 Oct 2018 10:09 EDT
Unable to import jar file - getting bad request
Hello,
I am trying to import a jar file of size 220MB into upgraded version of Pega 7.3.
after uploading successfully (can see the percentage bottom left corner in Chrome browser) getting the bad request.
also i can't see the file later when i open the wizard and click next i can't see the imported jar file. Is there a place where we can increase the session timeout please?
Below is the error coming after file upload. User session still exist. but the import wizard tab getting this error.
Bad Gateway
The proxy server received an invalid response from an upstream server.
Thanks,
Veera
***Updated by moderator: Lochan to add Categories***
Accepted Solution
Pegasystems Inc.
US
Hi,
As suggested by my colleague Asif, you can modify the prconfig.xml. Also, how are you trying to import the zip file?
I mean there are various ways in which this can be achieved.We can make use of System Management API for that purpose. Also, we can import using prpcServiceUtils.properties or you can directly use prpcUtils.properties(which will directly operate on Database) from Command LIne. Please refer
Please refer to below post.
https://community.pega.com/sites/default/files/help_v731/procomhelpmain.htm command
Regards,
Rachit
EPAM Systems, Inc.
ES
Hi Veera,
Thanks for posting on PSC.
Bad Gateway exception could occur due to multiple reasons, though your guess could be correct in this case about the timeout.
It occurs when,
- The web application did not respond in time and the request from Apache timed out.
- One server on the internet received an invalid response from another server.
Or other probable reasons, to investigate more please share complete PegaRULES and App Server logs to analyze.
Usually, Pega supports 1 GB import by default and in your case, it's much lesser. To avert this, you can either of below:-
- DSS configuration:-
OOTB pyMaxDragDropAttachSizeMB System Setting. Copy it to your own application ruleset and configure with required value.
Reference:-https://collaborate.pega.com/question/max-file-upload-size-using-dynamic-system-setting
- Modify prconfig.xml -
Hi Veera,
Thanks for posting on PSC.
Bad Gateway exception could occur due to multiple reasons, though your guess could be correct in this case about the timeout.
It occurs when,
- The web application did not respond in time and the request from Apache timed out.
- One server on the internet received an invalid response from another server.
Or other probable reasons, to investigate more please share complete PegaRULES and App Server logs to analyze.
Usually, Pega supports 1 GB import by default and in your case, it's much lesser. To avert this, you can either of below:-
- DSS configuration:-
OOTB pyMaxDragDropAttachSizeMB System Setting. Copy it to your own application ruleset and configure with required value.
Reference:-https://collaborate.pega.com/question/max-file-upload-size-using-dynamic-system-setting
- Modify prconfig.xml -
Open prconfig.xmlin a text editor or XML editor and add the following entry (in this example, 2 GB):
<env name="Initialization/MaximumFileUploadSizeMB" value="2048" />
Reference- https://docs-previous.pega.com/how-import-large-archive-zip-files-using-import-gadget
Other userful link:-https://community.pega.com/sites/default/files/help_v72/procomhelpmain.htm
I couldn't find any relevant docs of the reported issue occuring due to sssion timeout, so not sure about it.
Hope it helps, kindly notify by marking this post as answered for tracking purpose.
Regards,
Asif
or configure DSS settings(You can alter Copy "pyMaxDragDropAttachSizeMB" into your ruleset and set it to the same value as the DSS).
American Express Services Europe Ltd
GB
Hi Asif,
Thanks for your quick response.
I can see the file size limit is fine (its 1000MB) in system settings. I noticed if is crosses 120 seconds getting the bad request.
There should be some setting but i am not able to recall it. I was able to manage to upload a file which is 20MB.
Unfortunately i can't split the rulesets as well because one ruleset itself having 17000 rules where the size is coming around 120MB.
Thanks,
Veera
Accepted Solution
Pegasystems Inc.
US
Hi,
As suggested by my colleague Asif, you can modify the prconfig.xml. Also, how are you trying to import the zip file?
I mean there are various ways in which this can be achieved.We can make use of System Management API for that purpose. Also, we can import using prpcServiceUtils.properties or you can directly use prpcUtils.properties(which will directly operate on Database) from Command LIne. Please refer
Please refer to below post.
https://community.pega.com/sites/default/files/help_v731/procomhelpmain.htm command
Regards,
Rachit
American Express Services Europe Ltd
GB
Thanks for your reply.
The way we imported the file is an usual way developers import the jar file. Designer studio - Application - Distribution - Import.
We will try the other import option using prpc utilities and will update.
Thanks,
Veera
American Express Services Europe Ltd
GB
Sure will try this option. As this is our test environment we required to submit some RFC to copy and update the properties file.
I will update once i tried this. Thanks for your comments.
American Express Services Europe Ltd
GB
Hi All,
We are able to import product file using utilities script.
Thanks for your comments.
Thanks,
Veera
Bank of America
US
Hi Veera Saddala,
If you are using prpcutils successfully for PEGA7.3 version deployments , can you please give the properties file that you are using and also let me know if you did any changes in any file in prpcutils, I will try comparing your template, because my deployments are filing randomly.
Thanks
Ravi Kumar