...
You can also amend the port more simply using the -p option to qpid-server i.e. qpid-server -p <my port number'
I'm
...
The sleepycat exceptions are thrown from the Berkley DB code which we use for persistence.
Exceptions thrown here generally indicate a problem writing to the lock file for the database. Note that the value of the environment variable QPID_WORK defines the path to the bdb directory into which the lock file & db are written. If QPID_WORK is not set before starting the broker it will default to $HOME and the BDB files will be thus written to $HOME/bdb.
Common causes of problems like this include:
- you already have a broker running with the same BDB path and a lock file, thus you cannot start another one with the same work directory. Try changing QPID_WORK before starting another broker.
- the device into which the lock file would be written is full (or otherwise not writeable). Try changing QPID_WORK to be /tmp or somewhere else and restart to see if this is the issue.
I'm having problems with my classpath. How can I ensure that my classpath is ok ?
...
... then you know the broker started up. If not, then it didn't.
If you still can't figure out the problem (and you are in dev not prod) then drop us an email 'IBTech Qpid Developers' or use JPMIM "qpid users" to contact us.
When I try to send messages to a queue I'm getting a error as the queue does not exist. What can I do ?
In Qpid queues need a consumer before they really exist, unless you have used the virtualhosts.xml file to specify queues which should always be created at broker startup. If you don't want to use this config, then simply ensure that you consume first from queue before staring to publish to it. See the entry on our Qpid Java FAQ for more details of using the virtualhosts.xml route.