activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tryma <trym.asser...@creuna.no>
Subject Re: ActiveMQ JDBC issue (with Oracle jdbcPersistenceAdapter)
Date Fri, 27 Oct 2006 11:28:16 GMT

We seem to run into this same issue in our environment. We are running on
Linux Red Hat, Incubator ActiveMQ 4.1 and using Oracle 9.2.0.8 for
persistence of messages via thin client drivers (specifically the
ojdbc14.jar library).

The exception we get is the following:

[#|2006-10-27T12:55:11.184+0200|INFO|sun-appserver-ee9.1|javax.enterprise.system.stream.out|_ThreadID=16;_ThreadName=httpWorkerThrea
d-8080-0;|ERROR - MessageProducer.queueMessage(186) | Exception occurred
during send of IndexUpdate JMS message: javax.jms.JMSException: Failed to
broker message: ID:<SERVER>-41736-1161945742694-1:1:1:1:1 in container:
java.sql.SQLException: Data size bigger than max size for this type: 13644
javax.jms.JMSException: Failed to broker message:
ID:<SERVER>-41736-1161945742694-1:1:1:1:1 in container:
java.sql.SQLException: Data size bigger than max size for this type: 13644
        at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:46)
        at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1152)
        at
org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1548)
        at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:465)
        at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:356)
        at
no.creuna.searchengine.queue.MessageProducer.enqueueMessage(MessageProducer.java:204)
        at
no.creuna.searchengine.queue.MessageProducer.queueMessage(MessageProducer.java:167)
...SNIP...
        at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:251)
        at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:205)
        at
com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
        at
com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:103)
Caused by: java.io.IOException: Failed to broker message:
ID:lucene01.elkjop.int-41736-1161945742694-1:1:1:1:1 in container: java.sq
l.SQLException: Data size bigger than max size for this type: 13644
        at
org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:31)
        at
org.apache.activemq.store.jdbc.JDBCMessageStore.addMessage(JDBCMessageStore.java:72)
        at
org.apache.activemq.store.memory.MemoryTransactionStore.addMessage(MemoryTransactionStore.java:224)
        at
org.apache.activemq.store.memory.MemoryTransactionStore$1.addMessage(MemoryTransactionStore.java:117)
        at org.apache.activemq.broker.region.Queue.send(Queue.java:272)
        at
org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:294)
        at
org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:374)
        at
org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:193)
        at
org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:125)
        at
org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:98)
        at
org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:135)
        at
org.apache.activemq.broker.AbstractConnection.processMessage(AbstractConnection.java:434)
        at
org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:604)
        at
org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:238)
        at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
        at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:92)
        at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:67)
        at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:133)
        at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:123)
        at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:88)
        at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
        at java.lang.Thread.run(Thread.java:595)
Caused by: java.sql.SQLException: Data size bigger than max size for this
type: 13644
        at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
        at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
        at oracle.jdbc.ttc7.TTCItem.setArrayData(TTCItem.java:103)
        at
oracle.jdbc.dbaccess.DBDataSetImpl.setBytesBindItem(DBDataSetImpl.java:2484)
        at
oracle.jdbc.driver.OraclePreparedStatement.setItem(OraclePreparedStatement.java:1224)
        at
oracle.jdbc.driver.OraclePreparedStatement.setBytes(OraclePreparedStatement.java:2312)
        at
org.apache.commons.dbcp.DelegatingPreparedStatement.setBytes(DelegatingPreparedStatement.java:105)
        at
org.apache.commons.dbcp.DelegatingPreparedStatement.setBytes(DelegatingPreparedStatement.java:105)
        at
org.apache.activemq.store.jdbc.adapter.DefaultJDBCAdapter.setBinaryData(DefaultJDBCAdapter.java:68)
        at org.apache.activemq.store.jdbc.adapter|#]
        at
org.apache.activemq.store.jdbc.JDBCMessageStore.addMessage(JDBCMessageStore.java:69)
        ... 20 more
|#]

>From what I've read so far Oracle have one suggestion;

"If a large XML document (typically greater than 4000 characters) is
inserted into an XMLType column using a String object in JDBC, the run-time
error "java.sql.SQLException: Data size bigger than max size for this type"
is encountered. This problem can be solved by using a CLOB object to hold
the large XML documents."

but is this really a viable option for me or is there something else we need
to do?

Suggestions are gratefully received! :)


Thanks,
Trym



luser wrote:
> 
> There is a JDBC issue we encounter when testing ActiveMQ.  Our environment
> is Linux EL 3, JVM 1.4.2, ActiveMQ 4.0.  ActiveMQ is configured to use
> Oracle message persistence via thin client drivers.  Here is the content
> of the error message:
> 
> Has anyone seen an issue resembling this before?
> 
> 

-- 
View this message in context: http://www.nabble.com/ActiveMQ-JDBC-issue-tf2035759.html#a7028478
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.


Mime
View raw message