You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Thomas Preston (JIRA)" <de...@beehive.apache.org> on 2005/10/03 23:24:48 UTC

[jira] Commented: (BEEHIVE-960) Reload war problem when following tutorial

    [ http://issues.apache.org/jira/browse/BEEHIVE-960?page=comments#action_12331222 ] 

Thomas Preston commented on BEEHIVE-960:
----------------------------------------

I said before that it was no big deal because I could restart and the prob would go away. That's not exactly accurate and maybe this points toward the problem.

The directory: C:\tom\java\jakarta-tomcat-5.5.9\webapps\control_tutorial still exists after it fails to redeploy becuause the Struts.jar couldn't be deleted at redeploy. It's in:

C:\tom\java\jakarta-tomcat-5.5.9\webapps\control_tutorial\WEB-INF\lib

If you shutdown and then startup, the control_tutorial.war actually doesn't deploy properly because of missing web.xml (control_tutorial dir still exists with only struts.jar..so no web.xml). 

Anyway, to fix the problem created when trying to do hot-deploy, you actually have to shutdown, delete control_tutorial, startup.


> Reload war problem when following tutorial
> ------------------------------------------
>
>          Key: BEEHIVE-960
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-960
>      Project: Beehive
>         Type: Bug
>   Components: Tutorials
>     Versions: V1Beta
>  Environment: Not Applicable
>     Reporter: Thomas Preston
>     Priority: Minor

>
> In the final step of create controls tutorial having done all other steps successfully, have a problem with redeployment of the war:
> http://beehive.apache.org/docs/1.0m1/controls/tutorial_controls.html#test_3
> Looks like redeploy needs to undeploy and then you have some object of type shared.SharedFlow in the session. When the redeploy occurs the shared.SharedFlow class can't be found at the time that it needs to reload the session.  This is no big deal as you can stop and start the server to see the new code working, but it makes the demo not very nice.  Here is the stack:
> Oct 3, 2005 4:10:09 PM org.apache.catalina.startup.HostConfig checkResources
> INFO: Undeploying context [/control_tutorial]
> Oct 3, 2005 4:10:10 PM org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deploying web application archive control_tutorial.war
> Oct 3, 2005 4:10:10 PM org.apache.catalina.startup.ContextConfig applicationWebC
> onfig
> INFO: Missing application web.xml, using defaults only StandardEngine[Catalina].
> StandardHost[localhost].StandardContext[/control_tutorial]
> Oct 3, 2005 4:10:10 PM org.apache.catalina.session.StandardManager doLoad
> SEVERE: ClassNotFoundException while loading persisted sessions: java.lang.Class
> NotFoundException: shared.SharedFlow
> java.lang.ClassNotFoundException: shared.SharedFlow
>         at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa
> der.java:1332)
>         at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa
> der.java:1181)
>         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
>         at java.lang.Class.forName0(Native Method)
>         at java.lang.Class.forName(Class.java:242)
>         at org.apache.catalina.util.CustomObjectInputStream.resolveClass(CustomO
> bjectInputStream.java:73)
>         at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:153
> 8)
>         at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1460)
>         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1
> 693)
>         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
>         at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339)
>         at org.apache.catalina.session.StandardSession.readObject(StandardSessio
> n.java:1371)
>         at org.apache.catalina.session.StandardSession.readObjectData(StandardSe
> ssion.java:903)
>         at org.apache.catalina.session.StandardManager.doLoad(StandardManager.ja
> va:393)

-- 
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