FS deployment scanner uses different order resulting in failing deployments --------------------------------------------------------------------------- Key: AS7-1834 URL: https://issues.jboss.org/browse/AS7-1834 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.0.1.Final, 7.1.0.Alpha1 Environment: Windows 7 (most probably not specific to this OS) Reporter: Rico Neubauer Assignee: Jason Greene Attachments: server_startup_not_working.txt.zip, server_startup_working_due_to_deployment_of_EJBs_delayed.txt.zip Experiencing a different behavior in deployment depending upon deployment order. I have some OSGi bundles and one EJB-jar, which defines a dependency upon one of the bundles using: Dependencies: deployment.com.companyname.common.CompUtil:0.0.1.SNAPSHOT This works fine and everything works, when the EJB-jar gets deployed after all the OSGi-bundles are already started, see attached log server_startup_working_due_to_deployment_of_EJBs_delayed.txt However, when re-deploying all deployments, or just on a simple restart, all of the deployments fail, since it seems that this dependency leads some undefined state where in consequence also the VFS loses its mount-points, as can be seen here, where the mount point is in the start-up directory, which obviously causes a FNFEx: FileNotFoundException: D:\test\jboss-as-7.1.0.Alpha1-2011-09-12\bin\content\com.seeburger.lib.ext_1.0.0.jar\axiom-dom.jar See full log attached. Everything also works fine, when replacing the EJB-jar with an EJB-jar, which does not have any dependencies on an OSGi-bundle. In domain-mode, this problem does not arise. Bundles are started first, deployment of EJB-jar comes after. Probably in standalone-mode with manually deployed files instead of using the "deployments" folder, the problem might also not arise (untested). Config: standalone-preview jboss-as-7.1.0.Alpha1 as of 2011-09-12

FS deployment scanner uses different order resulting in failing deployments --------------------------------------------------------------------------- Key: AS7-1834 URL: https://issues.jboss.org/browse/AS7-1834 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.0.1.Final, 7.1.0.Alpha1 Environment: Windows 7 (most probably not specific to this OS) Reporter: Rico Neubauer Assignee: Thomas Diesler Attachments: server_startup_not_working.txt.zip, server_startup_working_due_to_deployment_of_EJBs_delayed.txt.zip Experiencing a different behavior in deployment depending upon deployment order. I have some OSGi bundles and one EJB-jar, which defines a dependency upon one of the bundles using: Dependencies: deployment.com.companyname.common.CompUtil:0.0.1.SNAPSHOT This works fine and everything works, when the EJB-jar gets deployed after all the OSGi-bundles are already started, see attached log server_startup_working_due_to_deployment_of_EJBs_delayed.txt However, when re-deploying all deployments, or just on a simple restart, all of the deployments fail, since it seems that this dependency leads some undefined state where in consequence also the VFS loses its mount-points, as can be seen here, where the mount point is in the start-up directory, which obviously causes a FNFEx: FileNotFoundException: D:\test\jboss-as-7.1.0.Alpha1-2011-09-12\bin\content\com.seeburger.lib.ext_1.0.0.jar\axiom-dom.jar See full log attached. Everything also works fine, when replacing the EJB-jar with an EJB-jar, which does not have any dependencies on an OSGi-bundle. In domain-mode, this problem does not arise. Bundles are started first, deployment of EJB-jar comes after. Probably in standalone-mode with manually deployed files instead of using the "deployments" folder, the problem might also not arise (untested). Config: standalone-preview jboss-as-7.1.0.Alpha1 as of 2011-09-12

FS deployment scanner uses different order resulting in failing deployments --------------------------------------------------------------------------- Key: AS7-1834 URL: https://issues.jboss.org/browse/AS7-1834 Project: Application Server 7 Issue Type: Bug Components: OSGi, Server Affects Versions: 7.0.1.Final, 7.1.0.Alpha1 Environment: Windows 7 (most probably not specific to this OS) Reporter: Rico Neubauer Assignee: Thomas Diesler Fix For: 7.2.0.Alpha1 Attachments: server_startup_not_working.txt.zip, server_startup_working_due_to_deployment_of_EJBs_delayed.txt.zip Experiencing a different behavior in deployment depending upon deployment order. I have some OSGi bundles and one EJB-jar, which defines a dependency upon one of the bundles using: Dependencies: deployment.com.companyname.common.CompUtil:0.0.1.SNAPSHOT This works fine and everything works, when the EJB-jar gets deployed after all the OSGi-bundles are already started, see attached log server_startup_working_due_to_deployment_of_EJBs_delayed.txt However, when re-deploying all deployments, or just on a simple restart, all of the deployments fail, since it seems that this dependency leads some undefined state where in consequence also the VFS loses its mount-points, as can be seen here, where the mount point is in the start-up directory, which obviously causes a FNFEx: FileNotFoundException: D:\test\jboss-as-7.1.0.Alpha1-2011-09-12\bin\content\com.seeburger.lib.ext_1.0.0.jar\axiom-dom.jar See full log attached. Everything also works fine, when replacing the EJB-jar with an EJB-jar, which does not have any dependencies on an OSGi-bundle. In domain-mode, this problem does not arise. Bundles are started first, deployment of EJB-jar comes after. Probably in standalone-mode with manually deployed files instead of using the "deployments" folder, the problem might also not arise (untested). Config: standalone-preview jboss-as-7.1.0.Alpha1 as of 2011-09-12