You are setting that as the JMS ClientID. Given the usage suggested from the logs, I dont expect that should make any difference here. You could simply stop setting a ClientID and let the client auto-generate its container-id to confirm that though.
On 31 May 2018 at 10:58, popalka <popa...@ya.ru> wrote: > I notice that containerId with value 'xxx' is hardcoded in our app. May this > is issue? > > > > > > -- > Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
