RE: Truncation Error

It looks like the serialized message size is bigger than that allowed by
Derby
for the LONG VARCHAR column.
 
From http://incubator.apache.org/derby/docs/ref/rrefsqlj30118.html:
 
  "The LONG VARCHAR FOR BIT DATA type allows storage of bit strings up to
32,700 bytes"
 
It may be possible to change the database schema to use BLOB
instead of LONG VARCHAR FOR BIT DATA (aka LONG VARBINARY). 
OpenJMS uses LONG VARBINARY instead of BLOB as vendor support 
for BLOB is patchy.
 
Another workaround is to use another database which doesn't have this
size restriction, such as MySQL.
 
-Tim
 


  _____  

From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
[mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of Francisco J.
Bido
Sent: Saturday, 9 July 2005 9:52 AM
To: [email protected]
Subject: [openjms-user] Truncation Error


Hi Everyone, 

Not sure what to make out this one... Has anyone seen it before?

http://openjms.sourceforge.net 
13:21:48.688 INFO [main] - Server accepting connections on
tcp://10.173.141.52:3035/ 
13:21:48.693 INFO [main] - JNDI service accepting connections on
tcp://10.173.141.52:3035/ 
13:21:48.696 INFO [main] - Admin service accepting connections on
tcp://10.173.141.52:3035/ 
13:21:48.813 INFO [main] - Server accepting connections on
rmi://10.173.141.52:1099/ 
13:21:48.814 INFO [main] - JNDI service accepting connections on
rmi://10.173.141.52:1099/ 
13:21:48.815 INFO [main] - Admin service accepting connections on
rmi://10.173.141.52:1099/ 
13:24:30.347 ERROR [RMI TCP Connection(4)-10.123.140.57] - Failed to make
message persistent 
org.exolab.jms.persistence.PersistenceException: 
ERROR 22001: A truncation error was encountered trying to shrink LONG
VARCHAR FOR BIT DATA 'XX-RESOLVE-XX' to length 32700. 
at
org.apache.derby.iapi.error.StandardException.newException(StandardException
.java) 
at org.apache.derby.iapi.types.SQLBinary.checkHostVariable(SQLBinary.java) 
at org.apache.derby.exe.ac601a400fx0104xf7aex87f0xffffd7390ab56.e0(Unknown
Source) 
at
org.apache.derby.impl.services.reflect.DirectCall.invoke(ReflectGeneratedCla
ss.java) 
at
org.apache.derby.impl.sql.execute.RowResultSet.getNextRowCore(RowResultSet.j
ava) 
at
org.apache.derby.impl.sql.execute.NormalizeResultSet.getNextRowCore(Normaliz
eResultSet.java) 
at
org.apache.derby.impl.sql.execute.DMLWriteResultSet.getNextRowCore(DMLWriteR
esultSet.java) 
at
org.apache.derby.impl.sql.execute.InsertResultSet.open(InsertResultSet.java)

at
org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedSt
atement.java) 
at
org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.ja
va) 
at
org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(EmbedPrep
aredStatement.java) 
at
org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(EmbedPrepare
dStatement.java) 
at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(Delegating
PreparedStatement.java:233) 
at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(Delegating
PreparedStatement.java:233) 
at org.exolab.jms.persistence.Messages.add(Messages.java:175) 
at org.exolab.jms.persistence.RDBMSAdapter.addMessage(RDBMSAdapter.java:326)

at
org.exolab.jms.messagemgr.MessageMgr.addPersistentMessage(MessageMgr.java:30
2) 
at org.exolab.jms.messagemgr.MessageMgr.add(MessageMgr.java:227) 
at org.exolab.jms.server.JmsServerSession.send(JmsServerSession.java:221) 
at
org.exolab.jms.server.net.RemoteServerSession.send(RemoteServerSession.java:
152) 
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) 
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25) 
at java.lang.reflect.Method.invoke(Method.java:585)


Best,
-Francisco