I am not sure what happenned before -- but now the java client can connect to the c++ broker and receive the helloworld message from the c++ topic producer.
I changed the helloworld message to only publish, and modified the java topic consumer to receive. the only issue was that the java consumer thought it might get a TextMessage class type, but it was a JMSBytesMessage instead. On Mon, Oct 29, 2012 at 11:28 PM, Gordon Sim <gordon.r....@gmail.com> wrote: > On 10/29/2012 10:45 PM, Sean K wrote: >> >> I am getting similar if not exact situation. >> >> I am using 0.18 c++ bundle, and the 0.18 java bundle. >> >> When I try to mix the two together, they do not work -- attempting to >> connect to localhost. >> >> They work separately in their own language enclave. > > > Are there any errors on the broker? Did you try java-client->c++-server and > c++-client->java-server or just one of them? > > Can you log a protocol trace for a failed example? (E.g. on c++ client > export QPID_LOG_ENABLE=trace+:amqp_0_10 or on qpidd use '--log-enable > trace+:amqp_0_10 --log-enable info+'). > > > > --------------------------------------------------------------------- > 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
