Open MQ General FAQ Cannot resolve external resource into attachment.

This page contains General FAQs about the Open MQ Project.

Q: Where are the bugs and issues?
A: Open MQ is the community version of Sun Java System Message Queue. Because of this, we track bugs both through Sun's internal tracking system, as well as with IssueTracker, here at Java Dot Net. At this time, most of our defect tracking happens to be through our internal bug tool (we call it Bugster). One day, we expect to transfer all our issue tracking to a single system. Until then, we have to monitor and manage with two systems. We agree, this is sub-optimal.
You can look for bugs in IssueTracker. These are filed by community members. Access for IssueTracker is via the left-side navigation links, when you are looking at the project site. For your convenience, here's a link you can use:

• IssueTracker Query Page

You can also look for bugs filed in our internal bug tracking system through the Software Developer Network interface at bugs.sun.com. Here are a couple of links to help you with this:

• The basic query page
• A pre-canned query for all Java MQ bugs, sorted by date

Please note that, some customers request that their bugs remain confidential. So, in rare cases, they might not be available publicly.
Q: I need to create a new Issue. What information should I include?
A: As with any problem, the better you can describe exactly what is going on with your test-case; the more likely we will be, to be able to provide a prompt response and either get you on your way, or work your problem into a fix for Open MQ. To help us with this, there are some general things we'd like you to add to the IssueTracker

1. Describe as completely as you can, what you were using, what you expected would happen, and what actually happened.
2. Include all other products which are interacting with Open MQ, and their versions.
3. If you are able to reproduce this problem, please include the steps you used for this. If you have a test case, and can supply the code, that would be best.
4. Always attach a complete log file. You will find these in the (imq-root)/var/logs directory. Please include the complete file, not just an extract. If at all possible, limit the operation to startup and the error. We realize this isn't always possible.
5. If your issue involves other systems (i.e. GlassFish Application Server, or Directory Server / LDAP, or something else, also consider including the logs from that component as well. If you can adjust the granularity of logging on those systems, so that they show the JMS operations that will be useful.
6. Finally, do have a look at the Unsupported Commands Wiki page. This will show you a host of additional diagnostic commands that might help you document your issue.