Alessio Soldano wrote:
Another thing to consider as workaround, do you build up the Service each time? If you have means for storing the port instance once you get that, that should keep a reference of the bus available when it's created, so you won't need to have a valid client thread default bus anymore later if you re-use the previously contructed port.
At the moment yes & no. The Service is cached, but the call to getPort is reissued every time. Do you know if the proxy returned by getPort is thread safe? I cannot seem to find any indication of it in any of the API docs. If so, I can simply cache the Port and reuse it every time. Otherwise, I guess I will need to create a pool of Ports. But before I start on the pool idea, I would like confirmation that it is or isn't thread safe.
Thanks,
Eric