I have been sending the chunk size, and then its contents, but it seems to be 
failing when the stream in question is of a pdf document.

Here is a sample . . . Is there something wrong? Why is it only the pdf. Much 
larger html and jpg files that I've scanned succeed.


int read = DEFAULT_CHUNK_SIZE;
            byte[] buffer = new byte[DEFAULT_CHUNK_SIZE];
            System.out.println("The default chunk size is " + 
DEFAULT_CHUNK_SIZE); // 2048
            while (read == DEFAULT_CHUNK_SIZE){
                try {
                    read = inputstream.read(buffer);
             // WRITE TO THE OUTPUTSTREAM
                    dataOutputStream.writeInt(read);
                    dataOutputStream.write(buffer, 0, read);
                } catch (IOException e){
                    setStatus(Curator.CURATE_ERROR);
                    log.error("Could not read/write to the socket . . . ");
                }
            }
            try {
                dataOutputStream.writeInt(0);
                dataOutputStream.flush();
            } catch (IOException e){
                setStatus(Curator.CURATE_ERROR);
                log.error("Error writing zero-length chunk to socket") ;
            }
..\Wendy
Wendy Bossons
Senior Software Engineer
MIT Libraries
Software Analysis and Development
77 Masachusetts Avenue
Cambridge, MA 02139-4307
617-253-0770
wboss...@mit.edu<mailto:wboss...@mit.edu>

On Nov 4, 2010, at 12:15 PM, Török Edwin wrote:

On Thu, 4 Nov 2010 11:50:40 -0400
Wendy J Bossons <wboss...@mit.edu<mailto:wboss...@mit.edu>> wrote:

Ok. I see. That's good -- it is clearer.

One question and this has been blocking my understanding as well --
when I scan a small pdf, I am getting this . . . INSTREAM: Size limit
reached, (requested: 4294967295, max: 25946112)

The file is the clam doc.
clamdoc
(1).pdf<http://sts-demo.mit.edu/bitstream/handle/123456789/7/clamdoc%20%281%29.pdf?sequence=3>
262Kb

The default chunk size is 2048.


I am not sure why this would occur, or how to remedy it. Bumping this
number in the clamd.conf to 50xxxxxxxxxx does not get rid of the
error.

Read the docs, you need to send the chunk's size, then the contents.

Run clamd with Debug yes in clamd.conf, it will give more details about
protocol errors.

--Edwin

_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml

Reply via email to