On Wed, 2010-06-30 at 02:50 -0700, Sodan wrote:
> case PrimitiveValueNode::BYTE_ARRAY_TYPE:
>             {
>                 int size = dataIn.readInt();
>                 std::vector<unsigned char> data;
>                 data.resize( size );
>                 dataIn.readFully( &data[0], size );
>                 value.setByteArray( data );
>                 break;
>             }
> 
> size is 0
> 
> ........

Should be fixed now the in 3.2.x branch in SVN

> 
> 
> 
> Timothy Bish wrote:
> > 
> > On Tue, 2010-06-29 at 06:31 -0700, Sodan wrote:
> >> I have always changed and compiled it as static lib, so no dll.
> >> 3.1.3 works like a charm, 3.2 goes boom. Same setup.
> >> 
> >> dang,
> >> Søren
> > 
> > A sample app that demonstrates the problem would be helpful.
> > 
> > Regards
> > 
> > 
> >> 
> >> 
> >> 
> >> Timothy Bish wrote:
> >> > 
> >> > On Tue, 2010-06-29 at 06:10 -0700, Sodan wrote:
> >> >> btw: we use 5.3.0.4 ActiveMQ.
> >> >> Maybe we need the newest version 5.3.2 to be compatible... ?
> >> >> 
> >> >> Søren
> >> >> 
> >> > 
> >> > There shouldn't be any substantive difference between these versions
> >> > when it comes to sending and receiving MapMessages.  
> >> > 
> >> > Are you ensuring that your application is linking against the AMQCPP
> >> DLL
> >> > using the correct runtime, you must use the Multithreaded Runtime
> >> (Debug
> >> > or Release depending on your build).
> >> > 
> >> > Are you setting any specific URI options?
> >> > 
> >> > Regards
> >> > 
> >> > -- 
> >> > Tim Bish
> >> > 
> >> > Open Source Integration: http://fusesource.com
> >> > ActiveMQ in Action: http://www.manning.com/snyder/
> >> > 
> >> > Follow me on Twitter: http://twitter.com/tabish121
> >> > My Blog: http://timbish.blogspot.com/
> >> > 
> >> > 
> >> > 
> >> 
> > 
> > -- 
> > Tim Bish
> > 
> > Open Source Integration: http://fusesource.com
> > ActiveMQ in Action: http://www.manning.com/snyder/
> > 
> > Follow me on Twitter: http://twitter.com/tabish121
> > My Blog: http://timbish.blogspot.com/
> > 
> > 
> > 
> 


Reply via email to