[
https://jira.jboss.org/browse/JBAS-8528?page=com.atlassian.jira.plugin.sy...
]
jaikiran pai commented on JBAS-8528:
------------------------------------
A workaround would be to rename the deployment, till a fix to take application-name into
account is provided.
IllegalStateException: jboss.naming:application=MyApp is already
installed
--------------------------------------------------------------------------
Key: JBAS-8528
URL:
https://jira.jboss.org/browse/JBAS-8528
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: 6.0.0.M5
Environment: Linux 2.6.18-8.el5 #1 SMP x86_64 GNU/Linux
Java 64-Bit Server VM "1.6.0_21"
Reporter: Rico Neubauer
Assignee: Ales Justin
Attachments: alreadyInstalled.txt
Can be seen with M5, also with Snapshot as of 2010-10-10.
This might have the same root cause as JBAS-6335, but JBAS-6335 is reported to be fixed,
whereas this issue definitely exists.
If you have 2 or more files in the deploy folder, which have the same name with different
suffixes, the deployer will run into the following error (full log will get attached):
[AbstractKernelController] Error installing to Real:
name=vfs:///mnt/san/develop/nbr/XXX/jboss/xxx/deploy/MyApp.war state=PreReal mode=Manual
requiredState=Real: org.jboss.deployers.spi.DeploymentException: Error deploying:
jboss.naming:application=MyApp
Caused by: java.lang.IllegalStateException: jboss.naming:application=MyApp is already
installed.
e.g. if you have an WAR and a SAR which have the same name:
- MyApp.sar
- MyApp.war
or the same with war and probably any other combination of it:
- MyApp.ear
- MyApp.sar
Workaround is to rename one of the files, which leads to successful deployment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira