Details

    • Branch Version/s:
      6.2.x
    • Backported to Branch:
      Committed
    • Similar Issues:
      Show 5 results 

      Description

      When ModuleAutoDeployListener checks the jar file in deploy folder to see if it should deploy it, it opens an inputstream and doesn't close it, which means that on windows, the auto deployer is unable to delete the jar file which causes it to be blacklisted and not deployed.

      02:34:50,482 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][Aut
      oDeployDir:204] Processing manifest-first-hook-test.jar
      02:34:50,484 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][Mod
      uleAutoDeployListener:63] Copied module for D:\liferay\bundles\deploy\manifest-f
      irst-hook-test.jar
      02:34:50,487 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][Mod
      uleAutoDeployListener:69] Module for D:\liferay\bundles\deploy\manifest-first-ho
      ok-test.jar copied successfully. Deployment will start in a few seconds.
      02:34:50,488 ERROR [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][Aut
      oDeployDir:217] Auto deploy failed to remove manifest-first-hook-test.jar
      02:34:50,489 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][Aut
      oDeployDir:224] Add manifest-first-hook-test.jar to the blacklist
      

        Issue Links

          Activity

          Hide
          Raymond Auge added a comment -

          Just started reviewing :)

          Sent from GH.

          Show
          Raymond Auge added a comment - Just started reviewing :) Sent from GH .
          Hide
          Brian Wulbern added a comment -

          PASSED Manual Testing using the following steps:

          1. Startup the bundle
          2. Deploy some *.jar files
          3. Check that they get consumed by the deploy folder and console doesn't throw any blacklist errors

          Fixed on:
          Win8 + Tomcat 7.0.42 + MySQL 5.5 Portal ee-6.2.x GIT ID: 2ee35345c8fc1a32db6ad2de6604c45ce366f180.
          Win8 + Tomcat 7.0.42 + MySQL 5.5 Portal master GIT ID: 99659e285c10f46692af5ee1f0d9ea8d5c611cc7.

          Jars get consumed and there are no blacklisting errors in console.

          Show
          Brian Wulbern added a comment - PASSED Manual Testing using the following steps: Startup the bundle Deploy some *.jar files Check that they get consumed by the deploy folder and console doesn't throw any blacklist errors Fixed on: Win8 + Tomcat 7.0.42 + MySQL 5.5 Portal ee-6.2.x GIT ID: 2ee35345c8fc1a32db6ad2de6604c45ce366f180. Win8 + Tomcat 7.0.42 + MySQL 5.5 Portal master GIT ID: 99659e285c10f46692af5ee1f0d9ea8d5c611cc7. Jars get consumed and there are no blacklisting errors in console.

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                28 weeks, 2 days ago

                Development

                  Structure Helper Panel