nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Problems for some users importing large files

skbaker

I have a user who has reported that when he tries to import a large (60MB) file into TeamSite (5.5 on AIX) using the "File->Import" tool, he gets the following error:

Error importing file file_name_removed_for_this_post.mpg to TeamSite server:
Error sending file to 'http://server.name.removed.for.this.post/iw-bin/iwfileupdownload.cgi':
Couldn't read file c:\Documents and Settings\Administrator\My Documents\filename_removed_for_this_post.mpg:
java.lang.OutOfMemoryError - null

I have tried to reproduce this from my own machine to two different TS servers (including the one he tried), and I was able to successfully import a file that was 63MB, with no errors. However, I have another colleague who was able to reproduce the error on his machine with a file of size 31MB. I have requested that the initial user try the import on a colleague's computer, but have not yet gotten a response from him.

The intermittent behavior I'm seeing leads me to believe that the problem might lie with the amount of memory on the user's machine. My machine has 512MB of memory on it. I don't yet know what my original user's machine has.

I found a KB article that talks about problems with file imports on TS 5.0.1 (originating from a known Sun java bug), but based on my success today, I'm guessing the problem has been resolved in 5.5.2.

Any ideas if this is indeed a client machine memory problem, or something else?

--Sandra

Find more posts tagged with

Comments

Migrateduser

I would still check what version of the Java VM is running on the client machine. I've seen that problem on 5.5.2 also. New version of JVM fixes it.

- Jason

Migrateduser

skbaker,

The problem is that the file you're importing has to fit into
the available virtual memory of the applet. This is sort of
a function of the way the java networking APIs work over
http, and it doesn't really have anything to do with IWTemp,
or the version of the JVM (plug-in).

There was a work-around added in 5.5.2_SP3 - along with a
bunch of other LaunchPad fixed - I often recommend people
with LaunchPad issues upgrade to >=SP3 in this forum (you
probably saw my past posts on this.)

However, in this case, that won't help because I believe the
AIX 5.5 code is based on 5.5.2L_SP1 so you'll need to do one
of the following:

- Increase the virtual memory availble to Windows on the
client PC, or

- Use the "direct mount" option to LaunchPad if you are/can
use samba. We bundle samba, as you may know. If the file
can be copied using a direct mount, the whole thing will not
be read into memory first. The Direct Mount option is set in
the LaunchPad Setup menu.

Hope that helps,

Jason Heirtzler
Interwoven Engineering

skbaker

Thanks for the great info. I've passed this on to my user!