You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Markward Schubert <ma...@gmail.com> on 2013/09/02 18:22:27 UTC

tomcat7w.exe

I have a short question.
Does the monitor exe do anything "magical" when a tomcat service is started
the first time with it, in contrast to starting the already installed
service with the windows service manager?

In fact our application would not start until we start the service from the
monitor exe.
Of course this is something in our app, but there must be some external
parameter, being "fixed" by running the exe first.

Monitor and servicemanagement both would be started "As Administrator", but
with different results.

After the Monitor was run once, the box seems to be in a "working" mode, so
after that, we can uninstall the service and delete the folder and do a
reinstall and everything would work, even without calling tomcat7w.exe.
This also makes debugging for me a bit hard at the moment, as the only
windows server 2012 box I currently have, is in "fixed" mode now.

Any help is very much appreciated!

Regards,
Markward

Re: tomcat7w.exe

Posted by Markward Schubert <ma...@gmail.com>.
Christopher,

>
> On 9/2/13 12:22 PM, Markward Schubert wrote:
> > I have a short question. Does the monitor exe do anything "magical"
> > when a tomcat service is started the first time with it, in
> > contrast to starting the already installed service with the windows
> > service manager?
> >
> > In fact our application would not start until we start the service
> > from the monitor exe. Of course this is something in our app, but
> > there must be some external parameter, being "fixed" by running the
> > exe first.
> >
> > Monitor and servicemanagement both would be started "As
> > Administrator", but with different results.
> >
> > After the Monitor was run once, the box seems to be in a "working"
> > mode, so after that, we can uninstall the service and delete the
> > folder and do a reinstall and everything would work, even without
> > calling tomcat7w.exe. This also makes debugging for me a bit hard
> > at the moment, as the only windows server 2012 box I currently
> > have, is in "fixed" mode now.
>
> Consider installing guest-VM software such as VirtualBox, VMWare, etc.
> with a disk snapshot taken while you are in "broken mode". Then, you
> can play with the configuration, launching, etc. and roll-back at any
> time back into the broken state in order to try something else (or
> verify that your last effort was correct).
>
> I do this kind of thing all the time, and it is very effective.
>

Thanks a lot for the advice, also to you other folks!
I thought about using some vm-boxes, but we decided to not invest further
into this issue at the moment. If this happens again in some setup, I will
digg into the problem again and will report, if I have any new information
or a solution.

Regards,
Markward

Re: tomcat7w.exe

Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Markward,

On 9/2/13 12:22 PM, Markward Schubert wrote:
> I have a short question. Does the monitor exe do anything "magical"
> when a tomcat service is started the first time with it, in
> contrast to starting the already installed service with the windows
> service manager?
> 
> In fact our application would not start until we start the service
> from the monitor exe. Of course this is something in our app, but
> there must be some external parameter, being "fixed" by running the
> exe first.
> 
> Monitor and servicemanagement both would be started "As
> Administrator", but with different results.
> 
> After the Monitor was run once, the box seems to be in a "working"
> mode, so after that, we can uninstall the service and delete the
> folder and do a reinstall and everything would work, even without
> calling tomcat7w.exe. This also makes debugging for me a bit hard
> at the moment, as the only windows server 2012 box I currently
> have, is in "fixed" mode now.

Consider installing guest-VM software such as VirtualBox, VMWare, etc.
with a disk snapshot taken while you are in "broken mode". Then, you
can play with the configuration, launching, etc. and roll-back at any
time back into the broken state in order to try something else (or
verify that your last effort was correct).

I do this kind of thing all the time, and it is very effective.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJSJyDQAAoJEBzwKT+lPKRYoOwP/RcwIXqcHt6LoGk5Obnw42k3
/OfmNLATPVaAkvd8MTzQAM4GVJinnQjziSYPMNZqHy/trOjpuGk7tQI++NxsTnv5
VhvxUUQ++uX5xBad1E6QwA3D0NScAAvYIS4Z27O2/w0Fe2SjYIaUcIvCBvWJk6qO
CgSE65A+BCE4OAoavzsDgp3aqNZlQhxlPjYaot2mGREff4Sbh1EkNW1DDB9z29ug
qavBD+sCf0NonOO2p7EGZbTkABCAW1InRIz630RvF1UW26Q6x9e0wCQlrL1G7HsV
JbRue06slztIIQsI7h9hnL28f/nKUrZb/5hZrV24UjUUhI3lyiQwn3uuqRnZKw7a
WUMwhaLGnMFBczFsdPqqkd7duZ/wlJi8hm0nNHPotBhOWQ7mXZaUz1fMGecasalO
gwmRTOk/BSUDUJcDVuLItT2bn6t6UO58THqo7UvzS+jhBEABiLL/A+YytdRQVViE
AOZJwXlbWTbRdIFwgmssOD7mRniFQWHmNA3sUTbq8yVtfN+q9z6R3AHXqMvqSPsn
IGGVJ25FzFtev5axnKvyGgfI8R68ha6tXPd+ZlLtxQ2gfa+xB+BexhvnDSYlPZ77
PSpYj4UlwuHm/aMnB3ySSh0QEcbCS1aCwdosQBLgbKWD40zD9Cxlt+Z86OAA0YGK
mNe4jk53U8EL/7Eu5jJB
=4PjX
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: tomcat7w.exe

Posted by André Warnier <aw...@ice-sa.com>.
Please do not "top post". It makes it difficult to follow the flow of the conversation.

