Permanent fix for DCR Saving Issue

Hi,

We have one DCR with size 1.9 MB and we had a problem saving the dcr.
We got a temporary fix to change the maxPostSize = "0" in server.xml file.
And it worked well but whenever we restart the TeamSite Server the maxPostSize will be replaced in server.xml

so is there any permanent fix for this?
Please advice.
we are on TeamSite 6.5 Solaris 10

Find more posts tagged with

Comments

Surender

Any ideas on the permanent fix for below issue?

Hi,

We have one DCR with size 1.9 MB and we had a problem saving the dcr.
We got a temporary fix to change the maxPostSize = "0" in server.xml file.
And it worked well but whenever we restart the TeamSite Server the maxPostSize will be replaced in server.xml

so is there any permanent fix for this?
Please advice.
we are on TeamSite 6.5 Solaris 10

Rick Poulin

Have you asked support?

There's no supported way of changing this file as far as I know. You could trace the original file's location (to the iw-home/install folder, i'm guessing) and change it there, but that's obviously unsupported. I can't help you out more than that, since I haven't had a 6.5 server at my disposal in years.

Migrateduser

Oh the horror! Anyway you could move to a newer version?

Surender

Thanks Rick and bmazum.

is it supported on newer versions of TeamSite?
I mean can we save large DCRs (2 MB files) without any issues and without changing server.xml file in newer versions of teamsite?

Bhargav Coca

I haven't seen any issues with more than 2MB for a DCR.
However, we have seen issues with people trying to put a whole of text in textarea.

TS 7.2.1

Thanks

Rick Poulin

is it supported on newer versions of TeamSite?
I mean can we save large DCRs (2 MB files) without any issues and without changing server.xml file in newer versions of teamsite?

The server.xml doesn't even exist in TS 7.x because they switched to JBoss. My guess is the default settings for JBoss are higher than they were for Tomcat because, as lilley pointed out, it hasn't been an issue since.

Migrateduser

Yes. We had a similar issue with a bulky DCR in 6.2 which got fixed in the later versions, perhaps owing to the analysis shared by Rick.