Are you writing the service script by yourself or using the Service Register script in Geronimo ?
https://svn.apache.org/repos/asf/geronimo/server/branches/2.1/assemblies/geronimo-boilerplate-minimal/src/main/underlay/bin/gserviceReg.sh I never met the problem you described with the service registered by gserviceReg.sh On Thu, Nov 26, 2009 at 1:48 AM, Quintin Beukes <quin...@skywalk.co.za>wrote: > Regarding this same component, has anyone noticed the following problem. > > I start my Geronimo server with the following: > "$KMS_SERVER"/geronimo/bin/gsh -c "geronimo/start-server --logfile > '$KMS_SERVER/geronimo/var/log/startup.log'" & > USER=`<"$KMS_CONF/geronimo-auth-user"` > PASS=`<"$KMS_CONF/geronimo-auth-pass"` > "$KMS_SERVER"/geronimo/bin/gsh -c "geronimo/wait-for-server -u $USER -w > $PASS" > > When it finished starting a message is printed to the tune of > "Geronimo started in h:mm:ss.sss". Sometimes this works perfectly, > though on the odd occassion the messages is printed only after a new > shell prompt has been printed, and this again sometimes goes paired > with echoing being broken. So when you type, the shell receives the > input but it's not being echoed. I have to issue a "reset" command to > return back to normal. > > I have not noticed anything triggering this problem. It will happen > intermittently for no reason. And since it's always paired with the > message being printed after the prompt, I figure it's probably a race > condition? Note that the failure is paired backwards with the late > printing, though the late printing doesn't indicate the echo failure. > I do think they're related though. > > This is a good start: > quin...@quintin-laptop sbin $ sudo /opt/kms/sbin/service restart appserver > Shutting down... > Waiting for Geronimo server: localhost:1099 > Launching Geronimo Server... > Geronimo server is started > Geronimo Server started in 0:00:33.382 > quin...@quintin-laptop sbin $ > > This is a failed start (with enter pressed 3 times afterwards and then > "ls" entered + another enter): > quin...@quintin-laptop sbin $ sudo /opt/kms/sbin/service restart appserver > Shutting down... > Waiting for Geronimo server: localhost:1099 > Launching Geronimo Server... > Geronimo server is started > quin...@quintin-laptop sbin $ Geronimo Server started in 0:00:33.382 > quin...@quintin-laptop sbin $ quin...@quintin-laptop sbin $ > quin...@quintin-laptop sbin $ > 2.1.4.start-appserver 2.1.4.stop-appserver common.sh daemon init.d > install jsvc service start-appserver start-jar stop-appserver > stop-jar > quin...@quintin-laptop sbin $ > > It's not the same as above, though I do think it's caused by the same > component, as the only way shell echoing can become broken would be > the terminal not being restored/initialized properly. Anyone noticed > this problem? > > Quintin Beukes > > > > On Wed, Nov 25, 2009 at 5:13 PM, Shawn Jiang <genspr...@gmail.com> wrote: > > I'm using G2.1.4 in LF, it should be a general problems. I don't think > its > > a GShell specific problem. Instead, we met this problem with both "gsh > -c > > deploy deploy" and "deploy.sh deploy". > > > > > > On Wed, Nov 25, 2009 at 7:13 PM, chi runhua <chirun...@gmail.com> wrote: > >> > >> Thanks Shawn for the sharing. > >> > >> I'll collect this info into G doc. Could you specify the G version you > >> are using, or is it a general problem in all G servers with a GShell > >> environment? > >> > >> Jeff C > >> > >> On Wed, Nov 25, 2009 at 5:29 PM, Shawn Jiang <genspr...@gmail.com> > wrote: > >>> > >>> Lotus Foundation(LF) is a customized linux OS. We met a wierd problem > >>> when deploying applications to a running Geronimo on LF. > >>> > >>> The deploy process is not successful and never return. I remote debug > >>> to it and found that it's caused by some native code execution when > doing > >>> the JLine UnixTerminal init. Seems LF does not support some native > code > >>> used in UnixTerminal. > >>> > >>> To resolve this problem, We have to set a system property in JAVA_OPTS > >>> > >>> -Djline.terminal=jline.UnsupportedTerminal > >>> > >>> to force the JLine use UnsupportedTerminal instead of UnixTerminal. > I'm > >>> sending this mail to log it in case someone else might meet similar > problems > >>> on other platforms, > >>> > >>> -- > >>> Shawn > >> > > > > > > > > -- > > Shawn > > > -- Shawn
