Petals Distribution

Handle relative path for component properties files during deploy

Details

  • Type: Bug Bug
  • Status: New New
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 5.1.0
  • Fix Version/s: 6.0.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    While deploying with a property files from cli, giving a property file with a relative path will always fail. The container will not be able to resolve the path:

    # Petals cli :
deploy -u mvn:org.ow2.petals/petals-bc-rest/1.2.0/zip -D propertiesFile=./conf/rest.properties
ERROR on line 3: org.ow2.petals.admin.api.exception.ArtifactAdministrationException: org.ow2.petals.jmx.api.api.exception.InstallerComponentErrorException: org.ow2.petals.jmx.api.impl.exception.PerformActionErrorException: java.rmi.UnmarshalException: Error unmarshaling return; nested exception is: 
	java.lang.ClassNotFoundException: com.ebmwebsourcing.easycommons.properties.PropertiesException (no security manager: RMI class loader disabled)

    # Petals ESB:
sample-0 2018/06/01 15:39:32,864 GMT+0200 SEVERE [Petals.Container.Lifecycle.Installer] : Can't install component
javax.jbi.JBIException: com.ebmwebsourcing.easycommons.properties.PropertiesException: PETALS_HOME is not defined

    In that case, container should rely on 'server.properties' to try to resolve the path.

    Show
    While deploying with a property files from cli, giving a property file with a relative path will always fail. The container will not be able to resolve the path: 
    # Petals cli :
deploy -u mvn:org.ow2.petals/petals-bc-rest/1.2.0/zip -D propertiesFile=./conf/rest.properties
ERROR on line 3: org.ow2.petals.admin.api.exception.ArtifactAdministrationException: org.ow2.petals.jmx.api.api.exception.InstallerComponentErrorException: org.ow2.petals.jmx.api.impl.exception.PerformActionErrorException: java.rmi.UnmarshalException: Error unmarshaling return; nested exception is: 
	java.lang.ClassNotFoundException: com.ebmwebsourcing.easycommons.properties.PropertiesException (no security manager: RMI class loader disabled)

    # Petals ESB:
sample-0 2018/06/01 15:39:32,864 GMT+0200 SEVERE [Petals.Container.Lifecycle.Installer] : Can't install component
javax.jbi.JBIException: com.ebmwebsourcing.easycommons.properties.PropertiesException: PETALS_HOME is not defined
    In that case, container should rely on 'server.properties' to try to resolve the path.
  • Environment:
    Unix

Activity

Ascending order - Click to sort in descending order
Christophe DENEUX made changes - Mon, 4 Jun 2018 - 12:06:18 +0200
Field Original Value New Value
Project Petals ESB Container [ 10029 ] Petals Distribution [ 10180 ]
Key PETALSESBCONT-457 PETALSDISTRIB-361
Issue Type Improvement Request [ 4 ] Bug [ 1 ]
Affects Version/s 5.1.0 [ 10699 ]
Affects Version/s 5.2.0 [ 10764 ]
Christophe DENEUX made changes - Mon, 4 Jun 2018 - 12:06:35 +0200
Fix Version/s 6.0.0 [ 10455 ]
Priority Major [ 3 ]

People

Dates

  • Created:
    Fri, 1 Jun 2018 - 16:21:03 +0200
    Updated:
    Fri, 13 Dec 2019 - 15:52:06 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.