Yes, something isn't working right. I should be able to get eyed on it Monday.
Thanks for confirming my initial thought.
Sent with BlackBerry Work (www.blackberry.com)
From: Bill Stewart
Sent: Nov 20, 2020 12:39 PM
To: Tomcat Users List
Subject: Re: Tomcat
On Fri, Nov 20, 2020 at 10:59 AM jonmcalexander wrote:
> When adding an instance as a service and using a domain service account to
> run Tomcat,
> what additional user rights assignments does the service account need?
The account will need at least SeServiceLogonRight ("Log on as a
service").
From: Zbynek Vavros [mailto:zbynek_vav...@cz.ibm.com]
Subject: Tomcat Windows service console window
can anyone point me how to set it so console window
appears when service started?
Windows services do not use console windows - that's one of the major points of
running something as a
: |
|
--|
|RE: Tomcat Windows service console window
On 07/09/2010 10:23 AM, Mikolaj Rydzewski wrote:
I was trying to create izpack.org installer for Tomcat and my
application. There was only one problem - how to install Tomcat as a
Windows service.
I tried various Tomcat versions, 6.0.18, 6.0.20, 6.0.26. I gave up with
6.0.20. Installing
On 07/09/2010 10:23 AM, Mikolaj Rydzewski wrote:
Hi,
I was trying to create izpack.org installer for Tomcat and my
application. There was only one problem - how to install Tomcat as a
Windows service.
Startup.bat and shutdown.bat were working, but I need service to be
running.
Finally, after
On 09/07/2010 09:34, Mikolaj Rydzewski wrote:
On 07/09/2010 10:23 AM, Mikolaj Rydzewski wrote:
I was trying to create izpack.org installer for Tomcat and my
application. There was only one problem - how to install Tomcat as a
Windows service.
I tried various Tomcat versions, 6.0.18, 6.0.20,
This issue was resolved by correctly utilizing the constructor of the
StreamSource object. It was expecting a String in URL/URI format and we were
passing in the file name only. The Zip download option of Tomcat did not
mind, but the Windows Service Installer option threw the Unknown protocol
c
From: hoffmandirt [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat Windows Service Installer vs Core zip install xml
The Zip download option of Tomcat did not mind, but the
Windows Service Installer option threw the Unknown protocol
c error.
Possibly due to the lack of a current directory
That makes sense to me. Thanks Chuck.
Caldarale, Charles R wrote:
From: hoffmandirt [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat Windows Service Installer vs Core zip install xml
The Zip download option of Tomcat did not mind, but the
Windows Service Installer option threw
hoffmandirt wrote:
I am having issues with XSLT files depending on which download option of
Tomcat 6.0.14 that I choose. If I download the ZIP file under Core, my XSLT
files transform with no problems. However if I download and use the Windows
Service Installer instead, I am getting the
Interesting, however I am pointing to the same JDK 1.5 for both. I wanted to
switch to the service instead of the bat startup and shutdown scripts. I
will give that a try and check it out. I was searching google for could
not compile stylesheet.
markt-2 wrote:
hoffmandirt wrote:
I am
I have been fighting a similar/same problem. It started last month
unexpectedly without any OS/Java ugrades or any new applications. I also
use Tomcat as standalone.
I was running TC 4.0.31 on Win2k SP4 on a dual processor PowerEdge 1650.
Looking at the Event Viewer logs I was getting Access
On 6/3/06, Martin Gainty [EMAIL PROTECTED] wrote:
Good Morning Bill-
I agree this can be a bit of a challenge but I found starting with base
webapps and then adding one webapp at a time usually helps
Also in the server.xml turn on debug flag via debug attribute
Server
Good Morning Bill-
I agree this can be a bit of a challenge but I found starting with base
webapps and then adding one webapp at a time usually helps
Also in the server.xml turn on debug flag via debug attribute
Server port=PutDefaultPortNumberHere debug=1
Then check the Logs and send that to
15 matches
Mail list logo