This link has been bookmarked by 1 people . It was first bookmarked on 06 Mar 2009, by NickITMGR.
-
06 Mar 09
-
Re: Alfresco Labs 3 Final - Shutdown ERROR
by tvaughan77 on 13 Feb 2009, 19:57 For the "16:38:22,222 User:System WARN [service.descriptor.DescriptorService] Alfresco JVM - WARNING - maximum heap size 493,063MB is less than recommended 512MB" . . . change your alfresco.sh (or alfresco.bat in your case) to look like:- Code: Select all
# Set any default JVM values
export JAVA_OPTS='-Xms256m -Xmx1024m -XX:MaxPermSize=128m -server'
The shutdown error is a known issue that involves log4j trying to log some messages after the context is shutdown; there's a big pissing contest between the log4j guys and a bunch of other application teams about "whose fault it is." As things stand now, I believe there is *no* solution to this problem. What I did was to follow someone else's advice on this board and startup alfresco with a JAVA_OPTS parameter that's used to kill alfresco when necessary. So, add this to your alfresco.bat file as well:- Code: Select all
#
# Custom param that serves only as a 'marker' for kill process...see:
# http://forums.alfresco.com/en/viewtopic.php?f=9&t=13763&p=49967
#
export JAVA_OPTS="${JAVA_OPTS} -DshutdownIdentifier=alfrepo"
I then use the "-DshutdownIdentifier" as a search string for killing the alfresco process when I need to shut alfresco down.
Finally, the difference between "alfresco" and "virtual alfresco" is pretty important:
* Alfresco is a web application that runs on "tomcat #1" . . . it's a separate *.war file containing all the alfresco code
* The web content management aspect of alfresco includes an ability to "preview" a website within a sandbox before actually deploying your web site. To implement this "preview" functionality, alfresco ships with a complete separate "tomcat #2" that is used to host content for preview purposes.
So, when you "start alfresco", you really need to do 2 things: start tomcat #1, and then start tomcat #2 -
For the "16:38:22,222 User:System WARN [service.descriptor.DescriptorService] Alfresco JVM - WARNING - maximum heap size 493,063MB is less than recommended 512MB" . . . change your alfresco.sh (or alfresco.bat in your case) to look like:
-
For the "16:38:22,222 User:System WARN [service.descriptor.DescriptorService] Alfresco JVM - WARNING - maximum heap size 493,063MB is less than recommended 512MB" . . . change your alfresco.sh (or alfresco.bat in your case) to look like:
-
Re: Alfresco Labs 3 Final - Shutdown ERROR
by tvaughan77 on 13 Feb 2009, 19:57 For the "16:38:22,222 User:System WARN [service.descriptor.DescriptorService] Alfresco JVM - WARNING - maximum heap size 493,063MB is less than recommended 512MB" . . . change your alfresco.sh (or alfresco.bat in your case) to look like:- Code: Select all
# Set any default JVM values
export JAVA_OPTS='-Xms256m -Xmx1024m -XX:MaxPermSize=128m -server'
The shutdown error is a known issue that involves log4j trying to log some messages after the context is shutdown; there's a big pissing contest between the log4j guys and a bunch of other application teams about "whose fault it is." As things stand now, I believe there is *no* solution to this problem. What I did was to follow someone else's advice on this board and startup alfresco with a JAVA_OPTS parameter that's used to kill alfresco when necessary. So, add this to your alfresco.bat file as well:- Code: Select all
#
# Custom param that serves only as a 'marker' for kill process...see:
# http://forums.alfresco.com/en/viewtopic.php?f=9&t=13763&p=49967
#
export JAVA_OPTS="${JAVA_OPTS} -DshutdownIdentifier=alfrepo"
I then use the "-DshutdownIdentifier" as a search string for killing the alfresco process when I need to shut alfresco down.
Finally, the difference between "alfresco" and "virtual alfresco" is pretty important:
* Alfresco is a web application that runs on "tomcat #1" . . . it's a separate *.war file containing all the alfresco code
* The web content management aspect of alfresco includes an ability to "preview" a website within a sandbox before actually deploying your web site. To implement this "preview" functionality, alfresco ships with a complete separate "tomcat #2" that is used to host content for preview purposes.
So, when you "start alfresco", you really need to do 2 things: start tomcat #1, and then start tomcat #2
-
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.