[ http://issues.apache.org/jira/browse/JS2-199?page=history ]
     
Ate Douma closed JS2-199:
-------------------------

     Assign To: Ate Douma
    Resolution: Fixed

See http://issues.apache.org/jira/browse/JS2-210.
Deployment has been completely rewritten and this problem cannot occur anymore. 

> Deployment Race Condition with Tomcat
> -------------------------------------
>
>          Key: JS2-199
>          URL: http://issues.apache.org/jira/browse/JS2-199
>      Project: Jetspeed 2
>         Type: Bug
>   Components: Deployment
>     Versions: 2.0-dev/cvs
>  Environment: tomcat 5.0.28
>     Reporter: John Donald
>     Assignee: Ate Douma
>     Priority: Critical

>
> The deployment of portlets and the deployment of Tomcat conflict.
> Step 1: Tomcat starts and looks for webapps
> Step 2: Tomcat finds jetspeed.xml and initializes the application
> Step 3: Jetspeed starts the DeploymentManager
> Step 4: The DeploymentManager finds the demo portal application and begins to 
> deploy it using manager.xml
> Step 5: Tomcat continues looking for webapps and finds webapps/demo which has 
> been created by Jetspeed
> Step 6: Tomcat initializes the demo webapp
> Step 7: The DeploymentManager continues and tries to register /demo through 
> the tomcat-manager
> Step 8: Error: /demo has already been deployed.
> This happens obviously also when autodeploy is set to false.
> Tomcat is just not finished its standard deployment, when it is interrupted 
> by the JS-DeploymentManager.
> It's critical, because when this happens to the security webapp you cannot 
> login.
> I've added the output I get when starting from scratch.
> [...]
> 21.01.2005 05:38:17 org.apache.catalina.core.StandardHostDeployer install
> INFO: Processing Context configuration file URL 
> file:C:\usr\jakarta-tomcat-5.0.28\conf\Catalina\localhost\jetspeed.xml
>  INFO: Deployment server port: 8080
>  INFO: Deployment server: localhost
>  INFO: Starting auto deployment service: 
> org.apache.jetspeed.deployment.impl.StandardDeploymentManager
>  INFO: Deployment scanning delay: 10000
>  INFO: Deployment staging directory: 
> C:\usr\jakarta-tomcat-5.0.28\webapps\jetspeed/WEB-INF/deploy
>  INFO: Deployment scanner successfuly started!
>  INFO: JetspeedServlet successfuly created the portal Engine. [EMAIL 
> PROTECTED]
>  INFO: JetspeedServlet attempting to initialize the  portletcontainer...
>  INFO: JetspeedServlet has successfuly initialized the portlet container...
>  INFO: Jetspeed Initialization complete, Ready to service requests.
> JetspeedContainerServlet: starting initialization of context Jetspeed-2 
> Enterprise Portal
> JetspeedContainerServlet: Initialization complete for context Jetspeed-2 
> Enterprise Portal
>  INFO: Loading portlet application from web archive 
> C:\usr\jakarta-tomcat-5.0.28\webapps\jetspeed\WEB-INF\deploy\demo.war
>  INFO: Preparing to (re) deploy portlet app "demo"
>  INFO: Deploying portlet applicaion WAR demo.war
>  INFO: Portlet application deployment target directory is 
> C:\usr\jakarta-tomcat-5.0.28\webapps\jetspeed/..//demo
> 21.01.2005 05:38:34 org.apache.catalina.core.StandardHostDeployer install
> INFO: Processing Context configuration file URL 
> file:C:\usr\jakarta-tomcat-5.0.28\conf\Catalina\localhost\manager.xml
> 21.01.2005 05:38:34 org.apache.catalina.core.StandardHostDeployer install
> INFO: Installing web application at context path /demo from URL 
> file:C:\usr\jakarta-tomcat-5.0.28\webapps\demo
> Writing out infused web.xml for demo
> 21.01.2005 05:38:37 org.apache.coyote.http11.Http11Protocol start
> INFO: Starting Coyote HTTP/1.1 on http-8080
> 21.01.2005 05:38:38 org.apache.jk.common.ChannelSocket init
> INFO: JK2: ajp13 listening on /0.0.0.0:8009
> 21.01.2005 05:38:38 org.apache.jk.server.JkMain start
> INFO: Jk running ID=0 time=16/141  
> config=C:\usr\jakarta-tomcat-5.0.28\conf\jk2.properties
> 21.01.2005 05:38:38 org.apache.catalina.startup.Catalina start
> INFO: Server startup in 21734 ms
> namespace = http://portals.apache.org/jetspeed
> name = service
> object = [EMAIL PROTECTED]
> service = [EMAIL PROTECTED]
>  INFO: Loading web.xml into memory....
>  INFO: Saving the portlet.xml in the registry...
>  INFO: Committing registry changes...
>  INFO: FileSystem deployment done.
> ERROR: org.apache.jetspeed.deployment.DeploymentException: Error 
> (re)deploying portlet app: 
> org.apache.jetspeed.tools.pamanager.PortletApplicationException: Cat
> alina container action failed, "FEHLER - Anwendung existiert bereits f�r 
> Kontext Pfad /demo
> "
> org.apache.jetspeed.deployment.DeploymentException: Error (re)deploying 
> portlet app: org.apache.jetspeed.tools.pamanager.PortletApplicationException: 
> Catalina c
> ontainer action failed, "FEHLER - Anwendung existiert bereits f�r Kontext 
> Pfad /demo
> "
>         at 
> org.apache.jetspeed.deployment.impl.DeployPortletAppEventListener.doDeploy(DeployPortletAppEventListener.java:299)
>         at 
> org.apache.jetspeed.deployment.impl.DeployPortletAppEventListener.invokeDeploy(DeployPortletAppEventListener.java:162)
>         at 
> org.apache.jetspeed.deployment.impl.StandardDeploymentManager.dispatch(StandardDeploymentManager.java:304)
>         at 
> org.apache.jetspeed.deployment.impl.StandardDeploymentManager.fireDeploymentEvent(StandardDeploymentManager.java:195)
>         at 
> org.apache.jetspeed.deployment.impl.StandardDeploymentManager$FileSystemScanner.run(StandardDeploymentManager.java:458)
> Caused by: org.apache.jetspeed.tools.pamanager.PortletApplicationException: 
> Catalina container action failed, "FEHLER - Anwendung existiert bereits f�r 
> Kontext
> Pfad /demo
> "
>         at 
> org.apache.jetspeed.tools.pamanager.ApplicationServerPAM.checkResponse(ApplicationServerPAM.java:225)
>         at 
> org.apache.jetspeed.tools.pamanager.ApplicationServerPAM.deploy(ApplicationServerPAM.java:84)
>         at 
> org.apache.jetspeed.deployment.impl.DeployPortletAppEventListener.doDeploy(DeployPortletAppEventListener.java:259)
>         ... 4 more
> ERROR: Error deploying 
> C:\usr\jakarta-tomcat-5.0.28\webapps\jetspeed\WEB-INF\deploy\demo.war

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to