Limitation on including DCT using inline script?

Hi,
I am trying to include in a DCT some component from another DCT using inline command. The script I have generates the inline content properly if I run the script from command line.

The same script when invoked while trying to create a DCR from GUI hangs while generating the inline content for some of the content types I have while working for some other content types.

After some debugging, it seems to me that either there is a limitation on the size of the content that can be inserted in a DCT using inline command OR there is a limitation on the size of DCT we can have.

Has anyone else faced similar problem?

Regards,
Rajiv

Find more posts tagged with

Comments

Adam Stoller

What version of TeamSite / TeamSite Templating are you using (including patch / service pack information)?
What platform?

I don't have access to our bug tracking system right now, but I believe there was (and perhaps may still be?) a known limitation to the amount of data that can be included through an inline (I don't remember what the limitation was, only that there was one)

Can you indicate how many characters your inline script that fails is returning?

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

I am using TeamSite 5.5.2 Build 16315 with SP2, Teamsite Templating version 5.5.2 on Solaris 5.8.

The inline content is getting limited to 16528 characters in my case while my requirements exceed this number.

Adam Stoller

Please open a case with Interwoven Support. At the very least, the limitation should be documented, at best, it should be removed (there might be reasons beyond our control why it cannot).

In the meantime, perhaps you can break up the source of the data and use multiple, successive inline's to retrieve it?

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

Thanks. Already opened the case and awaiting response.
I will investigate into the suggestion of breaking up the data but this may not be possible in our scenario.

catorarn

Hi Rajiv,

Two things to check:

1. Make sure the inlines are not returning any non UTF-8 characters. The first non UTF-8 character it returns will cause it to stop with an error
like:

"Error building the requirements: null"

2. Please check that first, but if that isn't the problem then you could try increasing the Heap size for servlet engine:

Here are the steps needed to change the amount of memory available to the jvm that is running the servlet engine:

* make a backup copy of your current `iwgethome`/private/bin/iwuiboot file and save it as iwuiboot.org. Also note the permissions on this file. *

1. Edit the file `iwgethome`/private/bin/iwuiboot

2. Locate the first occurrence of "TOMCAT_OPTS".

3. Add extra jvm options for memory management. Here is a before/after example from my server where I have increased the max heap size to 128MB (I believe the default is 16MB):

before: TOMCAT_OPTS="-Xss2m ..."
after: TOMCAT_OPTS="-Xss2m -Xmx128M -Djava.rmi.server.codebase=......."

Note: There are other memory management flags available for java. Run "`iwgethome`/tools/java1.3/bin/java -X" for help on these flags.

4. Run "iwreset -ui".

Cheers,

arnout

Migrateduser

Thanks Arnout,
The problem was with a non UTF-8 character. It got resolved when I fixed that. Though in case the inline content is large Team Site does not throw a templating error for the non UTF-8 issue. I waited for a long time for the error to be shown but it did not come up and the DCT seems to hang in such a case. While it does throw the error for a smaller inline content for the non UTF-8 character issue.
Even increasing the servlet engine memory upto 512M did not help.

jeremystitt

Was there ever a resolution to this problem? I recently installed TeamSite 5.5.2 and had the same problem with an inline command. Any attempt to edit a DCR caused the templating window to hang because of a non-UTF-8 character being put into the DCR from the inline command.

Now that I know the solution, I can edit my DCRs, but if the problem happens to one of my users, it may take longer to identify.

Migrateduser

Are you on 5.5.2 or 5.5.2 with an SP level? If you aren't on an SP level, I recommend you go at least to SP3. I know we fixed some internationalization issues in LSP1 and SP2.

regards,

lissa

ProfessorX

Great Posts thanks.
I have the same problem.

Im on TS 5.5.2 SP 5 so it has to be a later SP than 5 to fix it. Anyone know which one? Has it been fixed?

Thanks in advance!
WIN2K TS/TST 5.5.2 sp5; OD 5.6.0.1; DD 5.5.2
The Professor-

Migrateduser

I have had the same problem with not-so-"smart" quotes in the data. Seems like it should report the invalid XML instead of just hanging. Is there a bug filed on this?