![]() |
![]() |
![]() |
![]() |
![]() |
Troubleshooting
The Simulators Stop Communicating
The SDL Simulator and the SDL and TTCN Integrated Simulator may stop communicating. This can occur if there are "old" instances of the SDL and TTCN Integrated Simulator ETS process still alive. They will then "steal" messages from the intended recipient. There are some ways to make the Simulators communicate again:
- Exit the SDL and TTCN Integrated Simulator and start it again.
- Exit the SDL and TTCN Integrated Simulator. Restart the SDL Simulator. Start the SDL and TTCN Integrated Simulator again.
- Exit the Simulators and the Organizer. Check that no Postmaster process and no SDL and TTCN Integrated Simulator ETS process remains. If they do, kill them. Start the Organizer, the SDL Simulator and the SDL and TTCN Integrated Simulator.
Test Execution Stops
The execution of tests may stop at a certain point during execution for no reason. If the problem is reproducible, you should check the supported types. There is a possibility that a type has been used in a message between the simulators that is not supported.
The Simulators Get Out of Sync
The simulators may get out of sync. One way of doing this is when an execution in the SDL and TTCN Integrated Simulator has been aborted and the SDL Simulator has not been restarted.
http://www.ibm.com/rational |
![]() |
![]() |
![]() |
![]() |