Validation Panel Message | Possible Reason | Solution | Further Information |
---|
An error has occurred during the compilation of the project | This error is shown if the communication with the compiler failed. | - Try to clear the Compiler cache and deploy again.
- If the problem persists, contact the support team.
|
|
An error has occurred during the project data preparation | This error is shown if the code preparing the zip file for the compiler encounters an error. | - Check your code for erroneous data or bugs.
- If the problem persists, contact the support team.
|
|
REST interface classes: urn.AddressImplementation.Address.Public.Address, urn. Data_Model.com.Address share common class name 'Address' but class names in REST interface must be unique. | There are duplicate class names in your model. | Your BPMN model name (in our example: Address ) and a class of a BPMN message (in our example com.Address ) have the same name. Rename the BPMN or message class. | |
Version of the project ('21.2') is not compliant with semver format (major.minor.patch).
| The version number of your service is not written in the correct notation.
| Change the version number of your service. The number must follow Semantic Versioning 2.0.0: Major.Minor.Patch. A pre-release tag is optional. | |
[VALXUML] Attribute '@name' on element 'pins' has not a whitespace-less value.
| The name of an attribute in an imported library contains whitespaces.
| - In the Designer, special characters or whitespaces are not allowed in element names. The library developer must fix the erroneous names before importing the library.
- if you are using an SAP connector, you may have run into this compatiblity issue (see Migration Notes).
| |
[VALXUML] Attribute '@type' on element 'pins' has no (non-empty) value. | An imported library contains empty elements.
| The library developer must fix the erroneous elements before importing the library. | |
java.lang.OutOfMemoryError: GC overhead limit exceeded | Thi error is shown when the compiler service cannot claim enough resources (memory) for itself. | - Ask your PAS administrator to restart the compiler service.
- If the error occurs frequently, your administrator should check whether he can permanently provide more resources for the compiler.
|
|
javax.ws.rs.ProcessingException: java.io.IOException: Error writing to server
| The deployment took to long and ran in a timeout.
| - Check if all service properties are set correctly. Reload the Designer and restart the deployment of your service.
- As a workaround you can deploy the service repository file directly in the integration component (Bridge), see Deploying a Service in the Integration Component below for details.
| |