My maxFileSize is 6M, but whenever I pick pictures I can SEE are 1.43, or 1.21
Mb, I get the following message:
Picutre '<picture name="">' is too big. It will be uploaded unchanged (no
What's causing this? Is there another param I need to set? Again, maxFileSize
is set to 6M..so what's causing this?
That message occurs during picture transformation when the applet has run out
of memory. (It is unrelated to maxFileSize).
Have you tried fewer and/or smaller pictures?
I don't see it with smaller pictures. But the pictures I'm picking are not
unreasonably sized. 1.2 Mb...average size for a picture taken with a decent
And I'm writing this for my family members to use and not all of them are very
technically savey...so I really don't want them to have to resize all their
This message means THEIR system ran out of memory??
So bascially, my only solution is to disable the preview in the applet?
will adding ini_set("memory_limit","80M"); or something like that, prior to
applet instantiation help?
or is the applet's memory use different from any php settings?
nevermind. the ini_set didn't help.
Just an an FYI, I'm not seeing it on 2 of my comptuers, but I AM seeing this
warning message on my wife's laptop.
2.0 Ghz processor, 1.8Mb memory, 256Mb video card. not the best system..but
REALLY can't understand why (what I think is) an average computer, uploading
an average sized picture, is causing this message...
sorry..one other thing...you say during transformations. When this occurs, I
haven't DONE any transformation yet. Simply added the picture to my upload
list, then click the picture in the upload list.
Also, you said fewer or smaller pictures. This happens with just ONE picture.
I add ONE picture that's ~1.2Mb to my upload list. Click it to see the
preview, and the warning comes up!
Can you do the default_upload_policy, but still convert all image formats to
jpg? That would not be ideal, but would suit my needs.
The main reason I changed to the PictureUploadPolicy is I thought I needed
that to use the targetPictureFormat parameter.
It is a MUCH nicer interface..but if most my users are going to see warning
messages all the time, I'll refrain from using it.
You need to think about which parts of the procedure run on the user's
computer and which parts run on the server! The applet runs on the user's
You need to identify what is different about the laptop from the other 2 PCs
you have tried.
You can check your Java VM version & memory limit here : http://www.duckware.
(See also http://www.duckware.com/pmvr/howtoincreaseappletmemory.html )
ok. I'll do that.
As a side note, I could live with rewording the warning to say something like:
Picture '%1$s' is a bit large. You can still upload this picture, but you will
not be able to rotate it.
I've looked into updating the tooBigPicture warning in language_en. I've
changed it, and then followed the instructions here:
Then downloaded the latest java Development kit. RESIGNED the archive file as
per these instructions:
but I'm still seeing the same alert.
Again, if I could just alter the alter to let the user know, they can
proceed...just can't rotate. As it stands now, the warning makes it sound like
it's just too big. It's not too big. I can still upload them. It's just too
big to rotate.
okay...ALL computers I'm trying this on are using Java 1.6.0_24. So don't
think that's the problem
However, while the PC it does work on has a Max Mem of 245MB
the laptop has 31Mb...uh-oh!
I'll look at your "how to increase memory" link!
Well, that worked. Major thanks!!
I'll just put a little note above the applet that says: If you're getting
Picture <pic> is too big" errors, please see this link for steps on how to fix
In the mean time, I'd still like to change the wording of the Warning. So any
help there would be appreciated.
http://www.jupload.biz has no link with this JUpload
See : http://jupload.sourceforge.net/howto-
As stated by bilbo, this message is displayed when the applet runs out of
memory. But this is a not_to_easy one : AFAIK, it's not possible to control
the RAM allocated to the applet JVM. I guess it's based on the total available
As complementary information : default configuration is to have
pictureTransmitMetadata to false
cy.html for details)
This make necessary the creation of a new picture. Thus, making you come into
the issue you encountered.
To avoid it, you may reduce the target picture size (maxPicHeight and/or
maxPicWidth) or put pictureTransmitMetadata to true. In the latter case,
you'll need to check that you're picture are displayed correctly (see
As a last one : you're rewritting proposal for the message seems not accurate
to me. This message is displayed while uploading the picture. Your message
would be Ok, if it occurs before.
NB : I just added a FAQ entry, with this subject.
I'm seeing this warning message when I SELECT pictures from the upload
list...I'm guessing, because it's trying to generate the preview picture in
I am NOT having any issues uploading these pictures. It's simply when the user
selects the picture in the applet. Prior to even hitting the upload button.
So in that case, I DO believe my proposed warning text change does apply.
That said, I do appreciate all the info!!
Now the targetpicturesize parameters...won't that affect the size of the final
picture on my server?
I REALLY want to maintain resolution (up to a certain point, of course..in my
case, 6Mb)...but other than that, I really want these pictures to remain hi
resolution, if possible.
Can I just adjust the preview thumbnail size?? That seems to be where it's
I followed those increasing memory instruction. Increased it to 250.
Reloaded the Java mem test page and could see Max Mem was around 245Mb.
I then run the uploader...and it still gives me the warning on a picture that
was around 1.6 Mb.
I go BACK to the Java mem test page, and see Max Mem is not 40Mb.
Any clue what's going on here? Is JUpload resetting my Max Mem??
Some playing around, and I figured out what's creating the situation...but
seems like there's a memory leak somewhere.
If I can help you guys debug it, let me know. But to create the situation I:
I go to the java mem test page, and I'm at I'm at 245Mb Max Mem
I hit refresh on the java mem test page, now I'm at 95Mb Max Mem
I select another picture that's ~1.8 Mb. Preview shows fine (again, couples
I hit refresh on the java mem test page, now I'm at 38Mb.
I add another picture that's ~1.7Mb....and WHAM..I get the warning!
Sounds like memory's leaking somewhere.
If I can collect anything that would help you guys, please let me know.
I have fileChooserImagePreview = false, and yes the applet's still showing
mini-icons when searching folder, and when I select and add to the list. Click
on the item, and VIOLA...a preview shows in the upper right corner.
??? Even when I set fileChooserImagePreview to false?
the applet tag for the page shows it's set too:
<object classid="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93" <br="">codebase = "http://java.sun.com/update/1.5.0/jinstall-klzzwxh:00061_5-windows-i586.cab#Version=5,0,0,3"width = "650"height = "555"name = "JUpload">
<param name="uploadPolicy" value="PictureUploadPolicy"/>
<param name="lookAndFeel" value="system"/>
<param name="maxFileSize" value="6291456"/>
<param name="lang" value="en"/>
<param name="showLogWindow" value="false"/>
<param name="archive" value="wjhk.jupload.jar"/>
<param name="afterUploadURL" value="/Soda_Family_Albums/create_thumbnails.php"/>
<param name="allowedFileExtensions" value="jpg/jpeg/gif/png"/>
<param name="targetPictureFormat" value="png:jpg;gif:jpg;jpeg:jpg;"/>
<param name="sendMD5Sum" value="true"/>
<param name="fileChooserImagePreview" value="false"/>
<param name="debugLevel" value="99"/>
<param name="name" value="JUpload"/>
<param name="code" value="wjhk.jupload2.JUploadApplet"/>
<param name="httpUploadParameterType" value="array"/>
<param name="mayscript" value="true"/>
<param name="scriptable" value="false"/>
<param name="stringUploadSuccess" value="SUCCESS"/>
<param name="stringUploadError" value="ERROR: (.*)"/>
<param name="maxChunkSize" value="500000"/>
Oups and sorry : first message for bilbo :
I didn't see your link, to the memory setup for applets.
Great point here !
Added to the FAQ.
Just as an FYI, I still haven't found a way around this.
As a result, I just changed back to the default class, and my script will do
the converting to jpg.
it's no where near as fancy as the photo uploader...but until I can address
the memory leak/usage issue...I have to do it this way.
Just sucks cause this applet is SOOO close to being exactly what I
wanted/needed. But the inability to handle 1-2 Mb pictures is just not
sufficient for my needs.
But I DO appreciate your efforts, and it's still a great product!!
And thanks for the help thus-far!!
As a workaround, you may avoid the file browser, and use drag'n'drop instead.
You'll probably still got the error message, but the upload would occur.
In the meanwhile, I take a look at the code behavior....
Can you check the release, currently non-official, available here :
You found the bug?
Out of curiosity..what was it?
It's a THING OF BEAUTY!!
It works!!!! On all my machines! Previews show up quicker...I can click like
crazy, changing the selection like crazy...max memory changes by very small
amounts (<2Mb)...but hovers close to the set limit. That's even on my wife's
laptop which has a limit of 34Mb!!!!
Looks GREAT!!! Thank you SOOO much for fixing this! My cousin's about to have
a baby any day now...and the main reason I was working on this was to allow
her the ability to share her pictures with the family on our family web-site!
90% of my user's barely know how to work a computer, so the less
complicated/easier to use the better! This is a HUGE feature on my site!!
I even did some stress testing...uploading ~100 pics all around 1.5Mb...and
it's looking good!!
Can't thank you enough for your support!
Don't hesitate to donate ...
I just activate this option of Sourceforge !
If you can't see the button, here is the link...
Once I have a few of my user's try this out, and have success...I will most
definitely be sure to do just that!!
I will probably use Jupload and I'd loike to donate something.
Are you sending any kind of paper aknoledging the donation ?
Log in to post a comment.