Did you see the -L/tp64/boost/1.44.0 option passed to the command that
failed?
Is libboost_program_options.so (and the other Boost libs) in
/tp64/boost/1.44.0? Or in a subdirectory of that? I'm guessing a
subdirectory - you would need to specify the complete path to the
directory where the libs
Just btw, you can mark the queue as durable without making the message
persistent, in which case there would be no performance penalty.
Thanks, yeah I realise that, but you have to explicitly mark the
messages as not persistent, certainly for JMS the spec says that should
be the default and I
Youre right, the library files are in the lib subdirectory. Here's the partial
failed command which does contain the correct -L option.
iverBody.o ./qpid/framing/.libs/AMQP_ClientProxy.o
./qpid/framing/.libs/ClusterConnectionDeliveryRecordBody.o
./qpid/framing/.libs/SessionAttachBody.o ./qpi\
On 03/15/2012 05:27 PM, Fraser Adams wrote:
I *assume* that there are no sneaky little optimisations going on under
the hood when client and broker are located on the same host, like
let's do some memory mapping and bypass the TCP/IP stack
No, there is no special code for co-location at
