4:35 p.m.
Ryan Scharer created ISPN-2082:
----------------------------------
Summary: JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values >
4000 bytes
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Manik Surtani
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a BLOB
value column. If I try to store a BLOB value of less than 4000 bytes, everything works
fine. If the value is greater, the cache store fails with ORA-24816. This occurs because
the BLOB column is not the last one in the PreparedStatement SQL as the Oracle driver
requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore
implementation and write my own insert/update SQL in storeLockSafe(). This works fine,
but obviously isn't ideal from an upgrade point of view. Simply overriding
storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:23 a.m.
[
https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-2082:
-----------------------------------
Fix Version/s: 6.0.0.FINAL
Workaround Description: Clone the JdbcStringBasedCacheStore implementation and write
my own insert/update SQL in storeLockSafe() in order to get around the issue.
Workaround: Workaround Exists
JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values >
4000 bytes
--------------------------------------------------------------------------
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Manik Surtani
Fix For: 6.0.0.FINAL
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a
BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything
works fine. If the value is greater, the cache store fails with ORA-24816. This occurs
because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle
driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore
implementation and write my own insert/update SQL in storeLockSafe(). This works fine,
but obviously isn't ideal from an upgrade point of view. Simply overriding
storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:09 p.m.
[
https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin....
]
Mircea Markus commented on ISPN-2082:
-------------------------------------
re fixing this, DatabaseType can be enhanced with a more specific version of ORACLE and
add a corresponding SQL statement in the TableManipulation
JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values >
4000 bytes
--------------------------------------------------------------------------
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Manik Surtani
Fix For: 6.0.0.FINAL
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a
BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything
works fine. If the value is greater, the cache store fails with ORA-24816. This occurs
because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle
driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore
implementation and write my own insert/update SQL in storeLockSafe(). This works fine,
but obviously isn't ideal from an upgrade point of view. Simply overriding
storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:02 a.m.
[
https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin....
]
Manik Surtani reassigned ISPN-2082:
-----------------------------------
Assignee: Tristan Tarrant (was: Manik Surtani)
JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values >
4000 bytes
--------------------------------------------------------------------------
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Tristan Tarrant
Fix For: 5.2.0.ALPHA2, 5.2.0.FINAL
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a
BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything
works fine. If the value is greater, the cache store fails with ORA-24816. This occurs
because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle
driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore
implementation and write my own insert/update SQL in storeLockSafe(). This works fine,
but obviously isn't ideal from an upgrade point of view. Simply overriding
storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:02 a.m.
[
https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin....
]
Manik Surtani updated ISPN-2082:
--------------------------------
Fix Version/s: 5.2.0.ALPHA2
5.2.0.FINAL
(was: 6.0.0.FINAL)
JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values >
4000 bytes
--------------------------------------------------------------------------
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Tristan Tarrant
Fix For: 5.2.0.ALPHA2, 5.2.0.FINAL
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a
BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything
works fine. If the value is greater, the cache store fails with ORA-24816. This occurs
because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle
driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore
implementation and write my own insert/update SQL in storeLockSafe(). This works fine,
but obviously isn't ideal from an upgrade point of view. Simply overriding
storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:25 a.m.
[
https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin....
]
Thomas Fromm commented on ISPN-2082:
------------------------------------
Ryan, I tested now JdbcStringBasedCacheStore on a 11.2.0.3.0 RAC. No problems recognized.
I use BLOB too. So can you provide a test case for it?
JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values >
4000 bytes
--------------------------------------------------------------------------
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Tristan Tarrant
Fix For: 5.2.0.ALPHA2, 5.2.0.FINAL
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a
BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything
works fine. If the value is greater, the cache store fails with ORA-24816. This occurs
because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle
driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore
implementation and write my own insert/update SQL in storeLockSafe(). This works fine,
but obviously isn't ideal from an upgrade point of view. Simply overriding
storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:49 a.m.
[
https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin....
]
Ryan Scharer commented on ISPN-2082:
------------------------------------
I'll try to clear some time to post a trivial test case in the next couple of days.
JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values >
4000 bytes
--------------------------------------------------------------------------
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Tristan Tarrant
Fix For: 5.2.0.ALPHA2, 5.2.0.FINAL
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a
BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything
works fine. If the value is greater, the cache store fails with ORA-24816. This occurs
because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle
driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore
implementation and write my own insert/update SQL in storeLockSafe(). This works fine,
but obviously isn't ideal from an upgrade point of view. Simply overriding
storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:54 a.m.
[
https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin....
]
Thomas Fromm commented on ISPN-2082:
------------------------------------
Do you use thin client?
JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values >
4000 bytes
--------------------------------------------------------------------------
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Tristan Tarrant
Fix For: 5.2.0.ALPHA2, 5.2.0.FINAL
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a
BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything
works fine. If the value is greater, the cache store fails with ORA-24816. This occurs
because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle
driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore
implementation and write my own insert/update SQL in storeLockSafe(). This works fine,
but obviously isn't ideal from an upgrade point of view. Simply overriding
storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:58 a.m.
[
https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin....
]
Ryan Scharer commented on ISPN-2082:
------------------------------------
Yes, the debug version: ojdbc6_g.jar
JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values >
4000 bytes
--------------------------------------------------------------------------
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Tristan Tarrant
Fix For: 5.2.0.ALPHA2, 5.2.0.FINAL
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a
BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything
works fine. If the value is greater, the cache store fails with ORA-24816. This occurs
because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle
driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore
implementation and write my own insert/update SQL in storeLockSafe(). This works fine,
but obviously isn't ideal from an upgrade point of view. Simply overriding
storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:30 a.m.
[
https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin....
]
Thomas Fromm commented on ISPN-2082:
------------------------------------
Changed to JDK7 and used the debug driver. Still all things are looking good. I'm
looking forward to your test case :-)
JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values >
4000 bytes
--------------------------------------------------------------------------
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Tristan Tarrant
Fix For: 5.2.0.ALPHA2, 5.2.0.FINAL
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a
BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything
works fine. If the value is greater, the cache store fails with ORA-24816. This occurs
because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle
driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore
implementation and write my own insert/update SQL in storeLockSafe(). This works fine,
but obviously isn't ideal from an upgrade point of view. Simply overriding
storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:33 a.m.
[
https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin....
]
Thomas Fromm commented on ISPN-2082:
------------------------------------
Changed to JDK7 and used the debug driver. Still all things are looking good. I'm
looking forward to your test case :-)
JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values >
4000 bytes
--------------------------------------------------------------------------
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Tristan Tarrant
Fix For: 5.2.0.ALPHA2, 5.2.0.FINAL
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a
BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything
works fine. If the value is greater, the cache store fails with ORA-24816. This occurs
because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle
driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore
implementation and write my own insert/update SQL in storeLockSafe(). This works fine,
but obviously isn't ideal from an upgrade point of view. Simply overriding
storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:17 p.m.
[
https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin....
]
Ryan Scharer commented on ISPN-2082:
------------------------------------
Whew... thought I was going crazy because I couldn't reproduce the problem. Turns out
the missing secret ingredient is an unusually long key (> 1000 chars). I'm
guessing you were testing with much more prosaic keys. The following test case
illustrates the problem trivially. The first prepared statement succeeds, and the second
fails. The only difference is the insertion order.
--- SQL
create user clob_testcase identified by password;
grant connect, resource to clob_testcase;
create table clob_testcase.test (
KEY VARCHAR2(2000) NOT NULL,
VALUE BLOB,
TSTAMP NUMBER(10),
PRIMARY KEY (KEY)
);
--- JAVA
package com.test.clob;
import java.io.ByteArrayInputStream;
import java.sql.Blob;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
public class Main {
public static void main(String[] args) throws Exception {
char[] keyChars = new char[1001];
for (int i = 0; i < keyChars.length; i++) {
keyChars[i] = 'x';
}
char[] key2Chars = new char[1001];
for (int i = 0; i < keyChars.length; i++) {
key2Chars[i] = 'y';
}
byte[] bytes = new byte[18001];
for (int i = 0; i < bytes.length; i++) {
bytes[i] = 'z';
}
Class.forName("oracle.jdbc.OracleDriver");
Connection con =
DriverManager.getConnection("jdbc:oracle:thin:@racload0:1521/gen",
"clob_testcase", "password");
//this succeeds
PreparedStatement pstmt = con.prepareStatement("insert into test(tstamp, key,
value) values(?,?,?)");
pstmt.setLong(1, -1);
pstmt.setString(2, String.valueOf(keyChars));
pstmt.setBinaryStream(3, new ByteArrayInputStream(bytes), bytes.length);
pstmt.executeUpdate();
pstmt.close();
//this fails
pstmt = con.prepareStatement("insert into test(tstamp, value, key)
values(?,?,?)");
pstmt.setLong(1, -1);
pstmt.setBinaryStream(2, new ByteArrayInputStream(bytes), bytes.length);
pstmt.setString(3, String.valueOf(key2Chars));
pstmt.executeUpdate();
pstmt.close();
con.close();
}
}
JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values >
4000 bytes
--------------------------------------------------------------------------
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Tristan Tarrant
Fix For: 5.2.0.ALPHA2, 5.2.0.FINAL
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a
BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything
works fine. If the value is greater, the cache store fails with ORA-24816. This occurs
because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle
driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore
implementation and write my own insert/update SQL in storeLockSafe(). This works fine,
but obviously isn't ideal from an upgrade point of view. Simply overriding
storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3 a.m.
[
https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin....
]
Thomas Fromm commented on ISPN-2082:
------------------------------------
Thanks, can confirm it. Its working on normal Oracle installation and fails on RAC :-o
I can't agree with Mircea introducing a new database type. The easiest solution would
be reordering the fields in general.
If this is considered too dangerous, at least insert/updates for oracle should be changed,
because both orders works on normal oracle installations.
JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values >
4000 bytes
--------------------------------------------------------------------------
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Tristan Tarrant
Fix For: 5.2.0.ALPHA2, 5.2.0.FINAL
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a
BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything
works fine. If the value is greater, the cache store fails with ORA-24816. This occurs
because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle
driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore
implementation and write my own insert/update SQL in storeLockSafe(). This works fine,
but obviously isn't ideal from an upgrade point of view. Simply overriding
storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:23 a.m.
[
https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-2082:
-----------------------------------
Fix Version/s: 5.2.0.ALPHA3
(was: 5.2.0.ALPHA2)
JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values >
4000 bytes
--------------------------------------------------------------------------
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Tristan Tarrant
Fix For: 5.2.0.ALPHA3, 5.2.0.FINAL
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a
BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything
works fine. If the value is greater, the cache store fails with ORA-24816. This occurs
because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle
driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore
implementation and write my own insert/update SQL in storeLockSafe(). This works fine,
but obviously isn't ideal from an upgrade point of view. Simply overriding
storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:55 p.m.
[
https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2082:
--------------------------------
Fix Version/s: 5.2.0.Alpha4
(was: 5.2.0.Alpha3)
JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values >
4000 bytes
--------------------------------------------------------------------------
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Tristan Tarrant
Fix For: 5.2.0.Alpha4, 5.2.0.Final
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a
BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything
works fine. If the value is greater, the cache store fails with ORA-24816. This occurs
because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle
driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore
implementation and write my own insert/update SQL in storeLockSafe(). This works fine,
but obviously isn't ideal from an upgrade point of view. Simply overriding
storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:21 a.m.
[
https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-2082:
-----------------------------------
Fix Version/s: 5.2.0.Beta1
(was: 5.2.0.Alpha4)
JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values >
4000 bytes
--------------------------------------------------------------------------
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Tristan Tarrant
Fix For: 5.2.0.Beta1, 5.2.0.Final
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a
BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything
works fine. If the value is greater, the cache store fails with ORA-24816. This occurs
because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle
driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore
implementation and write my own insert/update SQL in storeLockSafe(). This works fine,
but obviously isn't ideal from an upgrade point of view. Simply overriding
storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:31 p.m.
[
https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2082:
--------------------------------
Fix Version/s: 5.2.0.CR1
(was: 5.2.0.Beta1)
JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values >
4000 bytes
--------------------------------------------------------------------------
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Tristan Tarrant
Fix For: 5.2.0.CR1, 5.2.0.Final
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a
BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything
works fine. If the value is greater, the cache store fails with ORA-24816. This occurs
because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle
driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore
implementation and write my own insert/update SQL in storeLockSafe(). This works fine,
but obviously isn't ideal from an upgrade point of view. Simply overriding
storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:37 p.m.
[
https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2082:
--------------------------------
Fix Version/s: 5.2.0.CR1
(was: 5.2.0.Beta2)
JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values >
4000 bytes
--------------------------------------------------------------------------
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Tristan Tarrant
Fix For: 5.2.0.CR1, 5.2.0.Final
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a
BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything
works fine. If the value is greater, the cache store fails with ORA-24816. This occurs
because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle
driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore
implementation and write my own insert/update SQL in storeLockSafe(). This works fine,
but obviously isn't ideal from an upgrade point of view. Simply overriding
storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:26 p.m.
[
https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2082:
--------------------------------
Fix Version/s: 5.2.0.CR1
(was: 5.2.0.Beta3)
JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values >
4000 bytes
--------------------------------------------------------------------------
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Tristan Tarrant
Fix For: 5.2.0.CR1, 5.2.0.Final
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a
BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything
works fine. If the value is greater, the cache store fails with ORA-24816. This occurs
because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle
driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore
implementation and write my own insert/update SQL in storeLockSafe(). This works fine,
but obviously isn't ideal from an upgrade point of view. Simply overriding
storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:06 p.m.
[
https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2082:
--------------------------------
Fix Version/s: 6.0.0.Final
(was: 5.2.0.Final)
(was: 5.2.0.CR1)
JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values >
4000 bytes
--------------------------------------------------------------------------
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Tristan Tarrant
Fix For: 6.0.0.Final
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a
BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything
works fine. If the value is greater, the cache store fails with ORA-24816. This occurs
because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle
driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore
implementation and write my own insert/update SQL in storeLockSafe(). This works fine,
but obviously isn't ideal from an upgrade point of view. Simply overriding
storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4193
days inactive
4346
days old
infinispan-issues@lists.jboss.org
23 comments
5 participants
participants (5)
-
Galder Zamarreño (JIRA) -
Manik Surtani (JIRA)
-
Mircea Markus (JIRA)
-
Ryan Scharer (JIRA)
-
Thomas Fromm (JIRA)