Menu
▾
▴
wrapper-user
|
From: Kannan E. <kan...@gm...> - 2007-05-21 08:02:48
|
Hi, Wrapper Service - 3.2.1 OS - Windows XP I have read these links, http://wrapper.tanukisoftware.org/doc/english/props-envvars.html http://sourceforge.net/tracker/?func=detail&aid=1491138&group_id=39428&atid=425187 These links say how to provide an environment variable for a wrapper configuration. Whenever I change my environment variable to a different value, I need to uninstall the service, change the conf, reinstall the service and start the service However, Let us assume that I want to pick an environment variable that is defined in the system (My computer -> Right click -> Variables -> Set value). Can someone tell me how to achieve it? Basically, If I change the environment variable, simply restarting the service should pick the new value. Is this possible? -- Regards, Kannan Ekanath |
|
From: Hubert F. <hub...@ab...> - 2007-05-21 08:45:12
|
Where is the correct place to stop the WrapperActionServer? I use implementation method 3. I initialize WrapperActionServer in the start() method and stop it by calling the WrapperActionServer int the stop() method. If I don't call the stop method, wrapper behaves good if I request shutdown or restart using WrapperActionServer with telnet. If I call WrapperActionServer.stop() , the process hangs. Last thing I see is "WrapperListener.stop runner thread started." Can anybody please help? Hubert INFO | jvm 1 | 2007/05/21 10:32:09 | WrapperManager Debug: WrapperManager.stop(0) called by thread: WrapperActionServer_runner INFO | jvm 1 | 2007/05/21 10:32:09 | WrapperManager Debug: Send a packet STOP : 0 DEBUG | wrapperp | 2007/05/21 10:32:09 | read a packet STOP : 0 DEBUG | wrapper | 2007/05/21 10:32:09 | JVM requested a shutdown. (0) DEBUG | wrapper | 2007/05/21 10:32:09 | wrapperStopProcess(0) called. DEBUG | wrapper | 2007/05/21 10:32:09 | Sending stop signal to JVM DEBUG | wrapperp | 2007/05/21 10:32:09 | send a packet STOP : NULL INFO | jvm 1 | 2007/05/21 10:32:09 | WrapperManager Debug: Received a packet STOP : INFO | jvm 1 | 2007/05/21 10:32:10 | WrapperManager Debug: Thread, WrapperActionServer_runner, handling the shutdown process. INFO | jvm 1 | 2007/05/21 10:32:10 | WrapperManager Debug: calling listener.stop() INFO | jvm 1 | 2007/05/21 10:32:10 | WrapperManager Debug: Waiting for WrapperListener.stop runner thread to complete. INFO | jvm 1 | 2007/05/21 10:32:10 | WrapperManager Debug: WrapperListener.stop runner thread started. ________________________________________ ABACUS User Conference 2007 ABACUS Business Software: Next Generation Donnerstag, 14. oder Freitag, 15. Juni 2007 Anmeldung unter: www.abacus.ch |
|
From: Chandra P. <cp...@ig...> - 2007-05-23 23:27:48
|
It will be quite useful if wrapper can support, wrapper.java.additional.N.development=3D-DDevSpecificProperty wrapper.java.additional.N.staging=3D-DStagingSpecificProperty wrapper.java.additional.N.production=3D-DProductionSpecificProperty #APPLICATION_ROLE variable is set to either (development, staging, production)=20 wrapper.config.filter.selector=3D%APPLICATION_ROLE% I am wondering if anything like this already exists or in the pipeline. -Chandra |
|
From: Leif M. <le...@ta...> - 2007-05-24 01:08:10
|
Chandra, This is something that I often do myself using Ant. It is quite easy to do token replacements using Ant and generate the wrapper.conf from a template. Have you looked into this? It would make your production wrapper.conf much cleaner than what you suggested. Let me know if there are some reasons why Ant would not work for you. Cheers, Leif Chandra Patni wrote: > It will be quite useful if wrapper can support, > > wrapper.java.additional.N.development=-DDevSpecificProperty > wrapper.java.additional.N.staging=-DStagingSpecificProperty > wrapper.java.additional.N.production=-DProductionSpecificProperty > > #APPLICATION_ROLE variable is set to either (development, staging, > production) > > wrapper.config.filter.selector=%APPLICATION_ROLE% > > I am wondering if anything like this already exists or in the pipeline. > > -Chandra |
|
From: Chandra P. <cp...@ig...> - 2007-05-24 06:26:57
|
Leif, We share application/configuration between servers. One example of this is -Xms -Xmx for servers with 2GB vs 4GB memory. And we don't want to have proliferation of config files for small changes but at the same time allow some minors variation based on tags. I hope that you recognize that fine grained config selectors are very useful features. One way to achieve the same effect by using=20 #include nfspath/%TAG_NAME%/j2ee.conf Due to strict numbering requirement for wrapper wrapper.java.additional.<n>, etc makes this difficult to maintain. Do you have any plans to remove this restriction? I was looking at the wrapper code and it didn't seem too difficult.=20 -Chandra -----Original Message----- From: wra...@li... [mailto:wra...@li...] On Behalf Of Leif Mortenson Sent: Wednesday, May 23, 2007 6:08 PM To: wra...@li... Subject: Re: [Wrapper-user] dev/stage/production configuration selectors Chandra, This is something that I often do myself using Ant. It is quite easy to do token replacements using Ant and generate the wrapper.conf from a template. Have you looked into this? It would make your production wrapper.conf much cleaner than what you suggested. Let me know if there are some reasons why Ant would not work for you. Cheers, Leif Chandra Patni wrote: > It will be quite useful if wrapper can support, > > wrapper.java.additional.N.development=3D-DDevSpecificProperty > wrapper.java.additional.N.staging=3D-DStagingSpecificProperty > wrapper.java.additional.N.production=3D-DProductionSpecificProperty > > #APPLICATION_ROLE variable is set to either (development, staging, > production)=20 > > wrapper.config.filter.selector=3D%APPLICATION_ROLE% > > I am wondering if anything like this already exists or in the pipeline. > > -Chandra ------------------------------------------------------------------------ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Chandra P. <cp...@ig...> - 2007-05-24 06:33:32
|
BTW, I am only asking for tagging <N> type properties. Usually, one would use wrapper.java.initmemory, wrapper.java.maxmemory for memory settings. Under this model, one would use wrapper.java.additional.<N> for memory settings.=20 We also use these for heaps > 4G. Wrapper is hard coded for no more 4G memory even for 64 bit versions. -----Original Message----- From: wra...@li... [mailto:wra...@li...] On Behalf Of Chandra Patni Sent: Wednesday, May 23, 2007 11:27 PM To: wra...@li... Subject: Re: [Wrapper-user] dev/stage/production configuration selectors Leif, We share application/configuration between servers. One example of this is -Xms -Xmx for servers with 2GB vs 4GB memory. And we don't want to have proliferation of config files for small changes but at the same time allow some minors variation based on tags. I hope that you recognize that fine grained config selectors are very useful features. One way to achieve the same effect by using=20 #include nfspath/%TAG_NAME%/j2ee.conf Due to strict numbering requirement for wrapper wrapper.java.additional.<n>, etc makes this difficult to maintain. Do you have any plans to remove this restriction? I was looking at the wrapper code and it didn't seem too difficult.=20 -Chandra -----Original Message----- From: wra...@li... [mailto:wra...@li...] On Behalf Of Leif Mortenson Sent: Wednesday, May 23, 2007 6:08 PM To: wra...@li... Subject: Re: [Wrapper-user] dev/stage/production configuration selectors Chandra, This is something that I often do myself using Ant. It is quite easy to do token replacements using Ant and generate the wrapper.conf from a template. Have you looked into this? It would make your production wrapper.conf much cleaner than what you suggested. Let me know if there are some reasons why Ant would not work for you. Cheers, Leif Chandra Patni wrote: > It will be quite useful if wrapper can support, > > wrapper.java.additional.N.development=3D-DDevSpecificProperty > wrapper.java.additional.N.staging=3D-DStagingSpecificProperty > wrapper.java.additional.N.production=3D-DProductionSpecificProperty > > #APPLICATION_ROLE variable is set to either (development, staging, > production)=20 > > wrapper.config.filter.selector=3D%APPLICATION_ROLE% > > I am wondering if anything like this already exists or in the pipeline. > > -Chandra ------------------------------------------------------------------------ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user ------------------------------------------------------------------------ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Leif M. <le...@ta...> - 2007-05-30 08:13:08
|
Chandra, I would still suggest using Ant to create your wrapper.conf. If that is not an option, how about this: In your wrapper.conf file, add an include line like this: #include ../conf/wrapper-%BUILD_MODE%.conf The you can set a BUILD_MODE environment variable to control exactly which include file is used. I was not clear from your original request how you would expect the wrapper to know which configuration mode to be using at any time anyway. Cheers, Leif Chandra Patni wrote: > BTW, I am only asking for tagging <N> type properties. Usually, one > would use wrapper.java.initmemory, wrapper.java.maxmemory for memory > settings. Under this model, one would use wrapper.java.additional.<N> > for memory settings. > We also use these for heaps > 4G. Wrapper is hard coded for no more 4G > memory even for 64 bit versions. > > > > > -----Original Message----- > From: wra...@li... > [mailto:wra...@li...] On Behalf Of Chandra > Patni > Sent: Wednesday, May 23, 2007 11:27 PM > To: wra...@li... > Subject: Re: [Wrapper-user] dev/stage/production configuration selectors > > Leif, > We share application/configuration between servers. One example of this > is -Xms -Xmx for servers with 2GB vs 4GB memory. And we don't want to > have proliferation of config files for small changes but at the same > time allow some minors variation based on tags. > > I hope that you recognize that fine grained config selectors are very > useful features. > > One way to achieve the same effect by using > > #include nfspath/%TAG_NAME%/j2ee.conf > > Due to strict numbering requirement for wrapper > wrapper.java.additional.<n>, etc makes this difficult to maintain. Do > you have any plans to remove this restriction? I was looking at the > wrapper code and it didn't seem too difficult. > > -Chandra > > -----Original Message----- > From: wra...@li... > [mailto:wra...@li...] On Behalf Of Leif > Mortenson > Sent: Wednesday, May 23, 2007 6:08 PM > To: wra...@li... > Subject: Re: [Wrapper-user] dev/stage/production configuration selectors > > Chandra, > This is something that I often do myself using Ant. It is quite easy > to > do token replacements using Ant and generate the wrapper.conf > from a template. Have you looked into this? It would make your > production wrapper.conf much cleaner than what you suggested. > > Let me know if there are some reasons why Ant would not work for > you. > > Cheers, > Leif > > Chandra Patni wrote: > >> It will be quite useful if wrapper can support, >> >> wrapper.java.additional.N.development=-DDevSpecificProperty >> wrapper.java.additional.N.staging=-DStagingSpecificProperty >> wrapper.java.additional.N.production=-DProductionSpecificProperty >> >> #APPLICATION_ROLE variable is set to either (development, staging, >> production) >> >> wrapper.config.filter.selector=%APPLICATION_ROLE% >> >> I am wondering if anything like this already exists or in the >> > pipeline. > >> -Chandra >> |
|
From: Chandra P. <cp...@ig...> - 2007-05-30 08:31:07
|
As I pointed out in my previous email, strict ordering of wrapper.java.additional.<n> makes include hard to maintain and fragile for wrapper.java.additional<n> type parameters. I think most of the wrapper users are bitten by a missing ordinal at some point. Perhaps you can consider dropping ordinal from "wrapper.java.additional", etc. You may have to do parse wrapper.conf multiple times to construct VM parameters and arguments.=20 =20 Per my original request, the value of "wrapper.config.filter.selector" should determine which one to pick. Of course it can be set to an environment variable. -Chandra -----Original Message----- From: wra...@li... [mailto:wra...@li...] On Behalf Of Leif Mortenson Sent: Wednesday, May 30, 2007 1:13 AM To: wra...@li... Subject: Re: [Wrapper-user] dev/stage/production configuration selectors Chandra, I would still suggest using Ant to create your wrapper.conf. If that is not an option, how about this: In your wrapper.conf file, add an include line like this: #include ../conf/wrapper-%BUILD_MODE%.conf The you can set a BUILD_MODE environment variable to control exactly which include file is used. I was not clear from your original request how you would expect the wrapper to know which configuration mode to be using at any time anyway. Cheers, Leif Chandra Patni wrote: > BTW, I am only asking for tagging <N> type properties. Usually, one > would use wrapper.java.initmemory, wrapper.java.maxmemory for memory > settings. Under this model, one would use wrapper.java.additional.<N> > for memory settings.=20 > We also use these for heaps > 4G. Wrapper is hard coded for no more 4G > memory even for 64 bit versions. > > > > > -----Original Message----- > From: wra...@li... > [mailto:wra...@li...] On Behalf Of Chandra > Patni > Sent: Wednesday, May 23, 2007 11:27 PM > To: wra...@li... > Subject: Re: [Wrapper-user] dev/stage/production configuration selectors > > Leif, > We share application/configuration between servers. One example of this > is -Xms -Xmx for servers with 2GB vs 4GB memory. And we don't want to > have proliferation of config files for small changes but at the same > time allow some minors variation based on tags. > > I hope that you recognize that fine grained config selectors are very > useful features. > > One way to achieve the same effect by using=20 > > #include nfspath/%TAG_NAME%/j2ee.conf > > Due to strict numbering requirement for wrapper > wrapper.java.additional.<n>, etc makes this difficult to maintain. Do > you have any plans to remove this restriction? I was looking at the > wrapper code and it didn't seem too difficult.=20 > > -Chandra > > -----Original Message----- > From: wra...@li... > [mailto:wra...@li...] On Behalf Of Leif > Mortenson > Sent: Wednesday, May 23, 2007 6:08 PM > To: wra...@li... > Subject: Re: [Wrapper-user] dev/stage/production configuration selectors > > Chandra, > This is something that I often do myself using Ant. It is quite easy > to > do token replacements using Ant and generate the wrapper.conf > from a template. Have you looked into this? It would make your > production wrapper.conf much cleaner than what you suggested. > > Let me know if there are some reasons why Ant would not work for > you. > > Cheers, > Leif > > Chandra Patni wrote: > =20 >> It will be quite useful if wrapper can support, >> >> wrapper.java.additional.N.development=3D-DDevSpecificProperty >> wrapper.java.additional.N.staging=3D-DStagingSpecificProperty >> wrapper.java.additional.N.production=3D-DProductionSpecificProperty >> >> #APPLICATION_ROLE variable is set to either (development, staging, >> production)=20 >> >> wrapper.config.filter.selector=3D%APPLICATION_ROLE% >> >> I am wondering if anything like this already exists or in the >> =20 > pipeline. > =20 >> -Chandra >> =20 ------------------------------------------------------------------------ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
