Problem

A deployed xUML service fails to start with error: Could not start server!.
The error message is displayed either in the standard log (see section Logging of xUML Services Logging of xUML Services) or in the E2E xUML Model Compiler after deploying the xUML service with option startup selected.

Solution

The problem described above can have the following reasons:

• Another xUML service is already running on the same control port (see Control Port already in use).
• ipv6 is disabled on your server.
• You tried to deploy an xUML service with defined SAP backends, but the required libraries are missing (see SAP Libraries Missing).
• The xUML service uses features that require a specific E2E xUML Runtime version and you are trying to run it on an E2E Bridge with a lower Runtime version (see Starting and Stopping xUML Services).
• The number of running processes and used memory might be limited by the local system account of Windows (see Windows Limitation on the number of startable services).
• The service uses a persistent state database which is not available at startup (see Installing and Configuring Database Access or Troubleshooting Database Access).

Steps:

1. Check the bridgeserver log of the xUML service. It contains details about errors that might have occurred (see xUML Service Standard Log).
2. Check the start log of the xUML service. It contains the environment variables that were set at startup time and information about errors that might have occurred. For more details, see xUML Service Start Log.
3. If ipv6 is disabled on your server, try starting the service with option --http.service.bind.default-af set to inet (see xUML Runtime Command Line Options for more).

4. It may be that none of the above mentioned issues apply to your problem and the service logs do not contain any helpful information. To dig further down the problem, you can try starting the service from a system terminal. The terminal shows more logging information and this may help to narrow down the problem.

   Note
   icon false
   Use this for debugging purposes only - don't keep a manually started service running! The E2E Bridge will not in all cases recognize this service as running.

   The data directory of the Bridge (default location: E2E_BRIDGE_DATA) contains one directory named bridge_<name of the service> for every service. This service directory contains a start script in folder bin (start.bat on Windows systems, start.sh on Unix systems.

   Call this start script as follows:

   Code Block
   language none
   start.bat <name of the program directory of the Bridge> e.g. in Windows: C:\E2E_BRIDGE_DATA\bridge_TransactionProcessing\bin> start.bat c:\E2E_BRIDGE_PROG

   After you have finished analyzing the service startup problems, stop the manually started service with the stop.bat (Windows), stop.sh (Unix) script from the same folder, or press Ctrl-C or stop it in the E2E Bridge.