Multiple errors after applying rollup patch 6 for FSW 6.0.0

Solution In Progress - Updated -

Issue

We are using FSW 6.0.0 with an earlier roll-up patch applied. After installing roll-up patch #6 we see multiple errors during startup, such as:

1:08:49,724 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."overlord-rtgov-acs.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."overlord-rtgov-acs.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "overlord-rtgov-acs.war"
    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.3.Final-redhat-2-bz-1174871.jar:7.2.3.Final-redhat-SNAPSHOT]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_71]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_71]
    at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71]
Caused by: java.lang.IllegalArgumentException: JBAS011046: A component named 'JEEACSLoader' is already defined in this module
    at org.jboss.as.ee.component.EEModuleDescription.addComponent(EEModuleDescription.java:140)
    at org.jboss.as.ejb3.deployment.processors.EJBComponentDescriptionFactory.addComponent(EJBComponentDescriptionFactory.java:60)
    at org.jboss.as.ejb3.deployment.processors.SessionBeanComponentDescriptionFactory.processSessionBeans(SessionBeanComponentDescriptionFactory.java:155)
    at org.jboss.as.ejb3.deployment.processors.SessionBeanComponentDescriptionFactory.processAnnotations(SessionBeanComponentDescriptionFactory.java:96)
    at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processAnnotations(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:58)
    at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:81)
    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.3.Final-redhat-2-bz-1174871.jar:7.2.3.Final-redhat-SNAPSHOT]
    ... 5 more

The main problem we face with the patch installation is that we are not 100% sure which rollup patch level our servers are based on - it is possible that patch 3, 4 or 5 has been applied before. The instructions from roll-up patch #6 on which files to delete contain specific file versions, but it seems we have duplicate jars with different versions around in some places. To ensure all previous files are properly deleted, we'd need instructions which apply to all versions, eg:

rm ${JBOSS_HOME}/standalone/deployments/dtgov-ha.war/WEB-INF/lib/s-ramp-client-0.3.1.*.jar
rm ${JBOSS_HOME}modules/system/layers/soa/org/switchyard/remote/main/switchyard-remote-1.1.1-*.jar

Can you provide something like that?

Environment

  • Red Hat JBoss Fuse Service Works
    • 6.0.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content