WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Resolving problems when you use HTTP and SOAP nodes
Use the advice that is given here to help you to resolve common problems that can arise when you develop web Services message flows that contain HTTP and SOAP nodes.
If you experience problems
when you use HTTP and SOAP nodes in message flows, complete the instructions
for the following scenarios to diagnose and solve the problem.
- Error message BIP3689 is issued when you deploy or restart an execution group
- Warning message BIP3690 is issued when you deploy or restart an execution group
- A HandshakeException is issued when you use an HTTPRequest node to make an HTTPS call
Use the replies to the following questions to assist you in diagnosing problems with HTTP or SOAP nodes:
Error message BIP3689 is issued when you deploy or restart an execution group
- Scenario: You configure Web Services Reliable Messaging (WS-RM) on one or more nodes in your message flow configuration. When you attempt to deploy the configuration to an execution group, or to restart the execution group, you see a BIP3689 error message.
- Explanation: Two or more nodes in your deployment configuration have the same value for the Path suffix for URL property, and at least one of these nodes is using WS-RM. Using the same URL twice is not allowed, as one execution group might get messages intended for another execution group, therefore breaking the WS-RM message ordering.
- Solution: Review the values for the Path suffix for URL property in the nodes that you plan to deploy to the same broker. Ensure that the URL for a node that is using WS-RM is not used anywhere else in the deployment configuration.
Warning message BIP3690 is issued when you deploy or restart an execution group
A HandshakeException is issued when you use an HTTPRequest node to make an HTTPS call
How do I tell which listener the HTTP and SOAP nodes are using?
If you are experiencing problems with message flows that contain
HTTP or SOAP nodes, and you want to collect trace
information to provide to your IBM® Support
Center, trace the execution group. If you are using the broker-wide
listener for HTTP or SOAP nodes, also trace the
HTTPListener component.
How do I collect HTTPListener trace?
To gather information about HTTP nodes and listeners, you must start trace, run your message flows, then retrieve and format the trace information.
Trace the execution group and the HTTPListener component:
Save the trace output so that you can
send it to the IBM Support Center,
if requested.
Turn off trace when you finish collecting information to avoid affecting the performance of the broker.