Hi, we have limited the attachment size at 10MB but a user can’t download a attachment greater then +/- 4,5MB, has anyone the same problem?
We are using Nokia E63/E71.
Subject: RE: Traveler Attachment Size
The user has a filter but the server has the max attachment setting. I assume you are saying you changed the server setting from 4MB to 10MB. If not, that is the setting you would have to change. BUT, be very careful as you are much more likely to run out of memory and crash the server. That’s why the 4MB limit is there - to prevent crashes. If you have the setting correct, you need to open a PMR to provide logs including a “tell traveler dump ”.http://www-01.ibm.com/support/docview.wss?uid=swg21447185
Subject: RE: Traveler Attachment Size
Hi,
I have changed the setting to 25MB, why would this be a killer for the server? I have pin pointed it to Nokia devices, on my Android I had downloaded files from 8MB.
Subject: RE: Traveler Attachment Size
The “killer” part of it is that in will run the Traveler server out of memory. The original code (which Nokia is using) has the whole attachment loaded into memory and passed around. If you start having a few copies of a 100MB object for one user, add a few users, etc., you can run out of memory. That’s why the 4MB limit is there in the first place.
With Android (and Apple), we added the capability to “stream” the attachment. Thus, the whole attachment is not loaded into memory but rather send to the device directly in little chunks. Because of the streaming, there is much less risk of the server running out of memory because the attachment is not loaded completely into memory. This feature has not found its way back into the Nokia and WM clients which is why you could get larger attachments on Android but not Nokia. Changing WM and Nokia to use the streamed attachments is on the list of future requirements; since Android was new, it just started with the streaming and never did it the older way.