Troubleshooting Guide

This chapter provides information on resolving issues you might encounter when running Team for Capella. This section is suitable for all profiles.

1. The Error Log View

To open the Error log view:

  • Window > Show View > Other…​, then search Error Log:

open view

  • Or, click on the search icon and search Error Log:

view search error log

When there’s a problem, the first thing to check is the error log:

error log

If errors are present, you can view the call stack and copy it:

error detail evloop npe

2. Sirius Session Details

The Sirius Session Details is available in properties page of the .aird file of a Capella project with opened session (right-click > Properties):

sirius session detail

This page contains information about resources, size, number of elements, number of representations, activated Viewpoints.

3. Collaborative Session Details

The Collaborative Session Details is available in properties page of the .aird file of a Capella project with opened session (right-click > Properties):

collaborative session detail

This page contains information about user, locked objects, connection.

4. Invalid License

When there’s an "invalid license" issue, you should check:

  • The license server monitoring, in Status and Statistics tabs.For example, on the left you’ll see the status tab with no error, and on the right with an error:

license server status

  • The License Server - Run job status and log, at the left the License Server is running but not at the right:

jenkins server license running

If a BadPaddingException is reported like here in the log:

license server console error

  • Stop the License Server - Run job

  • Delete the .ols files in lic-server/OLS

  • Re-extract the OLS_xxx.zip in to have 4 .ols files in lic-server/OLS

  • Start the License Server - Run job

  • Try to connect again with the Team for Capella client

5. Connection Issues

test connection access denied
Figure 1. the password is wrong
test connection no such user
Figure 2. the username is wrong
authentication fail message
Figure 3. the username or the password is wrong
test connection repo not found
Figure 4. the repository name is wrong or the repository is stopped
test connection cannot connect repository
Figure 5. the server is stopped or the hostname/port/connection type is wrong
server connection error message
Figure 6. the server is stopped or the hostname/port/connection type is wrong

6. Stopped Server or Repository

If the server or the repository is stopped:

  • Check the Server - Run Job status and its console log,

  • launch Server - List active repositories job and check the console log,

  • check the status and logs of the latest Project – Import – xxx jobs,

  • check the job configuration: some options can stop the repository or the server in the case of issue during backup:

    • -stopRepositoryOnFailure true (in default job configuration),

    • -closeserveronfailure true,

  • analyze the job logs, most common issues:

    • a new add-on has been added in the client bundle without installing it on the server-side.

    • corrupted data (invalid representation descriptor, wrongly managed dangling/proxy reference).

7. No More Responding Server

If in previous check (Stopped Server or Repository), server is still running, check:

  • Backup – Database job status and duration

  • Project – Import - xxx job (targeted repo) status and duration

  • Capella/OpenJDK Platform binary processes in the Windows task manager:

task manager capella

  • No responding clients, with longer than usual job duration or failed jobs, and high CPU/RAM consumption can indicate that Java XMX (and maybe RAM) must be increased for importer, server and/or client.

  • Make sure that sum of all XMX (importer.bat, server.ini, lic-server.ini, Jenkins) is below the physical RAM amount.

8. No More Responding Clients on Shared Client VM

If server issue is excluded (No More Responding Server):

  • Try to disable “link with editor” capabilities link with editor in Semantic Browser and other views.

  • Reduce the number of open editors.

  • Check the number of connected users.

  • Check the number of launched Capella instance.

  • Check the RAM amount of each Capella process in the Windows task manager.

  • Check that there is no SWAP.

  • Evaluate the xmx increase in capella.ini.

9. Importer: Fail to Start the New CDOServer

If the importer fails with this error:

javax.xl.stream.XMLStreamException: ParseError at [row,col]:[1,1]

It means the target repository is stopped or does not exist.

10. Job failing with wrong argument

If a job like "Server - List connected projects and locks" fails with an error message similar to

!MESSAGE port must be an integer java.lang.NumberFormatException: For input string: "-Dosgi.requiredJavaVersion=14" at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:68)

You should check the capella.ini or the exectued script file, as the "-vmargs" argument may have been deleted.