...

When deploying an xUML service, an error message is displayed that this service already exists: Instance 'xxx' at node 'yyy' exists!

Solution

If a compiled xUML service is deployed to a node instance, the Bridge will check whether an xUML service with the same name has already been deployed before. If you do not have chosen the option to overwrite the xUML service in the Builder project settings (see Deployment of xUML Services), the E2E Model Compiler will report the error shown above.

xUML Service Startup Fails

...

Check the node instance preferences, whether option Disable Automatic Service Startup is checked. This prevents automatic restart for all deployed services.

xUML Service Logs a Warning on Startup

Problem

On xUML service startup, the bridgeserver log reads:

[Warning] [Internal] [RESTLM] [9] [Sending response failed, socket error: 6 "sockets::Socket::writeLine() end failed. Broken pipe"]

Solution

Update to Bridge 7.2.0 resp. Bridge 6.0.30.

RESTLM/9 is thrown, if a client calls a REST or control port operation and does not wait for the answer. In certain cases, the Bridge itself will do this intentionally. The newer Bridge versions take this into account and will not throw this error anymore.

Control Port Already in Use

Problem

If you deploy an xUML service having the same control port as an xUML service already running, it can be deployed, but it cannot be started. In the xUML service log, the following error message is displayed.

[2010-10-04 10:58:06 +0200][Warning][Internal][NETLM][1][Failed to start listener on 120.110.120.52:22022.]
[2010-10-04 10:58:07 +0200][Warning][Internal][NETLM][1][Could not start all listeners. Probably due to conflicting port numbers.]
[2010-10-04 10:58:07 +0200][Fatal][Internal][CTRLLM][8][Starting the listener failed. Most probably ports are already in use.]
[2010-10-04 10:58:07 +0200][Fatal][Internal][SRVLM][7][Controller is not available, startup failed.]

Solution

A control port can only be used by one running xUML service. Check the control port of each deployed xUML service (see xUML Service Details). Either stop the other xUML service on the Bridge first, or adapt the control port of the current xUML service accordingly and deploy it again.

SOAP Port Already in Use

Problem

If you deploy an ¨xUML service using the same SOAP port as an xUML service already running, it can be deployed, but the SOAP port cannot be reserved. In the xUML service log, the following warning is displayed.

[2010-10-04 11:07:23 +0200][Warning][Internal][NETLM][1][Failed to start listener on 120.110.120.52:12022.]
[2010-10-04 11:07:24 +0200][Warning][Internal][NETLM][1][Could not start all listeners. Probably due to conflicting port numbers.]

Solution

A SOAP port can only be used by one running xUML service. Check the SOAP port of each deployed xUML service (see section Service Instances described in xUML Service Details). Either stop the other xUML service on the Bridge first, or adapt the SOAP port of the current xUML service accordingly and deploy it again.

SAP Libraries Missing

Problem

If a deployed xUML service with defined SAP backend fails to start, you need to check, if the necessary library has been installed.

Solution

In the Bridge, select the node instance, to which the xUML service should be deployed, and switch to the Runtime tab. Check, if the corresponding library SAP has been installed. In the highlighted area of the example below, it is indicated that the SAP library has already been installed.

...

Windows Limitation on the Number of Startable Services

Problem

Some Windows systems restrict the number of processes depending on the available memory and other parameters. Because of that, the problem might arouse, that no additional services can be started from the Bridge.

...

The limitation does not apply to Windows Server 2008 R2.

Solution

1. Increase the parameter SharedSection as described in the Microsoft knowledge base.
   SharedSection=xxxx,yyyy,zzzz
   For 32-bit systems, increase value yyyy to 12288 and value zzzz to 1024.
   For 64-bit systems, increase value yyyy to 20480 and value zzzz to 1024.
2. Monitor the HEAP.
   Using the tool dheapmon allows to monitor the HEAP utilization and also the effect of the startup/shutdown of the services to the HEAP.

xUML Service Cannot be Stopped

Problem

An xUML service cannot be stopped via the E2E Bridge.

Solution

In case of a complex xUML service, the shutdown may take longer than usually. Although the error message is displayed that the xUML service could not be stopped, it may still be shutting down. Wait a few seconds and reload the page to refresh the status of the xUML service. If it is still not stopped, you need to kill the corresponding Bridge process.
Check also the stop log of the xUML service. It contains the environment variables that were set during the shutdown and information about errors that might have occurred. For more details, see E2E Composite Service Stop Log.

...