[rabbitmq-discuss] NPE in RpcClient

Neil Ellis neil.ellis at mangala.co.uk
Fri Apr 4 20:10:16 BST 2008

Hi Matthias

That's just how it's done in the Mule connector, it's making use of  
the same client for RPC calls and non RPC calls. I think Tony put that  
together so you may want to chat with him, I'm sure Ross would be  
happy to change it if there is a better strategy.

Kind regards
On 4 Apr 2008, at 20:03, Matthias Radestock wrote:

> Neil,
> Neil Ellis wrote:
>> Not sure if this has already been reported; in version 1.2.0 of lib- 
>> rabbitmq there is a NPE if the publish() method has been called on  
>> RpcClient because the temp queue picks it up and attempts to call  
>> setBody() on the blocker. Trivially chaning blocker.set(body) to  
>> have a NP check fixes this:
>>                   if(blocker != null)  
>> {                                               blocker.set(body);
>>                    }
> Why would you call publish() on the RpcClient? You are meant to be  
> using one of
>  byte[] primitiveCall(byte[] message)
>  String stringCall(String message)
>  Map mapCall(Map message)
>  Map mapCall(Object[] keyValuePairs)
> to perform an RPC.
> Matthias.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2431 bytes
Desc: not available
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20080404/b54e0007/attachment.bin 

More information about the rabbitmq-discuss mailing list