> 
> 
> 2013/9/2 David Kerber <dc...@verizon.net>
> 
>> On 9/2/2013 12:22 PM, Markward Schubert wrote:
>>
>>> I have a short question.
>>> Does the monitor exe do anything "magical" when a tomcat service is
>>> started
>>> the first time with it, in contrast to starting the already installed
>>> service with the windows service manager?
>>>
>>> In fact our application would not start until we start the service from
>>> the
>>> monitor exe.
>>> Of course this is something in our app, but there must be some external
>>> parameter, being "fixed" by running the exe first.
>>>
>> Did you maybe modify some of the Java parameters through tomcat7w?  It can
>> do more than just start and stop the service; it can also modify the
>> service startup parameters.
>>
>> HTH!
>>
>>
>>
>>> Monitor and servicemanagement both would be started "As Administrator",
>>> but
>>> with different results.
>>>
>>> After the Monitor was run once, the box seems to be in a "working" mode,
>>> so
>>> after that, we can uninstall the service and delete the folder and do a
>>> reinstall and everything would work, even without calling tomcat7w.exe.
>>> This also makes debugging for me a bit hard at the moment, as the only
>>> windows server 2012 box I currently have, is in "fixed" mode now.
>>>
>>> Any help is very much appreciated!
>>>
>>> Regards,
>>> Markward
>>>
>>>
Markward Schubert wrote:
 > Hi David,
 >
 > well my colleagues claimed, they did not change any parameter, wich I have
 > to believe until I create a fresh windows 2012 image to test myself, but if
 > they were wrong and they DID CHANGE something, would this not be reset, as
 > soon as we uninstall the service with the service.bat?
 >
 > As far as I understand, these settings, being managed by the tomcat7w.exe
 > stick to a specific windows service and would be lost as soon as I remove
 > the service. Or are there any parameters, manipulating the OS' settings?
 >
 > The funny thing is in fact, that after a complete uninstall subsequent
 > installs works from then on.
 >

And hi.
I do not know if this is the explanation to your particular issue, but consider the 
following :

1) what an "uninstall" procedure really removes and doesn't remove, is one of these 
Windows mysteries that are only accessible to wizards of the 7th circle, and mere mortals 
like you and I can only ever hope to wonder at the results.

2) when you/they initially installed the Service, was it installed so that the service 
would run under the "LocalService" (or "LocalSystem") special account, or was it installed 
so that the service would run under another user-id ?
If it was installed to run under another user-id, then one of the things that would happen 
in the background, is that this other user-id would have auto-magically received the 
"permission to run as a service" on the local machine, which is not granted to mere mortal 
users.
And this would not "un-happen" auto-magically when you remove Tomcat from the machine.
That is just an example of one of the things which are not symmetrical between installing 
and de-installing.  There are probably a lot more.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: tomcat7w.exe

Posted by Markward Schubert <ma...@gmail.com>.
Hi David,

well my colleagues claimed, they did not change any parameter, wich I have
to believe until I create a fresh windows 2012 image to test myself, but if
they were wrong and they DID CHANGE something, would this not be reset, as
soon as we uninstall the service with the service.bat?

As far as I understand, these settings, being managed by the tomcat7w.exe
stick to a specific windows service and would be lost as soon as I remove
the service. Or are there any parameters, manipulating the OS' settings?

The funny thing is in fact, that after a complete uninstall subsequent
installs works from then on.

Markward




2013/9/2 David Kerber <dc...@verizon.net>

> On 9/2/2013 12:22 PM, Markward Schubert wrote:
>
>> I have a short question.
>> Does the monitor exe do anything "magical" when a tomcat service is
>> started
>> the first time with it, in contrast to starting the already installed
>> service with the windows service manager?
>>
>> In fact our application would not start until we start the service from
>> the
>> monitor exe.
>> Of course this is something in our app, but there must be some external
>> parameter, being "fixed" by running the exe first.
>>
>
> Did you maybe modify some of the Java parameters through tomcat7w?  It can
> do more than just start and stop the service; it can also modify the
> service startup parameters.
>
> HTH!
>
>
>
>> Monitor and servicemanagement both would be started "As Administrator",
>> but
>> with different results.
>>
>> After the Monitor was run once, the box seems to be in a "working" mode,
>> so
>> after that, we can uninstall the service and delete the folder and do a
>> reinstall and everything would work, even without calling tomcat7w.exe.
>> This also makes debugging for me a bit hard at the moment, as the only
>> windows server 2012 box I currently have, is in "fixed" mode now.
>>
>> Any help is very much appreciated!
>>
>> Regards,
>> Markward
>>
>>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.**apache.org<us...@tomcat.apache.org>
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

Re: tomcat7w.exe

Posted by David Kerber <dc...@verizon.net>.
On 9/2/2013 12:22 PM, Markward Schubert wrote:
> I have a short question.
> Does the monitor exe do anything "magical" when a tomcat service is started
> the first time with it, in contrast to starting the already installed
> service with the windows service manager?
>
> In fact our application would not start until we start the service from the
> monitor exe.
> Of course this is something in our app, but there must be some external
> parameter, being "fixed" by running the exe first.

Did you maybe modify some of the Java parameters through tomcat7w?  It 
can do more than just start and stop the service; it can also modify the 
service startup parameters.

HTH!


>
> Monitor and servicemanagement both would be started "As Administrator", but
> with different results.
>
> After the Monitor was run once, the box seems to be in a "working" mode, so
> after that, we can uninstall the service and delete the folder and do a
> reinstall and everything would work, even without calling tomcat7w.exe.
> This also makes debugging for me a bit hard at the moment, as the only
> windows server 2012 box I currently have, is in "fixed" mode now.
>
> Any help is very much appreciated!
>
> Regards,
> Markward
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org