I'm facing the same issue with apache-activemq-4.1.0 right now.
I have faced something simillar earlier.
looks like it's coded in Oracle driver to accept nothing greater than 4K as
a blob/byte[]/clob/char[]
below is how i fixed it (came across the solution somewhere i guess) :
Hi,
> I did a build from trunk and tested it. It works fine now.
I checked out the code, built it and tried running it but somehow it never
worked for me!!
I then modified the OracleJDBCAdapter which uploads Blobs > 4k now.
Attaching the code herewith! it's not the neatest way but that's only
Hi,
> I did a build from trunk and tested it. It works fine now.
I checked out the code, built it and tried running it but somehow it never
worked for me!!
I then modified the OracleJDBCAdapter which uploads Blobs > 4k now.
Attaching the code herewith! it's not the neatest way but that's only
Hi,
I am using JDBCPersistence (without journaling) in my product.
There are times when :
- my broker goes down
- there are already some messages in the queue as they were not processed
yet.
- my broker comes up again and restores the queue(s)
On the third step, it seems to be executing a simple
Can you share your implementation ?
Thanks in advance.
--
*Regards,*
*Chandra Shekhar Pandey*
*+918826390195*