You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by eklas <kl...@netgiro.com> on 2006/08/30 08:29:59 UTC

ActiveMQMapMessage, DataOutputStream and UTFDataFormatException

Hi

Why is the ActiveMQ MapMessage using the java.io.DataOutputStream
that has a 64 k bytes limitation on string properties?

Caused by: java.io.UTFDataFormatException: encoded string too long: 100026
bytes
 at java.io.DataOutputStream.writeUTF(DataOutputStream.java:347)
 at java.io.DataOutputStream.writeUTF(DataOutputStream.java:306)
 at
org.apache.activemq.util.MarshallingSupport.marshalPrimitive(MarshallingSupport.java:125)
 at
org.apache.activemq.util.MarshallingSupport.marshalPrimitiveMap(MarshallingSupport.java:59)
 at
org.apache.activemq.command.ActiveMQMapMessage.storeContent(ActiveMQMapMessage.java:114)


-- 
View this message in context: http://www.nabble.com/ActiveMQMapMessage%2C-DataOutputStream-and-UTFDataFormatException-tf2188017.html#a6053175
Sent from the ActiveMQ - User forum at Nabble.com.

Re: ActiveMQMapMessage, DataOutputStream and UTFDataFormatException

Posted by eklas <kl...@netgiro.com>.
Hi

I used activemq v4.0.
Today I've tried a snapshot of v4.0.2.
I no longer have the 64K problem of the DataOutputStream.
Instead I've stumbled into:
ERROR JournalPersistenceAdapter      - Failed to checkpoint a message store:
edu.emory.mathcs.backport.java.util.concurrent.ExecutionException:
java.io.IOException: Not started.
edu.emory.mathcs.backport.java.util.concurrent.ExecutionException:
java.io.IOException: Not started.
        at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:299)
        at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:118)
        at
org.apache.activemq.store.journal.JournalPersistenceAdapter.doCheckpoint(JournalPersistenceAdapter.java:377)
        at
org.apache.activemq.store.journal.JournalPersistenceAdapter$2.iterate(JournalPersistenceAdapter.java:121)
        at
org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:87)
        at
org.apache.activemq.thread.DedicatedTaskRunner.access$000(DedicatedTaskRunner.java:24)


rajdavies wrote:
> 
> which version of ActiveMQ are you using? This restriction was  
> recently removed - perhaps you can try a snapshot release ?
> e.g. http://people.apache.org/maven-snapshot-repository/org/apache/ 
> activemq/apache-activemq/
> 

-- 
View this message in context: http://www.nabble.com/ActiveMQMapMessage%2C-DataOutputStream-and-UTFDataFormatException-tf2188017.html#a6057919
Sent from the ActiveMQ - User forum at Nabble.com.

Re: ActiveMQMapMessage, DataOutputStream and UTFDataFormatException

Posted by Rob Davies <ra...@gmail.com>.
which version of ActiveMQ are you using? This restriction was  
recently removed - perhaps you can try a snapshot release ?
e.g. http://people.apache.org/maven-snapshot-repository/org/apache/ 
activemq/apache-activemq/

On 30 Aug 2006, at 07:29, eklas wrote:

>
> Hi
>
> Why is the ActiveMQ MapMessage using the java.io.DataOutputStream
> that has a 64 k bytes limitation on string properties?
>
> Caused by: java.io.UTFDataFormatException: encoded string too long:  
> 100026
> bytes
>  at java.io.DataOutputStream.writeUTF(DataOutputStream.java:347)
>  at java.io.DataOutputStream.writeUTF(DataOutputStream.java:306)
>  at
> org.apache.activemq.util.MarshallingSupport.marshalPrimitive 
> (MarshallingSupport.java:125)
>  at
> org.apache.activemq.util.MarshallingSupport.marshalPrimitiveMap 
> (MarshallingSupport.java:59)
>  at
> org.apache.activemq.command.ActiveMQMapMessage.storeContent 
> (ActiveMQMapMessage.java:114)
>
>
> -- 
> View this message in context: http://www.nabble.com/ 
> ActiveMQMapMessage%2C-DataOutputStream-and-UTFDataFormatException- 
> tf2188017.html#a6053175
> Sent from the ActiveMQ - User forum at Nabble.com.
>