[JBoss JIRA] Created: (AS7-1236) copied lib directory in the deployments directory results in deployment
10:05 p.m.
copied lib directory in the deployments directory results in deployment
------------------------------------------------------------------------
Key: AS7-1236
URL: https://issues.jboss.org/browse/AS7-1236
Project: Application Server 7
Issue Type: Feature Request
Environment: JBoss AS 7 CR 1
Reporter: Jim Tyrrell
Having an existing zipped up war file, and then unzipping it in the deployment directory,
creates a lib directory that has a bunch of jar files in it. It appears that these jar
files in this lib directory are marked as .failed as they are tried to be deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:07 p.m.
New subject: [JBoss JIRA] Commented: (AS7-1236) copied lib directory in the deployments directory results in deployment
[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
Jim Tyrrell commented on AS7-1236:
----------------------------------
Uploading a jar and error messages in a second...
copied lib directory in the deployments directory results in
deployment
------------------------------------------------------------------------
Key: AS7-1236
URL: https://issues.jboss.org/browse/AS7-1236
Project: Application Server 7
Issue Type: Feature Request
Environment: JBoss AS 7 CR 1
Reporter: Jim Tyrrell
Having an existing zipped up war file, and then unzipping it in the deployment directory,
creates a lib directory that has a bunch of jar files in it. It appears that these jar
files in this lib directory are marked as .failed as they are tried to be deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:21 p.m.
New subject: [JBoss JIRA] Updated: (AS7-1236) copied lib directory in the deployments directory results in deployment
[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
Jim Tyrrell updated AS7-1236:
-----------------------------
Attachment: Sample.war
Sample War file
copied lib directory in the deployments directory results in
deployment
------------------------------------------------------------------------
Key: AS7-1236
URL: https://issues.jboss.org/browse/AS7-1236
Project: Application Server 7
Issue Type: Feature Request
Environment: JBoss AS 7 CR 1
Reporter: Jim Tyrrell
Attachments: Sample.war
Having an existing zipped up war file, and then unzipping it in the deployment directory,
creates a lib directory that has a bunch of jar files in it. It appears that these jar
files in this lib directory are marked as .failed as they are tried to be deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:23 p.m.
New subject: [JBoss JIRA] Commented: (AS7-1236) copied lib directory in the deployments directory results in deployment
[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
Jim Tyrrell commented on AS7-1236:
----------------------------------
Put the Sample.war file in the deployments directory of the standalone instance.
Notice the file deploys.
14:18:54,637 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) Starting
deployment of "Sample.war"
14:18:55,302 INFO [org.jboss.web] (MSC service thread 1-7) registering web context:
/Sample
14:18:55,323 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2)
Deployed "Sample.war"
Now unzip the Sample.war file in the directory, creating a WEB-INF folder in the
deployments directory. You should see the following errors, below.
You will also notice that the jar files are marked as failed.
Jim-Tyrrells-MacBook-Pro-2:deployments jimtyrrell$ ls WEB-INF/lib/
drools-api-5.1.1.jar drools-core-5.1.1.jar.failed
drools-api-5.1.1.jar.failed log4j-1.2.16.jar
drools-compiler-5.1.1.jar log4j-1.2.16.jar.failed
drools-compiler-5.1.1.jar.failed mvel2-2.0.16.jar
drools-core-5.1.1.jar mvel2-2.0.16.jar.failed
14:19:05,388 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) Starting
deployment of "drools-api-5.1.1.jar"
14:19:05,388 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) Starting
deployment of "drools-compiler-5.1.1.jar"
14:19:05,390 INFO [org.jboss.as.server.deployment] (MSC service thread 1-16) Starting
deployment of "drools-core-5.1.1.jar"
14:19:05,396 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting
deployment of "log4j-1.2.16.jar"
14:19:05,397 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) Starting
deployment of "mvel2-2.0.16.jar"
14:19:05,396 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed
to start service jboss.deployment.unit."drools-api-5.1.1.jar".STRUCTURE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."drools-api-5.1.1.jar".STRUCTURE: Failed to process phase
STRUCTURE of deployment "drools-api-5.1.1.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_24]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to
mount deployment content
at
org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:82)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
Caused by: java.io.FileNotFoundException: /Users/jimtyrrell
1/Servers/jboss-7.0.0.CR1/standalone/deployments/drools-api-5.1.1.jar (No such file or
directory)
at java.io.FileInputStream.open(Native Method) [:1.6.0_24]
at java.io.FileInputStream.<init>(FileInputStream.java:106) [:1.6.0_24]
at org.jboss.vfs.spi.RootFileSystem.openInputStream(RootFileSystem.java:55)
at org.jboss.vfs.VirtualFile.openStream(VirtualFile.java:238)
at org.jboss.vfs.VFS.mountZip(VFS.java:434)
at
org.jboss.as.server.deployment.repository.impl.ServerDeploymentRepositoryImpl.mountDeploymentContent(ServerDeploymentRepositoryImpl.java:75)
at
org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:78)
... 6 more
14:19:05,402 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed
to start service jboss.deployment.unit."mvel2-2.0.16.jar".STRUCTURE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."mvel2-2.0.16.jar".STRUCTURE: Failed to process phase
STRUCTURE of deployment "mvel2-2.0.16.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_24]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to
mount deployment content
at
org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:82)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
Caused by: java.io.FileNotFoundException: /Users/jimtyrrell
1/Servers/jboss-7.0.0.CR1/standalone/deployments/mvel2-2.0.16.jar (No such file or
directory)
at java.io.FileInputStream.open(Native Method) [:1.6.0_24]
at java.io.FileInputStream.<init>(FileInputStream.java:106) [:1.6.0_24]
at org.jboss.vfs.spi.RootFileSystem.openInputStream(RootFileSystem.java:55)
at org.jboss.vfs.VirtualFile.openStream(VirtualFile.java:238)
at org.jboss.vfs.VFS.mountZip(VFS.java:434)
at
org.jboss.as.server.deployment.repository.impl.ServerDeploymentRepositoryImpl.mountDeploymentContent(ServerDeploymentRepositoryImpl.java:75)
at
org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:78)
... 6 more
14:19:05,397 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-13) MSC00001: Failed
to start service jboss.deployment.unit."drools-core-5.1.1.jar".STRUCTURE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."drools-core-5.1.1.jar".STRUCTURE: Failed to process phase
STRUCTURE of deployment "drools-core-5.1.1.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_24]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to
mount deployment content
at
org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:82)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
Caused by: java.io.FileNotFoundException: /Users/jimtyrrell
1/Servers/jboss-7.0.0.CR1/standalone/deployments/drools-core-5.1.1.jar (No such file or
directory)
at java.io.FileInputStream.open(Native Method) [:1.6.0_24]
at java.io.FileInputStream.<init>(FileInputStream.java:106) [:1.6.0_24]
at org.jboss.vfs.spi.RootFileSystem.openInputStream(RootFileSystem.java:55)
at org.jboss.vfs.VirtualFile.openStream(VirtualFile.java:238)
at org.jboss.vfs.VFS.mountZip(VFS.java:434)
at
org.jboss.as.server.deployment.repository.impl.ServerDeploymentRepositoryImpl.mountDeploymentContent(ServerDeploymentRepositoryImpl.java:75)
at
org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:78)
... 6 more
14:19:05,400 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed
to start service jboss.deployment.unit."log4j-1.2.16.jar".STRUCTURE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."log4j-1.2.16.jar".STRUCTURE: Failed to process phase
STRUCTURE of deployment "log4j-1.2.16.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_24]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to
mount deployment content
at
org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:82)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
Caused by: java.io.FileNotFoundException: /Users/jimtyrrell
1/Servers/jboss-7.0.0.CR1/standalone/deployments/log4j-1.2.16.jar (No such file or
directory)
at java.io.FileInputStream.open(Native Method) [:1.6.0_24]
at java.io.FileInputStream.<init>(FileInputStream.java:106) [:1.6.0_24]
at org.jboss.vfs.spi.RootFileSystem.openInputStream(RootFileSystem.java:55)
at org.jboss.vfs.VirtualFile.openStream(VirtualFile.java:238)
at org.jboss.vfs.VFS.mountZip(VFS.java:434)
at
org.jboss.as.server.deployment.repository.impl.ServerDeploymentRepositoryImpl.mountDeploymentContent(ServerDeploymentRepositoryImpl.java:75)
at
org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:78)
... 6 more
14:19:05,396 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-12) MSC00001: Failed
to start service jboss.deployment.unit."drools-compiler-5.1.1.jar".STRUCTURE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."drools-compiler-5.1.1.jar".STRUCTURE: Failed to process
phase STRUCTURE of deployment "drools-compiler-5.1.1.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_24]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to
mount deployment content
at
org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:82)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
Caused by: java.io.FileNotFoundException: /Users/jimtyrrell
1/Servers/jboss-7.0.0.CR1/standalone/deployments/drools-compiler-5.1.1.jar (No such file
or directory)
at java.io.FileInputStream.open(Native Method) [:1.6.0_24]
at java.io.FileInputStream.<init>(FileInputStream.java:106) [:1.6.0_24]
at org.jboss.vfs.spi.RootFileSystem.openInputStream(RootFileSystem.java:55)
at org.jboss.vfs.VirtualFile.openStream(VirtualFile.java:238)
at org.jboss.vfs.VFS.mountZip(VFS.java:434)
at
org.jboss.as.server.deployment.repository.impl.ServerDeploymentRepositoryImpl.mountDeploymentContent(ServerDeploymentRepositoryImpl.java:75)
at
org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:78)
... 6 more
14:19:05,407 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 1)
Deployment of "mvel2-2.0.16.jar" was rolled back with no failure message
14:19:05,407 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 1)
Deployment of "log4j-1.2.16.jar" was rolled back with no failure message
14:19:05,408 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 1)
Deployment of "drools-core-5.1.1.jar" was rolled back with no failure message
14:19:05,408 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 1)
Deployment of "drools-compiler-5.1.1.jar" was rolled back with no failure
message
14:19:05,409 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 1)
Deployment of "drools-api-5.1.1.jar" was rolled back with failure message
{"Failed services" =>
{"jboss.deployment.unit.\"drools-api-5.1.1.jar\".STRUCTURE" =>
"org.jboss.msc.service.StartException in service
jboss.deployment.unit.\"drools-api-5.1.1.jar\".STRUCTURE: Failed to process
phase STRUCTURE of deployment \"drools-api-5.1.1.jar\""}}
14:19:05,411 INFO [org.jboss.as.server.deployment] (MSC service thread 1-9) Stopped
deployment drools-compiler-5.1.1.jar in 2ms
14:19:05,411 INFO [org.jboss.as.server.deployment] (MSC service thread 1-14) Stopped
deployment log4j-1.2.16.jar in 3ms
14:19:05,411 INFO [org.jboss.as.server.deployment] (MSC service thread 1-11) Stopped
deployment drools-core-5.1.1.jar in 2ms
14:19:05,411 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped
deployment mvel2-2.0.16.jar in 2ms
14:19:05,411 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) Stopped
deployment drools-api-5.1.1.jar in 1ms
14:19:05,417 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 2)
{"Composite operation failed and was rolled back. Steps that failed:" =>
{"Operation step-2" => {"Failed services" =>
{"jboss.deployment.unit.\"drools-api-5.1.1.jar\".STRUCTURE" =>
"org.jboss.msc.service.StartException in service
jboss.deployment.unit.\"drools-api-5.1.1.jar\".STRUCTURE: Failed to process
phase STRUCTURE of deployment \"drools-api-5.1.1.jar\""}}}}
14:19:05,418 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 2) Composite
operation was rolled back
14:19:05,418 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 2) Composite
operation was rolled back
14:19:05,419 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 2) Composite
operation was rolled back
14:19:05,419 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 2) Composite
operation was rolled back
ld
copied lib directory in the deployments directory results in
deployment
------------------------------------------------------------------------
Key: AS7-1236
URL: https://issues.jboss.org/browse/AS7-1236
Project: Application Server 7
Issue Type: Feature Request
Environment: JBoss AS 7 CR 1
Reporter: Jim Tyrrell
Attachments: Sample.war
Having an existing zipped up war file, and then unzipping it in the deployment directory,
creates a lib directory that has a bunch of jar files in it. It appears that these jar
files in this lib directory are marked as .failed as they are tried to be deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:57 p.m.
New subject: [JBoss JIRA] Commented: (AS7-1236) copied lib directory in the deployments directory results in deployment
[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-1236:
---------------------------------------
It is legal to include non-deployment subdirectories under deployments/ as a means of
organizing content for whatever purpose the user may have. If the scanner finds a
directory whose name does not end in .ear, .jar, .rar, .sar or .war it assumes that
directory is just for organizational purposes and will recurse into it looking for
deployments. That is what is happening here. Unzipping an archive such that WEB-INF is a
directory not under another directory named X.war is a user error.
The scanner can handle this a bit more gracefully by checking for a directory named
WEB-INF or META-INF and if found logging a ERROR message and not recursing into it looking
for deployments. I'll add that in response to this JIRA. If you unzip an ear this way
though, you'll get an ERROR message about the META-INF dir, but it's going to go
ahead and try and deploy the modules in the ear since they are not located under
META-INF.
copied lib directory in the deployments directory results in
deployment
------------------------------------------------------------------------
Key: AS7-1236
URL: https://issues.jboss.org/browse/AS7-1236
Project: Application Server 7
Issue Type: Feature Request
Environment: JBoss AS 7 CR 1
Reporter: Jim Tyrrell
Attachments: Sample.war
Having an existing zipped up war file, and then unzipping it in the deployment directory,
creates a lib directory that has a bunch of jar files in it. It appears that these jar
files in this lib directory are marked as .failed as they are tried to be deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:04 p.m.
New subject: [JBoss JIRA] Commented: (AS7-1236) copied lib directory in the deployments directory results in deployment
[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
Jim Tyrrell commented on AS7-1236:
----------------------------------
What about the marking of the jar files as *.failed? Is that correct behavior?
copied lib directory in the deployments directory results in
deployment
------------------------------------------------------------------------
Key: AS7-1236
URL: https://issues.jboss.org/browse/AS7-1236
Project: Application Server 7
Issue Type: Feature Request
Environment: JBoss AS 7 CR 1
Reporter: Jim Tyrrell
Attachments: Sample.war
Having an existing zipped up war file, and then unzipping it in the deployment directory,
creates a lib directory that has a bunch of jar files in it. It appears that these jar
files in this lib directory are marked as .failed as they are tried to be deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:08 p.m.
New subject: [JBoss JIRA] Commented: (AS7-1236) copied lib directory in the deployments directory results in deployment
[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
Jim Tyrrell commented on AS7-1236:
----------------------------------
Remember also that the reason I found this was that I had a zipped up war file, and needed
to make some changes to it, so I unzipped it locally to create an exploded archive to play
with. While this may be user error, this is not the first time in my development life I
have done something like this to work on something...and I am guessing with millions of
downloads I am no the only unique one to do this.
copied lib directory in the deployments directory results in
deployment
------------------------------------------------------------------------
Key: AS7-1236
URL: https://issues.jboss.org/browse/AS7-1236
Project: Application Server 7
Issue Type: Feature Request
Environment: JBoss AS 7 CR 1
Reporter: Jim Tyrrell
Attachments: Sample.war
Having an existing zipped up war file, and then unzipping it in the deployment directory,
creates a lib directory that has a bunch of jar files in it. It appears that these jar
files in this lib directory are marked as .failed as they are tried to be deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:28 p.m.
New subject: [JBoss JIRA] Updated: (AS7-1236) Hitting self in head with hammer results in headache (was: copied lib directory in the deployments directory results in deployment)
[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
David Lloyd updated AS7-1236:
-----------------------------
Summary: Hitting self in head with hammer results in headache (was: copied lib
directory in the deployments directory results in deployment) (was: copied lib directory
in the deployments directory results in deployment )
Hitting self in head with hammer results in headache (was: copied lib
directory in the deployments directory results in deployment)
-----------------------------------------------------------------------------------------------------------------------------------
Key: AS7-1236
URL: https://issues.jboss.org/browse/AS7-1236
Project: Application Server 7
Issue Type: Feature Request
Environment: JBoss AS 7 CR 1
Reporter: Jim Tyrrell
Attachments: Sample.war
Having an existing zipped up war file, and then unzipping it in the deployment directory,
creates a lib directory that has a bunch of jar files in it. It appears that these jar
files in this lib directory are marked as .failed as they are tried to be deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:30 p.m.
New subject: [JBoss JIRA] Updated: (AS7-1236) copied lib directory in the deployments directory results in deployment
[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
David Lloyd updated AS7-1236:
-----------------------------
Summary: copied lib directory in the deployments directory results in deployment
(was: Hitting self in head with hammer results in headache (was: copied lib directory in
the deployments directory results in deployment))
Ha, ha.
copied lib directory in the deployments directory results in
deployment
-----------------------------------------------------------------------
Key: AS7-1236
URL: https://issues.jboss.org/browse/AS7-1236
Project: Application Server 7
Issue Type: Feature Request
Environment: JBoss AS 7 CR 1
Reporter: Jim Tyrrell
Attachments: Sample.war
Having an existing zipped up war file, and then unzipping it in the deployment directory,
creates a lib directory that has a bunch of jar files in it. It appears that these jar
files in this lib directory are marked as .failed as they are tried to be deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
midnight
New subject: [JBoss JIRA] Resolved: (AS7-1236) copied lib directory in the deployments directory results in deployment
[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry resolved AS7-1236.
-----------------------------------
Assignee: Brian Stansberry
Fix Version/s: 7.0.1.Final
Resolution: Done
Resolved via commit http://github.com/jbossas/jboss-as/compare/664ec1d...4514477
Agreed that this is a mistake that people will make. So, the scanner now detects META-INF
and WEB-INF directories and will not recurse into them looking for deployments; instead an
ERROR is logged. This will prevent incorrect deployments being attempted in many, but not
all, cases and for cases where an incorrect deployment is attempted, the log message
hopefully will help the user to understand what went wrong.
Re: the .failed markers, yes, if the scanner finds something and tries to deploy it and
that fails, the .failed marker is the correct behavior.
copied lib directory in the deployments directory results in
deployment
-----------------------------------------------------------------------
Key: AS7-1236
URL: https://issues.jboss.org/browse/AS7-1236
Project: Application Server 7
Issue Type: Feature Request
Environment: JBoss AS 7 CR 1
Reporter: Jim Tyrrell
Assignee: Brian Stansberry
Fix For: 7.0.1.Final
Attachments: Sample.war
Having an existing zipped up war file, and then unzipping it in the deployment directory,
creates a lib directory that has a bunch of jar files in it. It appears that these jar
files in this lib directory are marked as .failed as they are tried to be deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:21 p.m.
New subject: [JBoss JIRA] Updated: (AS7-1236) copied lib directory in the deployments directory results in deployment
[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-1236:
----------------------------------
Fix Version/s: 7.0.0.Final
(was: 7.0.1.Final)
copied lib directory in the deployments directory results in
deployment
-----------------------------------------------------------------------
Key: AS7-1236
URL: https://issues.jboss.org/browse/AS7-1236
Project: Application Server 7
Issue Type: Feature Request
Environment: JBoss AS 7 CR 1
Reporter: Jim Tyrrell
Assignee: Brian Stansberry
Fix For: 7.0.0.Final
Attachments: Sample.war
Having an existing zipped up war file, and then unzipping it in the deployment directory,
creates a lib directory that has a bunch of jar files in it. It appears that these jar
files in this lib directory are marked as .failed as they are tried to be deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:39 a.m.
New subject: [JBoss JIRA] Commented: (AS7-1236) copied lib directory in the deployments directory results in deployment
[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
Jim Tyrrell commented on AS7-1236:
----------------------------------
Okay I guess on the .failed markers, but I have to ask a question, so if we are deploying
just things likes .war, .ear, .sar, and a host of other well known extensions, why would
this even happen. In the past I thought there was a "deployable" list of
extensions JBoss AS/EAP would look at what changed requirement/need wise, or was this just
some oversight? Also curious does stuff like this end up in unit tests? How would I look
at those if they exist?
copied lib directory in the deployments directory results in
deployment
-----------------------------------------------------------------------
Key: AS7-1236
URL: https://issues.jboss.org/browse/AS7-1236
Project: Application Server 7
Issue Type: Feature Request
Environment: JBoss AS 7 CR 1
Reporter: Jim Tyrrell
Assignee: Brian Stansberry
Fix For: 7.0.0.Final
Attachments: Sample.war
Having an existing zipped up war file, and then unzipping it in the deployment directory,
creates a lib directory that has a bunch of jar files in it. It appears that these jar
files in this lib directory are marked as .failed as they are tried to be deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1 a.m.
New subject: [JBoss JIRA] Commented: (AS7-1236) copied lib directory in the deployments directory results in deployment
[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-1236:
---------------------------------------
One of the well known extensions is .jar, the standard deployment type for an ejb
deployment.
Most of the unit tests around scanner behavior can be found in
https://github.com/jbossas/jboss-as/blob/master/deployment-scanner/src/te...
copied lib directory in the deployments directory results in
deployment
-----------------------------------------------------------------------
Key: AS7-1236
URL: https://issues.jboss.org/browse/AS7-1236
Project: Application Server 7
Issue Type: Feature Request
Environment: JBoss AS 7 CR 1
Reporter: Jim Tyrrell
Assignee: Brian Stansberry
Fix For: 7.0.0.Final
Attachments: Sample.war
Having an existing zipped up war file, and then unzipping it in the deployment directory,
creates a lib directory that has a bunch of jar files in it. It appears that these jar
files in this lib directory are marked as .failed as they are tried to be deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:06 a.m.
New subject: [JBoss JIRA] Commented: (AS7-1236) copied lib directory in the deployments directory results in deployment
[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
Jim Tyrrell commented on AS7-1236:
----------------------------------
Yeah I get that a jar file is a standard deployment, but it is usually in the context of a
war/ear/etc....just found it odd that something in a directory that did not end in the
well known types (war, ear, sar, etc) would be scanned, and then that it would be crawled
it, and .failed file would be created in the exploded directory..just odd to me.
Are there cases where other "things" could be done to an exploded directory?
copied lib directory in the deployments directory results in
deployment
-----------------------------------------------------------------------
Key: AS7-1236
URL: https://issues.jboss.org/browse/AS7-1236
Project: Application Server 7
Issue Type: Feature Request
Environment: JBoss AS 7 CR 1
Reporter: Jim Tyrrell
Assignee: Brian Stansberry
Fix For: 7.0.0.Final
Attachments: Sample.war
Having an existing zipped up war file, and then unzipping it in the deployment directory,
creates a lib directory that has a bunch of jar files in it. It appears that these jar
files in this lib directory are marked as .failed as they are tried to be deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:17 a.m.
New subject: [JBoss JIRA] Commented: (AS7-1236) copied lib directory in the deployments directory results in deployment
[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-1236:
---------------------------------------
There is no requirement that an ejb deployment has to be packaged in an ear or a war. So
if the scanner sees a .jar, it assumes it's an ejb deployment and tries to deploy it.
This isn't new behavior; the scanner in AS 5 and 6 if it sees a directory it checks if
its filename matches one of the expected extensions; if yes it tries to deploy it as an
exploded deployment; if no it recurses into it looking for deployments. I believe the same
is true in AS 3 and 4 as well.
The only difference in AS 7 is we write out the .failed files.
copied lib directory in the deployments directory results in
deployment
-----------------------------------------------------------------------
Key: AS7-1236
URL: https://issues.jboss.org/browse/AS7-1236
Project: Application Server 7
Issue Type: Feature Request
Environment: JBoss AS 7 CR 1
Reporter: Jim Tyrrell
Assignee: Brian Stansberry
Fix For: 7.0.0.Final
Attachments: Sample.war
Having an existing zipped up war file, and then unzipping it in the deployment directory,
creates a lib directory that has a bunch of jar files in it. It appears that these jar
files in this lib directory are marked as .failed as they are tried to be deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:19 a.m.
New subject: [JBoss JIRA] Commented: (AS7-1236) copied lib directory in the deployments directory results in deployment
[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
Jim Tyrrell commented on AS7-1236:
----------------------------------
Okay I get the above, but this is a directory in this case lib, with a bunch of jar files
in it, how come AS7 reaches into that directory, I guess is the question?
copied lib directory in the deployments directory results in
deployment
-----------------------------------------------------------------------
Key: AS7-1236
URL: https://issues.jboss.org/browse/AS7-1236
Project: Application Server 7
Issue Type: Feature Request
Environment: JBoss AS 7 CR 1
Reporter: Jim Tyrrell
Assignee: Brian Stansberry
Fix For: 7.0.0.Final
Attachments: Sample.war
Having an existing zipped up war file, and then unzipping it in the deployment directory,
creates a lib directory that has a bunch of jar files in it. It appears that these jar
files in this lib directory are marked as .failed as they are tried to be deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:21 a.m.
New subject: [JBoss JIRA] Commented: (AS7-1236) copied lib directory in the deployments directory results in deployment
[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
Jim Tyrrell commented on AS7-1236:
----------------------------------
I can confirm that EAP 5.1 does "deploy" the lib folder with a collection of jar
files...interesting for sure....
copied lib directory in the deployments directory results in
deployment
-----------------------------------------------------------------------
Key: AS7-1236
URL: https://issues.jboss.org/browse/AS7-1236
Project: Application Server 7
Issue Type: Feature Request
Environment: JBoss AS 7 CR 1
Reporter: Jim Tyrrell
Assignee: Brian Stansberry
Fix For: 7.0.0.Final
Attachments: Sample.war
Having an existing zipped up war file, and then unzipping it in the deployment directory,
creates a lib directory that has a bunch of jar files in it. It appears that these jar
files in this lib directory are marked as .failed as they are tried to be deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:09 a.m.
New subject: [JBoss JIRA] Commented: (AS7-1236) copied lib directory in the deployments directory results in deployment
[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-1236:
---------------------------------------
The scanner allows subdirectories under deploy/ (AS < 7) or deployments/ that
aren't exploded deployments as a means to allow organization of content. For example,
in AS 5 I organized all the clustering related deployments under deploy/cluster/. If a
directory doesn't have a name that causes the scanner to treat it as an exploded
deployment, the scanner assumes it's there for organization of content and steps into
it.
copied lib directory in the deployments directory results in
deployment
-----------------------------------------------------------------------
Key: AS7-1236
URL: https://issues.jboss.org/browse/AS7-1236
Project: Application Server 7
Issue Type: Feature Request
Environment: JBoss AS 7 CR 1
Reporter: Jim Tyrrell
Assignee: Brian Stansberry
Fix For: 7.0.0.Final
Attachments: Sample.war
Having an existing zipped up war file, and then unzipping it in the deployment directory,
creates a lib directory that has a bunch of jar files in it. It appears that these jar
files in this lib directory are marked as .failed as they are tried to be deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4925
days inactive
4929
days old
17 comments
3 participants
participants (3)
-
Brian Stansberry (JIRA) -
David Lloyd (JIRA)
-
Jim Tyrrell (JIRA)