Hi Ppl,
Here's the problem definition:-
As a part of a J2EE Application that we are developing, we have a
functionality for uploading and viewing gif images. Everything is
working fine but for the fact that we are not able to upload image
data greater that 4088 bytes! At the front end, we are using Multipart
form data to get the image data into a byte array. In the callable
statement, the image data is set using setString. At the backend, we
are using DB2 where this image data column is declared as varchar.
We are using DB2 connect to connect to the data source and JDBC type 2
driver.
Any image data up to 4088 bytes goes fine and we are able to view the
images. But when I try to send 4089 bytes of data, at the backend, it
comes as all spaces! We tried to write the image data back into a file
just before executing the upload query to ensure that there was no
problem in the code. The file is rendering properly.
So, we are at a loss to understand the cause of this. We guess that
there is some problem with the driver or some size setting in DB2
connect.
Can anyone help?
Thanx.
Here's the problem definition:-
As a part of a J2EE Application that we are developing, we have a
functionality for uploading and viewing gif images. Everything is
working fine but for the fact that we are not able to upload image
data greater that 4088 bytes! At the front end, we are using Multipart
form data to get the image data into a byte array. In the callable
statement, the image data is set using setString. At the backend, we
are using DB2 where this image data column is declared as varchar.
We are using DB2 connect to connect to the data source and JDBC type 2
driver.
Any image data up to 4088 bytes goes fine and we are able to view the
images. But when I try to send 4089 bytes of data, at the backend, it
comes as all spaces! We tried to write the image data back into a file
just before executing the upload query to ensure that there was no
problem in the code. The file is rendering properly.
So, we are at a loss to understand the cause of this. We guess that
there is some problem with the driver or some size setting in DB2
connect.
Can anyone help?
Thanx.