Hi Harsha, You can enable remote debugging by declaring the standard JVM debug options directly in one of the environment variables used by the qpid-run script (eg JAVA_OPTS, QPID_OPTS) or making 'proper' use of the qpid-run script's handling for JPDA options (open the script, from build\bin or common\bin and youll see the seection with overview about 2/3rds down). If you meant you are starting the broker directly using the Main class within Eclipse then you should be able to debug it directly without any of the above.
As for producing messages, I would look at the org.apache.qpid.example.jmsexample.* packages in client\examples, which provide JMS examples for common messaging use cases using various features of the broker. Robbie 2010/1/14 Harsha Halgaswatta <[email protected]>: > Hi Robbie , Marnei > > After setting sslonly to false i found it is ok . Further my > connection string was admin/admin as credentials. As Marnei mentioned > that did not work. so after changing it to guest/guest it worked. So > thanks a lot for the information.Thanks for the information > > Further i need to know how to enable remote debugging in broker and > feed some messages on the queue in case of invoking subscribers. is > there any readings for this as well. > > Thanks > Harsha. > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
