Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 1.0, 1.0.1
-
Fix Version/s: 1.2-M3
-
Component/s: None
-
Labels:None
-
Environment:(all 32 Bit):
Windows XP SP2
Java 1.6.0_04
Tomcat 5.5.26
Grail 1.0
Description
reproducable as follows:
1. "grails create-app myapp"
2. "grails war"
3. deploy the war to <tomcat>/webapps
Everting works fine till now.
4. edit the "<development>/grails-app/views/layouts/main.gsp" (simply add "Hello" below the grails logo)
5. repeat steps 2. and 3.
Now the web app context "myapp" is now broken on the automatic context re-start . Tomcat stdout*.log message entry:
"log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository."
This does not happen, if the war is exploded manually into the Tomcat webapps.
Issue Links
| This issue is duplicated by: | ||||
| GRAILS-2544 | Stopping Tomcat Context and doing undeploy does not completely shut down app, grails jars still locked |
|
|
|
also happens with
as well as