[jboss-user] [Installation, Configuration & Deployment] - Re: Undeploying multiple wars inside an ear causes NameAlrea

[daniele.ulrich]

Hi jaikiran

The ear with the content listed below was running for a year without problems in all our environments. Now it does not run in PROD anymore; that's why I doubt that it helps to analyze the content. But I appreciate your help!

mpu.ear:

META-INF/
META-INF/MANIFEST.MF
META-INF/application.xml
META-INF/jboss-app.xml
mpu-util-18.1.jar
adInfuse-18.1.jar
externalProvisioningNotification-18.1.jar
messagemanagermodel-18.1.jar
alertmodel-18.1.jar
emsmodel-18.1.jar
vasrestriction-cronjob-18.1.jar
content-push-processor-18.1.jar
content-delivery-processor-18.1.jar
xtrazone-delivery-processor-18.1.jar
content-billing-processor-18.1.jar
ems-ejb-18.1.jar
mpu-war-18.1.war
ssimpu-war-18.1.war
messagebroker-delivery-interface-18.1.war
mmlsupportejb-18.1.jar
apscomponent-18.1.jar
messagemanager-18.1.jar
smtpservercomp-18.1.jar
jsch-0.1.39.jar
pbiclient-18.1.jar
pbiclientInterface-18.1.jar
access-18.1.jar
accessChannelInterface-18.1.jar
accessInterface-18.1.jar
apsproducer-18.1.jar
jmsproducerframework-18.1.jar
mailclient-18.1.jar
mailclientInterface-18.1.jar
onNetInterface-18.1.jar
smstestdevice-18.1.jar
soap-2.3.jar
subscriptioninfoInterface-18.1.jar
subscriptioninfo-18.1.jar
deregistration-18.1.jar
aplclient-18.1.jar
mmlsupport-18.1.jar
mmcpmmsfetcher-18.1.jar
mmcpmmsfetcherInterface-18.1.jar
rbtclient-18.1.jar
registrationUtil-18.1.jar
management-18.1.jar
exception-18.1.jar
propertyPool-18.1.jar
propertyPoolInterface-18.1.jar
util-18.1.jar
ssiframework-18.1.jar
msgsender-18.1.jar
dbConn-18.1.jar
dbConnInterface-18.1.jar
dbLayer-18.1.jar
utildb-18.1.jar
jmx-18.1.jar
httpframework-18.1.jar
mpslog-18.1.jar
wapPushSender-18.1.jar
lifecycle-18.1.jar
jmxtools-1.2.1.jar
commons-io-1.2.jar
commons-httpclient-3.0.jar
jdom-1.0.jar
asm-1.5.3.jar
aqapi-1.0.jar
axis-1.4.jar
otaclient-18.1.jar
oab-18.1.jar
emsInterface-18.1.jar
rilInterface-18.1.jar
xml-resolver-1.1.jar
oabschema-1.0.jar
sis2_corbaclient-1.0.0.jar
smsservices-18.1.jar
commons-discovery-0.4.jar
axis-wsdl4j-1.5.1.jar
alertClient-18.1.jar
purchase-18.1.jar
ccch-2.1.0.jar
axis-jaxrpc-1.4.jar
lbiclient-18.1.jar
lbsclient-3.2.0.jar
mclib_base-0.1.jar
mclib_conf-0.1.jar
mclib_log-0.1.jar
XMLA_net-1.0.18.jar
xmlaproxy-2.1.1.21.jar
axis-saaj-1.4.jar
promoClient-18.1.jar
cpeClient-18.1.jar
xml_apis-2.0.2.jar
wss4j-1.5.3.jar
addressing-2.0.jar
mbclient-18.1.jar
castor-1.0.3.jar
jargs-1.0.jar
oro-2.0.8.jar
avalon-framework-4.1.5.jar
contentdelivery-core-1.10.jar
contentdelivery-api-1.10.jar
trove-2.1.1.jar
commons-dbcp-1.2.1.jar
commons-pool-1.2.jar
xml-apis-1.0.b2.jar
jsr173-1.0.jar
mindterm-1.0.jar
saaj-1.2.jar
opensaml-1.0.1.jar
moss-gateway-security-2.1.0.2.jar
ehcache-1.1.jar
META-INF/maven/
META-INF/maven/com.swisscom.live/
META-INF/maven/com.swisscom.live/mpu/
META-INF/maven/com.swisscom.live/mpu/pom.xml
META-INF/maven/com.swisscom.live/mpu/pom.properties

I think others also faced this problem: https://jira.jboss.org/jira/browse/JBAS-7092

To be very precise: we had 3 wars in that ear: 

mpu-war-18.1.war
ssimpu-war-18.1.war
messagebroker-delivery-interface-18.1.war

now we had to put 2 wars outside the ear:

ssimpu-war-18.1.war
messagebroker-delivery-interface-18.1.war


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261823#4261823

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261823