And an example would be? The 4.0.3.zip I downloaded exactly matches the advertised size of 70908109:
[sstark@sstark Releases]$ ls -l jboss-4.0.3.zip -rwx------ 1 sstark mkpasswd 70908109 Oct 4 22:50 jboss-4.0.3.zip
Likewise, the size of the jboss-4.0.3-installer.jar matches the advertised 48140075 size:
[sstark@sstark Releases]$ ls -l jboss-4.0.3-installer.jar -rw-rw-rw- 1 sstark mkpasswd 48140075 Oct 5 00:51 jboss-4.0.3-installer.jar
I think it depends on the mirror used for the download.
If I download it from the Kent mirror the size downloaded is 279,352Kb and it contains 14 server configurations.
If I download it from the Pheonix mirror it looks like it is the correct size.
My download from Pheonix has just completed, that is the correct size and contains just the three normal server configurations.
Ok, then likely some mirrors have failed to replicate it correctly. Such versions certainly won't have a matching md5 sum, and if the size does not match, it can't be a valid distribution as the sizes listed on sourceforge are correct.
I hadn't any time to unpack or check it. I just noticed that what I downloaded was over 200MB. I figured that there was something amiss and that's why I posted the question.