I'm not familiar with the Solace broker and the error doesnt really say much, but if you think it is related to credentials, perhaps the old broker didnt actually require them and maybe you werent actually sending them, but the new one does. You could try enabling the protocol trace log to see what is being sent/received. Run the program with PN_TRACE_FRM=1. Note if there is authentication steps going on there will be details of that, so dont just paste the full output here.
On Thu, 13 Apr 2023 at 13:23, didier pavet <dpa4aviat...@gmail.com> wrote: > > Hello all, > > In the european aviation community a well know provider of flight data has > change its internal AMQP1.0 broker, switching from Apache ActiveMQ to > Solace PubSub+. > A set of our application but very few in fact use Python3 and interrogate > this AMQP broker. > So we have too few experience in this matter. > I use to maintain a library built above Apache qpid::proton which has work > very well > while we were accessing Apache ActiveMQ, the former version. > > Reaching Solace PubSub+, i face some insidious error : > ERROR:proton:SMF AD open flow response error > (which seems linked to "credential") but i do not succeed to localize . > > And afterwards, the queue or subscription are empty object . > The run() method of proton.reactor.Container instance that i use abruptally > end > very soon. > Has someone already experience that or can help me to choose the area where > i am supposed to dig into ? > > Many thanks . > > Didier (happy to share my issue ;-) ) --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
