Got error when sending message with big size

Question

Hello!
I hope someone will able to help. I am facing with the size issue (I guess).
The input file has a size of 58668 bytes. My program takes it and convert it to a TextMessage. When sending the file to the JMS queue, I got:
javax.jms.JMSException: Failed to process message: Failed to add message=ID:f411d6c8-c1df-1004-8942-9b67f9629ee5, destination=QueueName3 (5)
        at org.exolab.jms.messagemgr.MessageMgr.add(MessageMgr.java:199)
        at org.exolab.jms.server.ServerSessionImpl.send(ServerSessionImpl.java:205)
        at org.exolab.jms.server.net.RemoteServerSession.send(RemoteServerSession.java:152)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.exolab.jms.net.orb.DefaultORB$Handler.invoke(DefaultORB.java:553)
        at org.exolab.jms.net.orb.DefaultORB$1.run(DefaultORB.java:511)
        at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Thread.java:595)This error is generated when doing:
if(message instanceof TextMessage)
      this.producer.send(message);
  }producer is a MessageProducer.
I looked around and did not find any limitation on the send method :o(
FYI I am using OpenJMS has JMS provider.
Thx in advance

Answer 1

oh I looked into OpenJMS log (I could do that from the beginning) and I saw the following message:
17:00:11.005 ERROR [ORB-Worker-18] - Failed to process message
javax.jms.JMSException: Failed to process message: Failed to add message=ID:f3e38ebc-c1df-1004-8ecc-3d4e4e499b90, destination=
QueueName3 (5)
        at org.exolab.jms.messagemgr.MessageMgr.add(MessageMgr.java:199)
        at org.exolab.jms.server.ServerSessionImpl.send(ServerSessionImpl.java:205)
        at org.exolab.jms.server.net.RemoteServerSession.send(RemoteServerSession.java:152)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.exolab.jms.net.orb.DefaultORB$Handler.invoke(DefaultORB.java:553)
        at org.exolab.jms.net.orb.DefaultORB$1.run(DefaultORB.java:511)
        at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Thread.java:595)
17:00:41.333 ERROR [ORB-Worker-18] - Failed to process message
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(Unknown Source)
        at org.apache.derby.iapi.types.SQLBinary.checkHostVariable(Unknown Source)
        at org.apache.derby.exe.ac601a400fx0110xbb05xf3e9xffff95b19c308.e0(Unknown Source)
        at org.apache.derby.impl.services.reflect.DirectCall.invoke(Unknown Source)
        at org.apache.derby.impl.sql.execute.RowResultSet.getNextRowCore(Unknown Source)
        at org.apache.derby.impl.sql.execute.NormalizeResultSet.getNextRowCore(Unknown Source)
        at org.apache.derby.impl.sql.execute.DMLWriteResultSet.getNextRowCore(Unknown Source)
        at org.apache.derby.impl.sql.execute.InsertResultSet.open(Unknown Source)
        at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
...From what I understand, my issue is related to OpenJMS. Can the length be increased?