Zitat von Dennis Hesse BAW <[email protected]>: > Ok, to get more support is a big pro for tomcat ;-) Yep, the only thing is that we are a small group using IBM Java. Anyways, we have the same platform and I am part of the developer group. > > Java is the same in our case. I updated all the "Empfohlen"-Packages (is it > "recommended" in an english environment?) via YaST. > Zypper doesn't list any updates.
Did you execute "zypper refresh" ?. And yes, "Empfohlen" is recommended. > > I'll be giving Tomcat a try. Some hints The home directory of the the tomcat user is /usr/share/tomcat6, but is owned by root:root. This produces a lot of messages in /var/log/tomcat6/catalina.out Execute the following chown tomcat:tomcat /usr/share/tomcat6 su - tomcat mkdir systemprefs mkdir userprefs exit Now edit /etc/sysconfig/tomcat6 and add to CATALINA_OPTS "-Xmx1024m -Djava.awt.headless=true -Djava.util.prefs.userRoot=/usr/share/tomcat6/userprefs -Djava.util.prefs.systemRoot=/usr/share/tomcat6/systemprefs" If you have internet access using a proxy, add "-Dhttp.proxyHost=XXXX -Dhttp.proxyPort=????" This is my setup Christian > > Dennis. > > 2011/6/14 <[email protected]> > >> Zitat von Dennis Hesse BAW <[email protected]>: >> >> Its java-1_6_0-ibm, the one that came with SLES, we're trying to keep as >>> much of the SLES-Repos as possible, already had to get two clean >>> installations done after installing packages that didn't come from Novell >>> that were producing errors ... >>> >> >> I am using java-1_6_0-ibm, too. >> rpm -qa | grep java >> gives me >> java-1_6_0-ibm-1.6.0_sr9.1-1.5.1 >> which is the latest version >> >> >> >> >>> We had Geoserver in tomcat in our test environment and had problems that >>> tomcat itself randomly crashed, for example when deploying a war-file with >>> it, and we wanted to keep geoserver out of it so that if tomcat crashes at >>> least geoserver would still be accessible. >>> Why would you prefer a tomcat installation? >>> >> >> tomcat/geoserver is widely used. You will get a lot of support in the >> community. Jetty is intended for developing and it is a lot of work making >> jetty ready for production. My geoserver also runs on SLES 11.1. My tomcat >> is >> tomcat6-lib-6.0.18-17.1 >> >> Do you execute online updates ? >> >> zypper refresh ; zypper up >> >> >> Christian >> >> >> >> >> >> >>> Dennis. >>> >>> 2011/6/14 <[email protected]> >>> >>> Zitat von Dennis Hesse BAW <[email protected]>: >>>> >>>> I could, but we made the experience that geoserver is more stable >>>> without >>>> >>>>> tomcat, so we decided against it ... >>>>> It runs on a x86-64 VMWare virtual machine, Xeons under it ... >>>>> >>>>> >>>> Sun Java or OpenJDK ? I would strongly recommend the first. >>>> Did you install JAI. If not, you should. >>>> >>>> I do not have the possibilities since I am on a ppc architecture. :-( >>>> >>>> About tomcat: Do you really plan to use jetty in a production environment >>>> ?. I would not recommend this. What concrete problems do you have ? >>>> >>>> Christian >>>> >>>> >>>> >>>> >>>> I'll try to write a script on my own, maybe I have luck with it ;) >>>>> >>>>> 2011/6/14 <[email protected]> >>>>> >>>>> I developed the script on a SLES 11 on an IBM P6 LPAR (IBM ppc >>>>> series). >>>>> >>>>>> I >>>>>> do not use it anymore, since I installed tomcat, life is easier now. Do >>>>>> you >>>>>> have a possibility to use tomcat ? >>>>>> >>>>>> Christian >>>>>> >>>>>> Zitat von Dennis Hesse BAW <[email protected]>: >>>>>> >>>>>> Hi, >>>>>> >>>>>> >>>>>>> Just to keep my confusion alive, I just did a "service geoserver >>>>>>> status" >>>>>>> again after half an hour of doing nothing on the server, and and it >>>>>>> worked. >>>>>>> After logging out and in once more, it doesn't work anymore ... >>>>>>> >>>>>>> still confused >>>>>>> Dennis. >>>>>>> >>>>>>> 2011/6/10 Dennis Hesse BAW <[email protected]> >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> >>>>>>>> I'm experiencing a strange behaviour with the geoserver start script. >>>>>>>> >>>>>>>> I'm runnig geoserver 2.1 on a Suse SLES11 SP1, geoserver is installed >>>>>>>> without tomcat. >>>>>>>> >>>>>>>> I'm using the following script: >>>>>>>> >>>>>>>> #!/bin/sh >>>>>>>> # >>>>>>>> # /etc/init.d/tgtd >>>>>>>> # >>>>>>>> ### BEGIN INIT INFO >>>>>>>> # Provides: geoserver >>>>>>>> # Required-Start: $remote_fs $network >>>>>>>> # Should-Start: >>>>>>>> # Required-Stop: $remote_fs $network >>>>>>>> # Should-Stop: >>>>>>>> # Default-Start: 3 5 >>>>>>>> # Default-Stop: >>>>>>>> # Short-Description: geoserver test deployment >>>>>>>> # Description: Starts and stops geoserver >>>>>>>> ### END INIT INFO >>>>>>>> >>>>>>>> # >>>>>>>> # >>>>>>>> >>>>>>>> >>>>>>>> # Source LSB init functions >>>>>>>> . /etc/rc.status >>>>>>>> >>>>>>>> rc_reset >>>>>>>> >>>>>>>> >>>>>>>> PORT=7070 >>>>>>>> #echo $PORT >>>>>>>> STOPPORT=7069 >>>>>>>> #echo $STOPPORT >>>>>>>> #SUFFIX=_test >>>>>>>> >>>>>>>> PATH=/sbin:/bin:/usr/sbin:/usr/bin >>>>>>>> #echo $PATH >>>>>>>> NAME=geoserver >>>>>>>> #echo $NAME >>>>>>>> SCRIPTNAME=/etc/init.d/$NAME >>>>>>>> #echo $SCRIPTNAME >>>>>>>> LOCKFILE="/var/lock/subsys/${NAME}" >>>>>>>> #echo $LOCKFILE >>>>>>>> RETVAL=0 >>>>>>>> #echo $RETVAL >>>>>>>> >>>>>>>> JAVA_HOME=/usr/lib64/jvm/jre >>>>>>>> #echo $JAVA_HOME >>>>>>>> GEOSERVER_DATA_DIR=/opt/geoserver/data_dir >>>>>>>> #echo $GEOSERVER_DATA_DIR >>>>>>>> GEOSERVER_USER=root >>>>>>>> #echo $GEOSERVER_USER >>>>>>>> GEOSERVER_HOME=/opt/geoserver >>>>>>>> #echo $GEOSERVER_HOME >>>>>>>> >>>>>>>> >>>>>>>> # Read configuration variable file if it is present >>>>>>>> [ -r /etc/default/$NAME ] && . /etc/default/$NAME >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> case "$1" in >>>>>>>> start) >>>>>>>> ps -ef | grep -v grep | grep "${GEOSERVER_DATA_DIR}" #> /dev/null >>>>>>>> RETVAL=$? >>>>>>>> if [ $RETVAL -eq 0 ]; then >>>>>>>> echo "${NAME} is already running " >>>>>>>> else >>>>>>>> echo "Starting ${NAME} " >>>>>>>> echo `date` >> $GEOSERVER_DATA_DIR/serverlog >>>>>>>> cd "$GEOSERVER_HOME" >>>>>>>> su "$GEOSERVER_USER" -c "$JAVA_HOME/bin/java -server >>>>>>>> -DGEOSERVER_DATA_DIR=$GEOSERVER_DATA_DIR -Djava.awt.headless=true >>>>>>>> -Djetty.port=$PORT -DSTOP.PORT=$STOPPORT -DSTOP.KEY=geoserver -jar >>>>>>>> start.jar >>>>>>>> >> $GEOSERVER_DATA_DIR/serverlog 2>&1 &" >>>>>>>> >>>>>>>> RETVAL=$? >>>>>>>> if [ $RETVAL -eq 0 ]; then >>>>>>>> touch "${LOCKFILE}" >>>>>>>> else >>>>>>>> echo "Failure starting ${NAME}" >>>>>>>> fi >>>>>>>> fi >>>>>>>> ;; >>>>>>>> stop) >>>>>>>> ps -ef | grep -v grep | grep "${GEOSERVER_DATA_DIR}" #> >>>>>>>> /dev/null >>>>>>>> RETVAL=$? >>>>>>>> if [ $RETVAL -eq 0 ]; then >>>>>>>> echo "Stopping ${NAME} " >>>>>>>> echo `date` >> $GEOSERVER_DATA_DIR/serverlog >>>>>>>> cd "$GEOSERVER_HOME" >>>>>>>> su "$GEOSERVER_USER" -c "$JAVA_HOME/bin/java >>>>>>>> -DSTOP.PORT=$STOPPORT >>>>>>>> -DSTOP.KEY=geoserver -jar start.jar --stop >> >>>>>>>> $GEOSERVER_DATA_DIR/serverlog >>>>>>>> 2>&1" >>>>>>>> >>>>>>>> RETVAL=$? >>>>>>>> if [ $RETVAL -eq 0 ]; then >>>>>>>> rm "${LOCKFILE}" >>>>>>>> else >>>>>>>> echo "Failure stopping ${NAME}" >>>>>>>> fi >>>>>>>> else >>>>>>>> echo "${NAME} is not running" >>>>>>>> fi >>>>>>>> ;; >>>>>>>> >>>>>>>> >>>>>>>> restart|reload) >>>>>>>> $0 stop >>>>>>>> sleep 5 >>>>>>>> $0 start >>>>>>>> ;; >>>>>>>> status) >>>>>>>> ps -ef | grep -v grep | grep /opt/geo >>>>>>>> RETVAL=$? >>>>>>>> if [ $RETVAL -eq 0 ]; then >>>>>>>> echo "$NAME is running." >>>>>>>> else >>>>>>>> echo "$NAME is not running." >>>>>>>> fi >>>>>>>> >>>>>>>> ;; >>>>>>>> *) >>>>>>>> echo $"Usage: $0 {start|stop|restart|status}" >>>>>>>> exit 1 >>>>>>>> esac >>>>>>>> rc_exit >>>>>>>> >>>>>>>> The problem I've got is that the script doesn't work properly. >>>>>>>> Sometimes >>>>>>>> it >>>>>>>> does just what it should do, but the next moment the restart-command >>>>>>>> just >>>>>>>> tells me that the geoserver isn't running. ps -ef | grep -v grep | >>>>>>>> grep >>>>>>>> /opt/geo is producing an output telling geoserver is running even in >>>>>>>> that >>>>>>>> case, the script just can't get this info. I've had an echo >>>>>>>> $RETVALwritten in, and the script returned 1 in that case. >>>>>>>> >>>>>>>> >>>>>>>> Hope you can follow me and can tell me what is going wrong here? >>>>>>>> >>>>>>>> Thanks >>>>>>>> Dennis. >>>>>>>> -- >>>>>>>> >>>>>>>> Dennis Hesse >>>>>>>> Bundesanstalt für Wasserbau Dienststelle Hamburg >>>>>>>> Wedeler Landstraße 157 22559 Hamburg >>>>>>>> Tel.: 040 81908-0 E-mail: [email protected] >>>>>>>> Webseiten: BAW <http://www.baw.de/de/index.php.html> || MDI-DE< >>>>>>>> http://www.mdi-de.org/> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>> >>>>>>> Dennis Hesse >>>>>>> Bundesanstalt für Wasserbau Dienststelle Hamburg >>>>>>> Wedeler Landstraße 157 22559 Hamburg >>>>>>> Tel.: 040 81908-0 E-mail: [email protected] >>>>>>> Webseiten: BAW <http://www.baw.de/de/index.php.html> || >>>>>>> MDI-DE<http://www.mdi-de.org/> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> ---------------------------------------------------------------- >>>>>> This message was sent using IMP, the Internet Messaging Program. >>>>>> >>>>>> >>>>>> >>>>>> >>>>> -- >>>>> >>>>> Dennis Hesse >>>>> Bundesanstalt für Wasserbau Dienststelle Hamburg >>>>> Wedeler Landstraße 157 22559 Hamburg >>>>> Tel.: 040 81908-0 E-mail: [email protected] >>>>> Webseiten: BAW <http://www.baw.de/de/index.php.html> || >>>>> MDI-DE<http://www.mdi-de.org/> >>>>> >>>>> >>>>> >>>> >>>> ---------------------------------------------------------------- >>>> This message was sent using IMP, the Internet Messaging Program. >>>> >>>> >>>> >>> >>> -- >>> >>> Dennis Hesse >>> Bundesanstalt für Wasserbau Dienststelle Hamburg >>> Wedeler Landstraße 157 22559 Hamburg >>> Tel.: 040 81908-0 E-mail: [email protected] >>> Webseiten: BAW <http://www.baw.de/de/index.php.html> || >>> MDI-DE<http://www.mdi-de.org/> >>> >>> >> >> >> ---------------------------------------------------------------- >> This message was sent using IMP, the Internet Messaging Program. >> >> > > > -- > > Dennis Hesse > Bundesanstalt für Wasserbau Dienststelle Hamburg > Wedeler Landstraße 157 22559 Hamburg > Tel.: 040 81908-0 E-mail: [email protected] > Webseiten: BAW <http://www.baw.de/de/index.php.html> || > MDI-DE<http://www.mdi-de.org/> > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
