[ http://issues.apache.org/jira/browse/GERONIMO-1947?page=all ] Anita Kulshreshtha resolved GERONIMO-1947: ------------------------------------------
Resolution: Fixed This has been fixed by Dain in rev. 405570. I have tested using no-geronimo-plan.war - . hot deploy, . stop the server and . restart the server. > Repeat hot deployment of WARs with no Geronimo plan > --------------------------------------------------- > > Key: GERONIMO-1947 > URL: http://issues.apache.org/jira/browse/GERONIMO-1947 > Project: Geronimo > Type: Bug > Security: public(Regular issues) > Components: deployment > Versions: 1.0 > Environment: Linux, Java HotSpot(TM) Client VM (build 1.4.2_11-b06, mixed > mode) > Reporter: Erin Mulder > Priority: Critical > Fix For: 1.1 > Attachments: no-geronimo-plan.war > > I created a WAR with no deployment plan (see attached no-geronimo-plan.war) > and copied it to the hot deployment directory. Now, every time I start the > server, it tries to deploy it again with a different version number. It does > get an error at that point, but the console is showing N copies and the > startup sequence is showing N-1, where N is the number of server restarts > since I originally deployed it. > Here's a snippet from the console: > Component Name URL State Commands > default/no-geronimo-plan/1146368518972/war /no-geronimo-plan > running Stop Uninstall > default/no-geronimo-plan/1146368650976/war /no-geronimo-plan > running Stop Uninstall > default/no-geronimo-plan/1146368847429/war /no-geronimo-plan > running Stop Uninstall > default/no-geronimo-plan/1146369719473/war /no-geronimo-plan > running Stop Uninstall > default/no-geronimo-plan/1146370013515/war /no-geronimo-plan > running Stop Uninstall > Here's what it looks like at startup: > Booting Geronimo Kernel (in Java 1.4.2_11)... > Starting Geronimo Application Server v.1.1-SNAPSHOT > [**************************] 100% 22s Startup complete > Listening on Ports: > 1099 0.0.0.0 RMI Naming > 1527 0.0.0.0 Derby Connector > 4201 0.0.0.0 ActiveIO Connector EJB > 4242 127.0.0.1 Remote Login Listener > 8019 127.0.0.1 Jetty Connector AJP13 > 8080 0.0.0.0 Jetty Connector HTTP > 8443 0.0.0.0 Jetty Connector HTTPS > 9999 0.0.0.0 JMX Remoting Connector > 61616 0.0.0.0 ActiveMQ Message Broker Connector > Started Application Modules: > EAR: geronimo/webconsole-jetty/1.1-SNAPSHOT/car > RAR: geronimo/activemq/1.1-SNAPSHOT/car > RAR: geronimo/system-database/1.1-SNAPSHOT/car > WAR: default/no-geronimo-plan/1146368518972/war > WAR: default/no-geronimo-plan/1146368650976/war > WAR: default/no-geronimo-plan/1146368847429/war > WAR: default/no-geronimo-plan/1146369719473/war > WAR: geronimo/remote-deploy-jetty/1.1-SNAPSHOT/car > WAR: geronimo/welcome-jetty/1.1-SNAPSHOT/car > Web Applications: > http://wildfire:8080/ > http://wildfire:8080/console > http://wildfire:8080/console-standard > http://wildfire:8080/no-geronimo-plan > http://wildfire:8080/no-geronimo-plan > http://wildfire:8080/no-geronimo-plan > http://wildfire:8080/no-geronimo-plan > http://wildfire:8080/remote-deploy > Geronimo Application Server started > 00:06:49,487 ERROR [DirectoryMonitor] Unable to scan file > /files/dev/geronimo-1.1/assemblies/j2ee-jetty-server/target/geronimo-1.1-SNAPSHOT/deploy/no-geronimo-plan.war > during initialization > java.lang.IllegalArgumentException: Invalid id: no-geronimo-plan > at > org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:49) > at > org.apache.geronimo.deployment.plugin.ConfigIDExtractor.identifyTargetModuleIDs(ConfigIDExtractor.java:168) > at > org.apache.geronimo.deployment.hot.DirectoryHotDeployer.isFileDeployed(DirectoryHotDeployer.java:166) > at > org.apache.geronimo.deployment.hot.DirectoryMonitor.initialize(DirectoryMonitor.java:191) > at > org.apache.geronimo.deployment.hot.DirectoryMonitor.run(DirectoryMonitor.java:169) > at java.lang.Thread.run(Thread.java:534) > 00:06:53,496 INFO [Hot Deployer] Deploying no-geronimo-plan.war > 00:06:53,840 WARN [JettyModuleBuilder] Web application does not contain a > WEB-INF/geronimo-web.xml deployment plan. This may or may not be a problem, > depending on whether you have things like resource references that need to be > resolved. You can also give the deployer a separate deployment plan file on > the command line. > Deployed default/no-geronimo-plan/1146370013515/war @ > http://wildfire:8080/no-geronimo-plan > I'll clean out the server and try to reproduce from scratch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira