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 other problems when developing message flows
Use the advice given here to deal with problems that can arise when developing message flows, and that are not covered in the specific categories listed in "Resolving problems when developing message flows"
- The values of your promoted properties are lost after editing
- The Message Flow editor experiences problems when opening a message flow, and opens in error mode
- A message flow has subflows with the same user-defined property set to different values, but only one value is set at run time
- You want to move resources to a new broker schema that you have created but it is not visible in the Broker Development view
- A selector exception is raised when you use WebSphere Adapters
The values of your promoted properties are lost after editing
- Scenario: You edited a message flow using the Message Flow editor, and the values of your promoted properties are lost.
- Explanation: The values of promoted properties for nodes with more than a single subflow definition (that is, two identically named subflows in the same project reference path) are lost if the flow is edited and saved.
- Solution: To avoid this problem, ensure that each subflow in your project has a different name.
The Message Flow editor experiences problems when opening a message flow, and opens in error mode
- Scenario: You attempt to open an existing message flow in the Message Flow editor and it opens in read-only error mode, displaying a list of parsing or loading errors. The message flow is not open and a message is displayed indicating that the message flow file is not valid.
- Explanation: The message flow file is unreadable or is corrupted, and the Message Flow editor cannot render the model graphically.
- Solution: Contact IBM® Customer Support for assistance with the corrupted file.
A message flow has subflows with the same user-defined property set to different values, but only one value is set at run time
- Scenario: You have a message flow that contains identical subflows. Each subflow has the same user-defined property (UDP), but with different values. At run time, only one of the values is set.
- Explanation: A UDP has global scope and is not specific to a particular subflow. If you reuse a subflow in a message flow, and those subflows have identical UDPs, you cannot set the UDPs to different values.
- Solution: If you need to set a different value for each subflow, use a different UDP for each subflow.