[jboss-as7-dev] Seeing one failed deployment stop other successful deployments

[Brian Stansberry]

Good point. The current behavior makes a bit of sense for changes copied 
into deployments/ after boot, but it's not appropriate at boot. So 
better to stop the batching:

https://issues.jboss.org/browse/AS7-783

On 5/14/11 3:29 PM, John Bailey wrote:
> Yeah. The deployment scanner is sending a single batch  for the deployments discovered in a scan.  This most likely isn't the desired behavior.
>
> On May 13, 2011, at 8:00 PM, Jason Greene<jgreene at redhat.com>  wrote:
>
>> Hmm I would need to look at the code but if it's batching them in the same plan that would explain it. The default is to rollback composites if a single op fails.
>>
>> Sent from my iPhone
>>
>> On May 13, 2011, at 5:30 PM, Scott Stark<sstark at redhat.com>  wrote:
>>
>>> I'm seeing a problem with one bad deployment failing other deployments
>>> when starting a server with more than one deployment in the deployments
>>> directory. If I startup the server with:
>>> [root at ip-10-72-59-227 log]# ls ../deployments/
>>> README.txt  ROOT.war.dodeploy     weld-permalink.war.dodeploy
>>> ROOT.war    weld-permalink.war
>>>
>>> and the weld-permalink.war fails, the successfully deployed ROOT.war is
>>> stopped. Why would that be?
>>>
>>> 18:18:02,233 INFO  [org.jboss.as] (MSC service thread 1-1) JBoss AS
>>> 7.0.0.Beta3-SNAPSHOT "TBD" started in 8363ms - Started 77 of 96 services
>>> (19 services are passive or on-demand)18:18:02,250 INFO
>>> [org.jboss.as.server.deployment] (pool-3-thread-1) Content ad
>>> ded at location
>>> /var/lib/libra/efb401bdb2e641528a1f9278ca091719/jbossas/test3/jbossas-7.0.0/standalone/data/content/fc/b80fdb5b58448bebcdb680ac7790fdcfea5965/content
>>> 18:18:02,282 WARN  [org.jboss.vfs] (MSC service thread 1-2) VFS was
>>> unable to set the URLStreamHandlerFactory.  This will have unpredictable
>>> results
>>> 18:18:02,284 INFO  [org.jboss.as.server.deployment] (MSC service thread
>>> 1-1) Starting deployment of "weld-permalink.war"
>>> 18:18:02,633 WARN  [org.jboss.as.server.deployment.module] (MSC service
>>> thread 1-3) META-INF directory
>>> /content/weld-permalink.war/WEB-INF/classes/META-INF ignored as it is
>>> not a valid location for META-INF18:18:05,609 WARN
>>> [org.jboss.as.server.deployment.service-loader] (MSC service thread 1-1)
>>> Encountered invalid class name
>>> "com.sun.faces.vendor.Tomcat6InjectionProvider:org.apache.catalina.util.DefaultAnnotationProcessor"
>>> for service type "com.sun.faces.spi.injectionprovider"18:18:05,609 WARN
>>> [org.jboss.as.server.deployment.service-loader] (MSC service thread 1-1)
>>> Encountered invalid class name
>>> "com.sun.faces.vendor.Jetty6InjectionProvider:org.mortbay.jetty.plus.annotation.InjectionCollection"
>>> for service type "com.sun.faces.spi.injectionprovider"
>>> 18:18:05,967 INFO  [org.jboss.weld] (MSC service thread 1-1) Processing
>>> CDI deployment: weld-permalink.war18:18:06,068 INFO  [org.jboss.web]
>>> (MSC service thread 1-2) registering web context:
>>> 18:18:06,069 INFO  [org.jboss.as.server.deployment] (MSC service thread
>>> 1-2) Com
>>> pleted deployment of "ROOT.war" in 3800 ms
>>> 18:18:06,872 INFO  [org.jboss.weld] (MSC service thread 1-3) Starting
>>> Services for CDI deployment: weld-permalink.war
>>> 18:18:06,069 INFO  [org.jboss.as.server.deployment] (MSC service thread
>>> 1-2) Completed deployment of "ROOT.war" in 3800 ms
>>> 18:18:06,872 INFO  [org.jboss.weld] (MSC service thread 1-3) Starting
>>> Services for CDI deployment: weld-permalink.war
>>> 18:18:07,172 INFO  [org.jboss.weld.Version] (MSC service thread 1-3)
>>> WELD-000900 1.1.0 (Final)18:18:07,277 INFO  [org.jboss.weld] (MSC
>>> service thread 1-3) Starting weld service
>>> 18:18:08,042 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3)
>>> MSC00001: Failed to start service
>>> jboss.deployment.unit."weld-permalink.war".WeldService:
>>> org.jboss.msc.service.StartException in service
>>> jboss.deployment.unit."weld-permalink.war".WeldService:
>>> java.lang.ClassCastException:
>>> org.jboss.weldx.transaction.org$jboss$weld$bean-org$jboss$as$weld$deployment$WeldDeployment$additionalClasses-Built-in-UserTransaction_$$_WeldProxy
>>> cannot be cast to javassist.util.proxy.ProxyObject
>>> ...
>>> 18:18:08,218 INFO  [org.jboss.as.server.deployment] (MSC service thread
>>> 1-2) Stopped deployment weld-permalink.war in 112ms
>>> 18:18:08,534 INFO  [org.jboss.as.server.deployment] (MSC service thread
>>> 1-2) Stopped deployment ROOT.war in 422ms
>>>
>>> [root at ip-10-72-59-227 log]# ls ../deployments/
>>> README.txt  ROOT.war.failed     weld-permalink.war.failed
>>> ROOT.war    weld-permalink.war
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev


-- 
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat