Petals BC MAIL

Error while uninstalling a Mail SU

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Resolution: Duplicate
  • Affects Version/s: 3.2
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    The SU was uninstalled from the "installed" directory.

    0 2012/02/13 14:51:17,176 GMT+0100 SEVERE [Petals.JBI-Management.DeploymentService] : The service assembly 'sa-Mail-ReportMailService-provide' can not be removed from repository
    java.io.IOException: Unable to delete file: D:\Petals-4\petals-esb-4.0\repository\service-assemblies\sa-Mail-ReportMailService-provide-02-13-2012-024958244\install\su-Mail-ReportMa
    ilService-provide\MailService.wsdl
    at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1390)
    at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1044)
    at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:977)
    at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1381)
    at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1044)
    at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:977)
    at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1381)
    at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1044)
    at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:977)
    at org.ow2.petals.system.repository.RepositoryServiceImpl.removePackage(RepositoryServiceImpl.java:676)
    at org.ow2.petals.system.repository.RepositoryServiceImpl.removeServiceAssembly(RepositoryServiceImpl.java:410)
    at org.objectweb.fractal.julia.generated.C36dc48a8_0.removeServiceAssembly(INTERCEPTOR[RepositoryService])
    at org.objectweb.fractal.julia.generated.Cd51ee9d3_0.removeServiceAssembly(INTERFACE[RepositoryService])
    at org.ow2.petals.jbi.management.task.deployment.undeploy.RemoveSADirectoryTask.execute(RemoveSADirectoryTask.java:62)
    at org.ow2.petals.jbi.management.TaskProcessor.process(TaskProcessor.java:78)
    at org.ow2.petals.jbi.management.deployment.DeploymentServiceImpl.undeploy(DeploymentServiceImpl.java:640)
    at org.ow2.petals.jbi.management.deployment.DeploymentServiceImpl.forceUndeploy(DeploymentServiceImpl.java:234)
    at org.objectweb.fractal.julia.generated.C9ae71627_0.forceUndeploy(INTERCEPTOR[DeploymentService])
    at org.objectweb.fractal.julia.generated.C59d5ff32_0.forceUndeploy(INTERFACE[DeploymentService])
    at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.performUndeploySA(AutoLoaderServiceImpl.java:508)
    at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.uninstall(AutoLoaderServiceImpl.java:211)
    at org.ow2.petals.jbi.management.autoload.InstalledDirectoryScanner.run(InstalledDirectoryScanner.java:71)
    at java.util.TimerThread.mainLoop(Unknown Source)
    at java.util.TimerThread.run(Unknown Source)

    There must be an input stream which is not closed correctly and prevents the file from being deleted.

    Show
    The SU was uninstalled from the "installed" directory.
    0 2012/02/13 14:51:17,176 GMT+0100 SEVERE [Petals.JBI-Management.DeploymentService] : The service assembly 'sa-Mail-ReportMailService-provide' can not be removed from repository java.io.IOException: Unable to delete file: D:\Petals-4\petals-esb-4.0\repository\service-assemblies\sa-Mail-ReportMailService-provide-02-13-2012-024958244\install\su-Mail-ReportMa ilService-provide\MailService.wsdl at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1390) at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1044) at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:977) at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1381) at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1044) at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:977) at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1381) at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1044) at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:977) at org.ow2.petals.system.repository.RepositoryServiceImpl.removePackage(RepositoryServiceImpl.java:676) at org.ow2.petals.system.repository.RepositoryServiceImpl.removeServiceAssembly(RepositoryServiceImpl.java:410) at org.objectweb.fractal.julia.generated.C36dc48a8_0.removeServiceAssembly(INTERCEPTOR[RepositoryService]) at org.objectweb.fractal.julia.generated.Cd51ee9d3_0.removeServiceAssembly(INTERFACE[RepositoryService]) at org.ow2.petals.jbi.management.task.deployment.undeploy.RemoveSADirectoryTask.execute(RemoveSADirectoryTask.java:62) at org.ow2.petals.jbi.management.TaskProcessor.process(TaskProcessor.java:78) at org.ow2.petals.jbi.management.deployment.DeploymentServiceImpl.undeploy(DeploymentServiceImpl.java:640) at org.ow2.petals.jbi.management.deployment.DeploymentServiceImpl.forceUndeploy(DeploymentServiceImpl.java:234) at org.objectweb.fractal.julia.generated.C9ae71627_0.forceUndeploy(INTERCEPTOR[DeploymentService]) at org.objectweb.fractal.julia.generated.C59d5ff32_0.forceUndeploy(INTERFACE[DeploymentService]) at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.performUndeploySA(AutoLoaderServiceImpl.java:508) at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.uninstall(AutoLoaderServiceImpl.java:211) at org.ow2.petals.jbi.management.autoload.InstalledDirectoryScanner.run(InstalledDirectoryScanner.java:71) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source)
    There must be an input stream which is not closed correctly and prevents the file from being deleted.
  • Environment:
    Windows 7

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vincent Zurczak added a comment - Tue, 14 Feb 2012 - 17:59:08 +0100

This bug does not occur everytime.
Sometimes it works correctly. And sometimes, it reults in this exception. Is there some kind of polling? Or something that reads the WSDL later on?

Show
Vincent Zurczak added a comment - Tue, 14 Feb 2012 - 17:59:08 +0100 This bug does not occur everytime. Sometimes it works correctly. And sometimes, it reults in this exception. Is there some kind of polling? Or something that reads the WSDL later on?
Hide
Permalink
Christophe DENEUX added a comment - Wed, 15 Feb 2012 - 09:46:17 +0100

It seems to me that this problem is the same as PETALSSEPOJO-1 and PETALSSESCA-8, and I suspect a problem of classloader freeing (PETALSSEPOJO-3, PETALSSEPOJO-7, PETALSESBCONT-17).

Show
Christophe DENEUX added a comment - Wed, 15 Feb 2012 - 09:46:17 +0100 It seems to me that this problem is the same as PETALSSEPOJO-1 and PETALSSESCA-8, and I suspect a problem of classloader freeing (PETALSSEPOJO-3, PETALSSEPOJO-7, PETALSESBCONT-17).
Hide
Permalink
Victor NOËL added a comment - Mon, 5 Oct 2015 - 12:00:50 +0200

duplicate of PETALSESBCONT-17

Show
Victor NOËL added a comment - Mon, 5 Oct 2015 - 12:00:50 +0200 duplicate of PETALSESBCONT-17

People

Dates

  • Created:
    Mon, 13 Feb 2012 - 14:53:19 +0100
    Updated:
    Mon, 5 Oct 2015 - 12:00:50 +0200
    Resolved:
    Mon, 5 Oct 2015 - 12:00:39 +0200
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.