Back to Ideas
12
Like
Follow Idea
For large espaces, increase default size maximum
3600Views
17Comments
Implemented
Service Studio
Development Environment Release 49

Every time I update Service Studio, I have to go into the "ServiceStudio.WS.bindings.config" file and replace the default maxbuffersize, maxbufferpoolsize, and maxreceivedmessagesize of 33554432 to a higher value that actually works.


I think we can all agree that the default of 33MB is pretty small by today's standard of technology.

  1. Please increase the default when deploying new versions of Service Studio to something useful.
  2. Additionally, a more friendly error message would also be useful for diagnosing this situation.

-Yes, if I click send report, then click view I can figure it out, but that's probably a bit much for more novice users, or someone who has never experienced this exact error before.




Also, including the actual body of part of the error report in case someone does a search, so they find this thread:


Communication error: There was an error contacting 'some-server.com' .

Operations Log:
    [8/24/2015 8:22:04 AM] [3] Notification        SS_Error|||0|0|0|2015-08-24T12:22:04.820
    [8/24/2015 8:22:04 AM] [3] Exception           OutSystems.Communication.Exceptions.CommunicationException: The maximum message size quota for incoming messages (33554432) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element. ---> System.ServiceModel.CommunicationException: The maximum message size quota for incoming messages (33554432) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element. ---> System.ServiceModel.QuotaExceededException: The maximum message size quota for incoming messages (33554432) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element.
   --- End of inner exception stack trace ---

OSerror.png
24 Aug 2015
Copy link to comment
2016-04-21 20-09-55
J.
 
MVP
depends what 33Mb is about.

a simple textfile.. i say it's large.
an espace, well, I never get above the 10Mb.
It's also about having a good architecture?

24 Aug 2015
Copy link to comment
You set the MaxReceivedMessageSize property via the server config file, this should solve your problem.

25 Aug 2015
Copy link to comment
Ah You already figured it out, the feature request is to increase the default MaxReceivedMessageSize :)
25 Aug 2015
Copy link to comment
Hi Rober,

I have the same issue, could you please explain to me how can i increase the MaxReceviedMessageSize?

Thanks

Simone
13 May 2016
Copy link to comment

I have the same situation here  with  every  update.

You can find a workaround here: https://www.outsystems.com/forums/discussion/13180/error-maximum-message-size/

TL;DR
c:\Program files\OutSystems\Development Environment 10.0\ServiceStudio.WS.bindings.config
Replace all occurrences of "33554432" with "2147483647"

16 Apr 2018
Copy link to comment

33 MB is filled very fast if you use some animated gifs in your app. And the rest doesn't help to make stuff smaller

23 May 2018
Copy link to comment
2022-07-06 03-36-19
Hanno
 
MVP

Not sure if the path changed recently, but the config file for me was located at:
C:\Program Files\OutSystems\Development Environment 10.0\Service Studio\ServiceStudio.WS.bindings.config

10 Jul 2018
Copy link to comment

It has to do where you have installed Outsystems

14 Nov 2018
Copy link to comment
2022-07-06 03-36-19
Hanno
 
MVP
Merged this idea with 'On a SeviceStudio upgrade, preserve or ask to preserve *.conf files' (created on 11 Mar 2019 16:10:07 by erik berg)
03 Oct 2019
Copy link to comment

When a new version of ServiceStudio is installed as an upgrade, all of the *.conf files are replaced.  There should be a on option to ask if you want the *.conf files be replaced or preserved.  The ServiceStudio.WS.bindings.conf file in particular is a sore spot as this file does not have proper values in it for any project that has large amount of data in its espace.



This comment was:
- originally posted on idea 'On a SeviceStudio upgrade, preserve or ask to preserve *.conf files' (created on 11 Mar 2019 by erik berg)
- merged to idea 'For large espaces, increase default size maximum' on 03 Oct 2019 12:07:20 by Hanno
11 Mar 2019
Copy link to comment
2014-02-07 17-02-43
Vasco Pessanha

Hey Erik,

What would be the problem of overriding/replacing this conf files? 

Cheers,



This comment was:
- originally posted on idea 'On a SeviceStudio upgrade, preserve or ask to preserve *.conf files' (created on 11 Mar 2019 by erik berg)
- merged to idea 'For large espaces, increase default size maximum' on 03 Oct 2019 12:07:20 by Hanno
18 Mar 2019
Copy link to comment

The problem with replacing the file is it overrides all the custom configuration changes that I previously was  required to make to get ServiceStudio to publish without a failure.

The configuration files are actually in the wrong windows folder as well.  Configuration files should not be in Program Files but in Program Data or a User based directory.  Depending on the client and their security, I might not even have access to change these configuration files after an upgrade.

Once you get burned by the configuration files being blindly overwritten a few times, you start to put off upgrading ServiceStudio because of the pain that it causes.



This comment was:
- originally posted on idea 'On a SeviceStudio upgrade, preserve or ask to preserve *.conf files' (created on 11 Mar 2019 by erik berg)
- merged to idea 'For large espaces, increase default size maximum' on 03 Oct 2019 12:07:20 by Hanno
18 Mar 2019
Copy link to comment
2014-02-07 17-02-43
Vasco Pessanha

Thanks for the feedback Erik,

I'll forward this to the team responsible for the upgrade.

What version are you using?

Cheers,



This comment was:
- originally posted on idea 'On a SeviceStudio upgrade, preserve or ask to preserve *.conf files' (created on 11 Mar 2019 by erik berg)
- merged to idea 'For large espaces, increase default size maximum' on 03 Oct 2019 12:07:20 by Hanno
19 Mar 2019
Copy link to comment
Changed the category to
Service Studio


This comment was:
- originally posted on idea 'On a SeviceStudio upgrade, preserve or ask to preserve *.conf files' (created on 11 Mar 2019 by erik berg)
- merged to idea 'For large espaces, increase default size maximum' on 03 Oct 2019 12:07:20 by Hanno
11 Jun 2019
Copy link to comment
2022-07-06 03-36-19
Hanno
 
MVP

This is becoming a big disruption and time waster with the auto-update feature enabled. You only realise something has changed/new version has been installed when you try and open a big eSpace. 

Having to now halt your train of thought, close SS, change the config file, and then re-open your work is very disruptive and costly in terms of developers getting their train of thought back up to speed.



This comment was:
- originally posted on idea 'On a SeviceStudio upgrade, preserve or ask to preserve *.conf files' (created on 11 Mar 2019 by erik berg)
- merged to idea 'For large espaces, increase default size maximum' on 03 Oct 2019 12:07:20 by Hanno
03 Oct 2019
Copy link to comment
2022-07-06 03-36-19
Hanno
 
MVP
08 Jan 2020
Copy link to comment
2019-07-02 17-13-46
Tércio Soares
Changed the status to
Implemented
on 06 Jan 2020

Hi.

As Hanno stated, this is implemented now. The value of "MaxReceivedMessageSize" was set to the maximum possible, starting with Development Environment 11.6.21.8208.

Let me know if you have any questions.

Thanks,

Tércio

08 Jan 2020
Copy link to comment