Thanks, I tested the sample, and it does work with HSQLDB. But when I tested it against SQL Server with similar results I got before: Upload works but reading the file with DatabaseReader returns 0 bytes. :(

So, my guess is, something has changed between 2.1.5 and 2.1.7 that makes
the JDBC driver for SQL Server incompatible with Cocoon. With the jar-files from 2.1.5 (same setup otherwise) this works. What could this change be?

The method that throws this error "Assuming client reset stream" in DatabaseReader.java is:

public void generate() throws ProcessingException, SAXException, IOException {
        try {
            Response response = ObjectModelHelper.getResponse(objectModel);
            this.serialize(response);
        } catch (IOException ioe) {
            getLogger().warn("Assuming client reset stream");

            this.doCommit = false;
        } catch (Exception e) {
            this.doCommit = false;

            throw new ResourceNotFoundException("DatabaseReader error:", e);
        }
    }


-Tuomo

On Sun, 17 Jul 2005, Andrew Franz wrote:

DatabaseReader is used in the samples:
http://localhost:8080/cocoon/samples/blocks/databases/mod-db/file-upload-blob
(Cocoon 2.1.7, Tomcat 5.5)

After upload, this uses DatabaseReader to retrieve the image from HSQLDB.
If this works ok, then the problems are with SQL Server maybe the column definition


Tuomo L wrote:

Hi,

Is anyone using the DatabaseReader with Cocooon 2.1.7 ? We just cannot get
it to function. Log says "Assuming client reset stream".

If it works, could you please tell which versions of Java, Tomcat and db you have on what system? We're trying to figure out the source for this
problem. With Cocoon 2.1.5 everything works fine. We are using SQL Server
2000 and it's latest JDBC driver provided by MS.

-Tuomo


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to