Default Messaging Provider Problem Determination - IBM Redbooks

More documents

Recommendations

Info

32079 bytes in size. The WebSphere MQ client link configuration is checked and all appears correct. Ensure that you are using the latest version of the WebSphere MQ client code by checking the jar files that are used by the JMS application and by verifying that they are at the current service level. See the following link for additional information: http://www.ibm.com/software/integration/mqfamily/support/summary Having established what we believe to be a product defect, we refer to “The next step” on page 50 for what to do next. Message CWSID0032W One minor problem found during the writing of this book was the message code CWSID0032W during startup. See Example 25. Example 25 CWSID0032W during startup SibMessage E [busname] CWSID0032W: An inconsistency in the WCCM document sib-engines.xml was detected; reason uuid=B77F76AAB6EC0BC35414B268 targetUuid=B77F76AAB6EC0BC35414B268 The next step Note: This problem has been resolved in the 6.0.2 refresh pack. The error did not appear to cause any problems to the runtime and was resolved by the installation of refresh pack 6.0.2. The symptoms and problem areas included in this paper are some that you are more likely to experience. However, there are other things that can go wrong, or the cause of the problem might be related to a component other than the default messaging provider. If, after going through this process, you still have an undiagnosed problem, we recommend that you go back to Approach to Problem Determination in WebSphere Application Server V6, REDP-4073, at: http://www.redbooks.ibm.com/redpapers/pdfs/redp4073.pdf Review the “Classify the problem and determine the root cause” section to see if there are any other components that might be causing the problem. If you feel sure you have a messaging problem, there are things you can do before contacting IBM support. First, you should review the documentation you 50 WebSphere Application Server V6: Default Messaging Provider Problem Determination
have gathered for errors related to the problem that were not addressed in this paper and search support sites for information or fixes. The WebSphere Information Center contains problem determination information for troubleshooting service integration technologies. Take the time to review this information to see if there are any tips that will help you. You can find this guide at: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere. pmc.nd.doc/ref/rjk_prob0.html To assist the service organization it is useful to gather appropriate documentation. As we have mentioned, there are some basics such as SystemOut.log, SystemErr.log, server logs, and the exception logs from the FFDC directory. From your own analysis, you might have determined that traces would also be required. Before doing so, remember the following: ► Make the documentation relevant. Ensure that the documentation is recent and that it shows the problem. ► Provide a clear and concise description of the problem. By now, you have investigated the problem yourself, and you have a good understanding of how the problem occurs. ► Is the problem easily recreated? If possible, describe the steps that are needed to reproduce the problem or provide a small test case to demonstrate the problem. It is easier to diagnose and fix a problem with a suitable small test case that does not require a large configuration (for example using databases or network configurations). The service organization is aware that this is not always possible. ► Can you gather a suitable trace for the problem? Because you have done some preliminary analysis, you might have an understanding of which component you believe is causing the problem. See Table 2 on page 52 for a listing of the trace strings that might be appropriate for the components you believe are responsible. For a list of documentation required to report a problem to IBM support, see Mustgather: Service Integration Technology, at: http://www.ibm.com/support/docview.wss?uid=swg21199330 You can also find general information about what documentation to gather in the Troubleshooting Guide for WebSphere Application Server at: http://www.ibm.com/support/docview.wss?rs=180&context=SSEQTP&uid=swg27005324 If you believe you have identified a messaging component area where the problem exists but have not identified the particular problem, you could attempt WebSphere Application Server V6: Default Messaging Provider Problem Determination 51
Page 1 and 2: Redbooks Paper WebSphere Applicatio
Page 3 and 4: DB Messaging data store WebSphere A
Page 5 and 6: Problem categories Work the problem
Page 7 and 8: You can find information about find
Page 9 and 10: Figure 3 Viewing messages on the qu
Page 11 and 12: Note: In the following examples, th
Page 13 and 14: embedded exception code, CWSIS1524E
Page 15 and 16: : Caused by: java.sql.SQLException:
Page 17 and 18: Tip: Defining the data source for t
Page 19 and 20: Immediately after attempting to tak
Page 21 and 22: : [7/8/05 10:49:26:631 EDT] 0000002
Page 23 and 24: Finally, you must ensure that you d
Page 25 and 26: Message Consumer WebSphere Applicat
Page 27 and 28: Symptom: Messages disappear when us
Page 29 and 30: However, a message code is seen in
Page 31 and 32: CWSIS1538I, which indicate that the
Page 33 and 34: [...] 00000037 SibMessage I [NewBus
Page 35 and 36: Figure 13 Queue destination propert
Page 37 and 38: Figure 14 Exception destination is
Page 39 and 40: Figure 15 Mediation Destination 1 D
Page 41 and 42: Figure 17 Map module to server 5. E
Page 43 and 44: Figure 18 Messages waiting for medi
Page 45 and 46: To connect correctly to the bus, th
Page 47 and 48: the network environment and worksta
Page 49: Product errors If the messaging eng
Page 53 and 54: Notices This information was develo

Default Messaging Provider Problem Determination - IBM Redbooks

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?