Hi Harsha
Thank you for your advise.
Now I am trying DSS in another environment and find out whether it will be
killed again.
In the server logs, "wso2server.sh: line 300: 8634 killed" is displayed.
I checked the source in wso2server.sh as following.
when the state is "START_EXIT_STATUS", it can not run to line 300(done) and
to be killed, is it right?
(line 262)START_EXIT_STATUS=121
status=$START_EXIT_STATUS
#To monitor a Carbon server in remote JMX mode on linux host machines, set the
below system property.
# -Djava.rmi.server.hostname="your.IP.goes.here"
while [ "$status" = "$START_EXIT_STATUS" ]
do
$JAVACMD \
-Xbootclasspath/a:"$CARBON_XBOOTCLASSPATH" \
-Xms256m -Xmx1024m -XX:MaxPermSize=256m \
-XX:+HeapDumpOnOutOfMemoryError \
-XX:HeapDumpPath="$CARBON_HOME/repository/logs/heap-dump.hprof" \
$JAVA_OPTS \
-Dcom.sun.management.jmxremote \
-classpath "$CARBON_CLASSPATH" \
-Djava.endorsed.dirs="$JAVA_ENDORSED_DIRS" \
-Djava.io.tmpdir="$CARBON_HOME/tmp" \
-Dcatalina.base="$CARBON_HOME/lib/tomcat" \
-Dwso2.server.standalone=true \
-Dcarbon.registry.root=/ \
-Djava.command="$JAVACMD" \
-Dcarbon.home="$CARBON_HOME" \
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager \
-Dcarbon.config.dir.path="$CARBON_HOME/repository/conf" \
-Djava.util.logging.config.file="$CARBON_HOME/repository/conf/etc/logging-bridge.properties"
\
-Dcomponents.repo="$CARBON_HOME/repository/components/plugins" \
-Dconf.location="$CARBON_HOME/repository/conf"\
-Dcom.atomikos.icatch.file="$CARBON_HOME/lib/transactions.properties" \
-Dcom.atomikos.icatch.hide_init_file_path=true \
-Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true \
-Dcom.sun.jndi.ldap.connect.pool.authentication=simple \
-Dcom.sun.jndi.ldap.connect.pool.timeout=3000 \
-Dorg.terracotta.quartz.skipUpdateCheck=true \
-Djava.security.egd=file:/dev/./urandom \
-Dfile.encoding=UTF8 \
org.wso2.carbon.bootstrap.Bootstrap $*
status=$?
(line 300)done
"a period time" means it is not a fixed time,
sometimes it is several days and sometimes it is several hours.
stevegyc
Hi Stevegyc
It's stranged. Process may be killed due to ran out of memory,disk space and
etc. So it would be great if you can provide more details about it. May be you
find more info from server logs.
What you mean by sever state has changed in wso2server.sh and roughly how many
days you mean by long period time ?
Thanks,
Harsha
On Thu, Aug 7, 2014 at 3:15 PM, stevegyc <steve...@163.com> wrote:
Hi:
Recently I found after running for a period of time, The process of DSS
will be killed.
In the log, the following information is displayed:
wso2server.sh: line 300: 8634 killed.
I checked the file wso2server.sh, it seems like somehow the state has
changed.
Had anyone encountered this problem?
stevegyc
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Harsha Kumara
Software Engineer, WSO2 Inc.
Mobile: +94775505618
Blog:harshcreationz.blogspot.com_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
