Please find here the reference guide of warnings and error raised by the Petals ESB Container
|| Code \\ || Description \\ || How to solve it ? \\ ||
| INST-E0001 \\ | The JBI Identifier of the archive used to upgrade an existing component is not the same as the installed one \\ | * Is the upgrade archive right ?
* If the upgrade archive is right, update its JBI identifier, for example, using the [goal 'jbi-configure' of the Maven Petals Plugin|petalscomponents:Maven Petals Plug-in 2.1.4+#jbi-configure]. |
| INST-E0002 | Unable to upgrade the existing component with the new archive \\ | Check previous errors to know the initial error and refer to its description. \\ |
| INST-E0003 \\ | The version of the upgrade archive is not compliant with the version of the installed component (component namespaces are different in the JBI descriptors) \\ | * Is the upgrade archive right ?
* If versions are not compliant, you must realize a migration instead of an upgrade. |
| INST-E0004 \\ | The mime type of the archive to install is not supported \\ | Supported mime types are listed in the error message. If the detected mime type of your archive is text/html, perhaps have you forgotten to [configure your HTTP proxy|petalsesbsnapshot:Known Problems#HTTPProxySettings] ? \\ |
| INST-E0005 \\ | Error downloading the archive from an HTTP URL \\ | Check the [HTTP response code|http://www.w3.org/Protocols/HTTP/HTRESP.html] to have more information on the error cause. \\ |
| INST-E0006 \\ | Error connecting to the HTTP server to download an archive \\ | Check the stack trace to have more information on the error cause. \\ |
| INST-E0007 \\ | Shared-library not found during component installation \\ | The component that your are installing needs a shared library that is not installed. |
| INST-E0008 \\ | Shared-library version not found during component installation. \\ | The component that your are installing needs a specific version of a shared library previously installed. The shared library is installed but not with the expected version, or its version is not defined. \\ |
| INST-E0009 \\ | The shared library already exists. \\ | A shared library with the same name and same version is already installed. \\ |
| INST-E0010 \\ | A conflict occurs resolving shared library version of a component \\ | The component that you are installing needs a shared library. Several versions of the shared library are installed. A conflict can occurs resolving the version of the shared library to use by the component. \\
\\
In a Petals ESB node where versions 'none' (no version specified), 'v1', 'v2' of the same SL are installed, component installation results according to the specified version are: \\
* 'none': INST-E0010,
* v1 : v1
* v2 : v2
* v3 : INST-E0008 |
| INST-E0011 \\ | A conflict resolving shared library version of a component will occur on next Petals ESB node restart \\ | The shared library that you are installing is another version of a shared library already installed, and it will create a conflict when restarting the Petals ESB node because the already installed shared library is used by an installed component that does not specify the shared library version to use. See INST-E0010 for more information on conflict of shared library version. \\ |
| INST-E0012 \\ | The JBI Identifier of the archive used to upgrade an existing shared library is not the same as the installed one | Is the upgrade archive right ? |
| INST-E0013 \\ | No version 'none' of the shared library is installed \\ | Only version 'none' of shared libraries can be upgraded. Otherwise, you should installed a new version (different from 'none') of the shared library and adapt your components to use it. \\ |
| INST-E0014 \\ | Unable to upgrade the existing shared library with the new archive | Check previous errors to know the initial error and refer to its description. |
| INST-E0015\\ | The endpoint that is deploying already exists\\ | An endpoint that you are installing through a service-assembly already exists in the Petals ESB. Have you deployed the same SA on another Petals node of the topology ? To deploy a service-assembly on two Petals nodes of the same topology, endpoint names MUST be different. Think to use the special endpoint name 'autogenerate'.\\ |
|| Code \\ || Description \\ || How to solve it ? \\ ||
| INST-E0001 \\ | The JBI Identifier of the archive used to upgrade an existing component is not the same as the installed one \\ | * Is the upgrade archive right ?
* If the upgrade archive is right, update its JBI identifier, for example, using the [goal 'jbi-configure' of the Maven Petals Plugin|petalscomponents:Maven Petals Plug-in 2.1.4+#jbi-configure]. |
| INST-E0002 | Unable to upgrade the existing component with the new archive \\ | Check previous errors to know the initial error and refer to its description. \\ |
| INST-E0003 \\ | The version of the upgrade archive is not compliant with the version of the installed component (component namespaces are different in the JBI descriptors) \\ | * Is the upgrade archive right ?
* If versions are not compliant, you must realize a migration instead of an upgrade. |
| INST-E0004 \\ | The mime type of the archive to install is not supported \\ | Supported mime types are listed in the error message. If the detected mime type of your archive is text/html, perhaps have you forgotten to [configure your HTTP proxy|petalsesbsnapshot:Known Problems#HTTPProxySettings] ? \\ |
| INST-E0005 \\ | Error downloading the archive from an HTTP URL \\ | Check the [HTTP response code|http://www.w3.org/Protocols/HTTP/HTRESP.html] to have more information on the error cause. \\ |
| INST-E0006 \\ | Error connecting to the HTTP server to download an archive \\ | Check the stack trace to have more information on the error cause. \\ |
| INST-E0007 \\ | Shared-library not found during component installation \\ | The component that your are installing needs a shared library that is not installed. |
| INST-E0008 \\ | Shared-library version not found during component installation. \\ | The component that your are installing needs a specific version of a shared library previously installed. The shared library is installed but not with the expected version, or its version is not defined. \\ |
| INST-E0009 \\ | The shared library already exists. \\ | A shared library with the same name and same version is already installed. \\ |
| INST-E0010 \\ | A conflict occurs resolving shared library version of a component \\ | The component that you are installing needs a shared library. Several versions of the shared library are installed. A conflict can occurs resolving the version of the shared library to use by the component. \\
\\
In a Petals ESB node where versions 'none' (no version specified), 'v1', 'v2' of the same SL are installed, component installation results according to the specified version are: \\
* 'none': INST-E0010,
* v1 : v1
* v2 : v2
* v3 : INST-E0008 |
| INST-E0011 \\ | A conflict resolving shared library version of a component will occur on next Petals ESB node restart \\ | The shared library that you are installing is another version of a shared library already installed, and it will create a conflict when restarting the Petals ESB node because the already installed shared library is used by an installed component that does not specify the shared library version to use. See INST-E0010 for more information on conflict of shared library version. \\ |
| INST-E0012 \\ | The JBI Identifier of the archive used to upgrade an existing shared library is not the same as the installed one | Is the upgrade archive right ? |
| INST-E0013 \\ | No version 'none' of the shared library is installed \\ | Only version 'none' of shared libraries can be upgraded. Otherwise, you should installed a new version (different from 'none') of the shared library and adapt your components to use it. \\ |
| INST-E0014 \\ | Unable to upgrade the existing shared library with the new archive | Check previous errors to know the initial error and refer to its description. |
| INST-E0015\\ | The endpoint that is deploying already exists\\ | An endpoint that you are installing through a service-assembly already exists in the Petals ESB. Have you deployed the same SA on another Petals node of the topology ? To deploy a service-assembly on two Petals nodes of the same topology, endpoint names MUST be different. Think to use the special endpoint name 'autogenerate'.\\ |