[
https://issues.apache.org/jira/browse/DERBY-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-3650:
----------------------------------
Attachment: Derby3650FullClientRepro.java
Attaching one more case, Derby3650FullClientRepro which shows the regression
from 10.2 to 10.3 caused by the fix for DERBY-2892. For client even without
the free we fail,, because there is a free under the covers. This case passes
with 10.2 or with soft upgrade to higher versions but fails with a new database
for 10.3.3.0
java DerbyFullClientRepro
--- rs.next iteration 1
Clob id : 1
--- rs.next iteration 2
Clob id : 1
Exception in thread "main" java.sql.SQLException: The exception
'java.sql.SQLException: Java exception: 'Reached end-of-
stream prematurely, with 2 byte(s) to go: java.io.EOFException'.' was thrown
while evaluating an expression.
at
org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:96)
at
org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:362)
at org.apache.derby.client.am.Clob.getCharacterStream(Clob.java:349)
at Derby3650FullClientRepro.main(Derby3650FullClientRepro.java:25)
Caused by: org.apache.derby.client.am.SqlException: The exception
'java.sql.SQLException: Java exception: 'Reached end-o
f-stream prematurely, with 2 byte(s) to go: java.io.EOFException'.' was thrown
while evaluating an expression.
at
org.apache.derby.client.am.Statement.completeExecute(Statement.java:1601)
at
org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(NetStatementReply.java:322)
at
org.apache.derby.client.net.NetStatementReply.readExecuteCall(NetStatementReply.java:106)
at
org.apache.derby.client.net.StatementReply.readExecuteCall(StatementReply.java:75)
at
org.apache.derby.client.net.NetStatement.readExecuteCall_(NetStatement.java:179)
at
org.apache.derby.client.am.Statement.readExecuteCall(Statement.java:1567)
at
org.apache.derby.client.am.PreparedStatement.flowExecute(PreparedStatement.java:2139)
at
org.apache.derby.client.am.PreparedStatement.executeX(PreparedStatement.java:1582)
at
org.apache.derby.client.am.CallableLocatorProcedures.clobGetLength(CallableLocatorProcedures.java:859)
at org.apache.derby.client.am.Clob.getLocatorLength(Clob.java:1050)
at org.apache.derby.client.am.Lob.sqlLength(Lob.java:116)
at org.apache.derby.client.am.Lob.checkForLocatorValidity(Lob.java:386)
at
org.apache.derby.client.am.UpdateSensitiveClobLocatorReader.<init>(UpdateSensitiveClobLocatorReader.java:74)
at org.apache.derby.client.am.Clob.getCharacterStreamX(Clob.java:362)
at org.apache.derby.client.am.Clob.getCharacterStream(Clob.java:340)
... 1 more
Caused by: org.apache.derby.client.am.SqlException: Java exception: 'Reached
end-of-stream prematurely, with 2 byte(s) t
o go: java.io.EOFException'.
... 16 more
> Derby + Hibernate JPA 3.2.1 problem on entity with Blob/Clob
> ------------------------------------------------------------
>
> Key: DERBY-3650
> URL: https://issues.apache.org/jira/browse/DERBY-3650
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.4.1.3
> Environment: Mac OSX 10.4
> JDK 1.5.0_13
> Hibernate EntityManager 3.2.1
> Reporter: Golgoth 14
> Attachments: Derby3650EmbeddedRepro.java,
> Derby3650FullClientRepro.java, Derby3650FullRepro.java, Derby3650Repro.java,
> DerbyHibernateTest.zip, testdb.zip, traces_on_FormatIdStream_alloc.txt,
> UnionAll.java
>
>
> Hi,
> I'm using Derby in Client - Server mode with Hibernate JPA EJB 3.0.
> When a query on an entity containing a Clob and some joins on other entites
> is executed, an exception with the following message is thrown:
> XJ073: The data in this BLOB or CLOB is no longer available. The
> BLOB/CLOB's transaction may be committed, or its connection is closed.
> This problem occurs when the property "hibernate.max_fetch_depth" is greater
> than 0.
> When hibernate.max_fetch_depth=0, the query works.
> If Derby is configured in embedded mode, the query works independently of the
> value of hibernate.max_fetch_depth.
> On the Hibernate's documentation, the advised value of
> hibernate.max_fetch_depth is 3.
> Could you explain me if I made something wrong ?
> Thank you.
> Stephane
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
