date:20130227


Rainer Jung wrote:

On 26.02.2013 19:41, Jochen Wißmann wrote:

Hello,

i am trying to find an easy way to determine from the http-client side,
which  AJP13-worker handled my request.
So my basic idea is to use mod_header to add mod_jk`s env-variable
JK_WORKER_NAME to the Header of the http-response.
I tried to get something like this working:

httpd.conf:
...
Header add TC-Server %{JK_WORKER_NAME}e
...

All my previous attempts resulted in http-responses looking like this:

 HTTP/1.1 200 OK
 Set-Cookie: ARPT=LRWQXVS110.160.11.26CKMLQ; path=/
 Date: Tue, 26 Feb 2013 18:25:31 GMT
 Server: Apache/2.2.22 (Unix) mod_jk/1.2.36 mod_ssl/2.2.22
OpenSSL/0.9.8x DAV/2
 Set-Cookie: JSESSIONID=A4052BF60BA2007F0B0F47E2699AFDE.liferay0; Path=/
 Set-Cookie: GUEST_LANGUAGE_ID=en_US; Expires=Wed, 26-Feb-2014 18:25:31
GMT; Path=/
 Set-Cookie: COOKIE_SUPPORT=true; Expires=Wed, 26-Feb-2014 18:25:31
GMT; Path=/
 Liferay-Portal: Liferay Portal Community Edition 6.0.6 CE (Bunyan /
Build 6006 / February 17, 2011)
 ETag: 838b4ae2
 Content-Length: 8043
 X-Server-Ip: 110.160.11.26
 TC-Server: (null)
 Content-Type: text/html;charset=utf-8

Why do i get TC-Server: (null) ?
Using the Variable JK_WORKER_NAME to log the worker's name via
mod_log_config works fine.

Am i missing something? Is it even possible to access the env-variable
JK_WORKER_NAME with module mod_header?
Could anyone please help?
Thanks!


mod_jk respects the environment variable JK_WORKER_NAME when choosing a
target worker, but it does not set it.

mod_jk only sets a note with name JK_WORKER_NAME, which is different
from an env var. The n in your log format means note.

Unfortunately most variable use supported in Apache config is for env
vars, not for notes, so you can't directly set the header from a note.

There are two things you can experiment with:

a) using an undocumented mod_rewrite feature to try to copy the note
into an env var and then using that env var to set the header

or

b) not using the normal JkMount or uriworkermap.properties way of
defining the workers responsible for handling the URIs, but instead
using mod_rewrite via setting the env var JK:WORKER_NAME

Ad a)

Works roughly like that (untested):

RewriteCond %{ENV:JK_WORKER_NAME} (.*)
RewriteRule . - [ENV=WORKER:%1]

Note 1: the undocumented feature of mod_rewrite is, that
%{ENV:JK_WORKER_NAME} first looks for a note named JK_WORKER_NAME and
only if it doesn't find it for an env var.

Note 2: The RewriteRule now sets a new env var WORKER to the captured
value of the note. lease choose a new variable name here, not
JK_WORER_NAME.

Now we add

Header add TC-Server-Ip %{WORKER}e

If you choose another name as WORKER for the new env var in the
RewriteRule, please adjust here as well.

Finally: if it doesn't work, try again by placing the Rewrite lines in a
Directory/Directory block. Don't forget to switch

RewriteEngine On

Ad b)

You can use mod_rewrite to set the env var JK_WORKER_NAME (now it is
important to use that name). mod_jk will then route the request to that
worker and since you had set the env var yourself, you can also copy it
to a header.

RewriteRule ^/c - [ENV=JK_WORKER_NAME:liferay]
RewriteRule ^/c/.* - [ENV=JK_WORKER_NAME:liferay]
RewriteRule ^/group - [ENV=JK_WORKER_NAME:liferay]
RewriteRule ^/group/.* - [ENV=JK_WORKER_NAME:liferay]

etc.

and then

Header add TC-Server-Ip %{JK_WORKER_NAME}e

Final remarks:

Your config does not really warrant this effort: you only have one
worker name, so what do you expect in the header? I'm asking, because if
you are using a load balancer worker (assumed name lb) in your real
config, and it has sub workers for example node1 and node2 then
JK_WORKER_NAME will always be lb. To actually get the chosen sub
worker, only recipe 1 has a chance to work. You would there replace
JK_WORJER_NAME in the RewriteCond by JK_WORKER_ROUTE. Unfortunately I
think that the route note is not set before the request actually gets
forwarded and that is to late for mod_rewrite to be able to copy it in
an env var.

In that case (load balancer and you want to know the chosen lb sub
worker) we would either need to add something to mod_jk, or allow
mod_headers to also support notes, or write a special small module.

Having written all that, I think the following patch to mod_headers
would be best. It simply adds support for notes to mod_headers (%{xxx}n
notation):

Index: modules/metadata/mod_headers.c
===
--- modules/metadata/mod_headers.c  (revision 1449529)
+++ modules/metadata/mod_headers.c  (working copy)
@@ -200,6 +200,16 @@
 return (null);
 }

+static const char *header_request_note(request_rec *r, char *a)
+{
+const char *s = apr_table_get(r-notes,a);
+
+if (s)
+return unwrap_header(r-pool, s);
+else
+return (null);
+}
+
 static const char *header_request_ssl_var(request_rec *r, char *name)
 {
 if (header_ssl_lookup) {
@@ -853,6 +863,7 @@

Re: Issue with Async Servlet onTimeout

2013-02-27 Thread Sumit Bhardwaj

Hi Chris,

Looks like tomcat 7.0.37 solve this issue.

One question though, I am seeing following error in catalina.out

*java.lang.IllegalStateException: Calling [asyncComplete()] is not valid
for a request with Async state [MUST_COMPLETE]*


do I need to handle something in my code??

Also are there any detailed examples of implementation of AsynListener?

Thanks,
Sumit

On Wed, Feb 27, 2013 at 11:52 AM, Sumit Bhardwaj
sumit.bhard...@gmail.comwrote:

 Sure Chris,

 would try with 7.0.37

 Thanks,
 Sumit


 On Wed, Feb 27, 2013 at 11:42 AM, Christopher Schultz 
 ch...@christopherschultz.net wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256

 Sunit,

 On 2/26/13 8:05 PM, Sumit Bhardwaj wrote:
  Hi,
 
  I am using AsyncContext for implementing a file download app and
  seeing issues on the timeout. I am using tomcat 7.0.23  (and have
  tried on 7.0.28 as well, but seeing the issue in 28 as well)

 Any chance of testing on 7.0.37, the current release? There have been
 a number of fixes to the async portions of Tomcat since 7.0.23/28,
 though none of the changelog descriptions jump out at me as being
 obviously relevant.

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

 iEYEAREIAAYFAlEto8oACgkQ9CaO5/Lv0PDX8gCfVG46d8YDTpKxEXEtqik1E17x
 w60AoKrQ8yOuSfsZ23lcKLsBLxk1igwW
 =P8HP
 -END PGP SIGNATURE-

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

Re: mod_jk how to add JK_WORKER_NAME to http-header

2013-02-27 Thread Rainer Jung

On 27.02.2013 09:59, André Warnier wrote:

 And from Schwaben too...
 I feel a bit naive after all the sophisticated technical stuff above, in
 suggesting the following, but how about :
 If I understand the original post correctly, the whole point would be to
 know, at the httpd level, which worker (Tomcat) actually processed
 this request, right ?
 If so, why not have the desired response header added at the Tomcat level ?
 The more or less standard workhorsse URLRewriteFilter could be used here
 for that.
 rule
 from.*/from
 set type=response-header name=TC-workername of this
 tomcat/set
 /rule
 and then check this on the way back in Apache..
 That would also overcome Rainer's note about load-balancing above.
 As a matter of fact, I am quite sure that Tomcat itself already adds
 some kind of response header to indicate that it was involved in this,
 so it might just be a matter of proper Tomcat configuration.

Much better :)

Rainer


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

Re: Tomcat 7 doesn't start on Windows

Hi again

Thanks for your answers. I have given up. I have tried some of the suggestions:

* Uninstall all JVM's and Tomcats (and reinstall)
* Checked dependcies, yes there were two, that are also present on another 
machine running Tomcat7 (TCP/IP, ADF)
* Tried to use client/jvm.dll instead of server/jvm.dll

Nothing helps - I can still only run the service from the command prompt. I 
find it strange though, that Tomcat isn't able to log anything at all about 
this, but maybe it's all Windows fault?

Hopefully things will work on a new VPS, and I'll quit the old one.

/Rune

Den 26/02/2013 kl. 13.04 skrev Rune Stilling s...@rdfined.dk:

 Hi list
 
 I have been trying to get this to work by looking a lot on similar situations 
 around the net but nothing works. My setup is as follows:
 
 * Tomcat 7.0.37 installed via the Windows service installer package
 * Windows 2003 server
 * Java/JRE 1.7.0_15
 * Using C:\Program Files\Java\jre7\bin\server\jvm.dll
 
 So the problem is that the Tomcat7 service won't start from the service 
 control panel. I just get a Could not start … and Error 1053: The service 
 did not respond ….
 
 There's nothing in the Tomcat logs (both stdout and stderr are empty). The 
 event logs shows a generic service control manager error.
 
 But - If I start the service from the command line by typing tomcat7 
 //TS/Tomcat7 the thing works fine.
 
 Also if I change the service user account to the Administrator account I 
 get a different error by startup Error 1068: The dependency service or group 
 failed to start.
 
 Any ideas?
 
 /Rune
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 


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

Re: mod_jk how to add JK_WORKER_NAME to http-header

2013-02-27 Thread Jochen Wißmann


On 27.02.2013 09:59, André Warnier wrote:

Rainer Jung wrote:

On 26.02.2013 19:41, Jochen Wißmann wrote:

Hello,

i am trying to find an easy way to determine from the http-client side,
which  AJP13-worker handled my request.
So my basic idea is to use mod_header to add mod_jk`s env-variable
JK_WORKER_NAME to the Header of the http-response.
I tried to get something like this working:

httpd.conf:
...
Header add TC-Server %{JK_WORKER_NAME}e
...

All my previous attempts resulted in http-responses looking like this:

 HTTP/1.1 200 OK
 Set-Cookie: ARPT=LRWQXVS110.160.11.26CKMLQ; path=/
 Date: Tue, 26 Feb 2013 18:25:31 GMT
 Server: Apache/2.2.22 (Unix) mod_jk/1.2.36 mod_ssl/2.2.22
OpenSSL/0.9.8x DAV/2
 Set-Cookie: JSESSIONID=A4052BF60BA2007F0B0F47E2699AFDE.liferay0; 
Path=/
 Set-Cookie: GUEST_LANGUAGE_ID=en_US; Expires=Wed, 26-Feb-2014 
18:25:31

GMT; Path=/
 Set-Cookie: COOKIE_SUPPORT=true; Expires=Wed, 26-Feb-2014 18:25:31
GMT; Path=/
 Liferay-Portal: Liferay Portal Community Edition 6.0.6 CE (Bunyan /
Build 6006 / February 17, 2011)
 ETag: 838b4ae2
 Content-Length: 8043
 X-Server-Ip: 110.160.11.26
 TC-Server: (null)
 Content-Type: text/html;charset=utf-8

Why do i get TC-Server: (null) ?
Using the Variable JK_WORKER_NAME to log the worker's name via
mod_log_config works fine.

Am i missing something? Is it even possible to access the env-variable
JK_WORKER_NAME with module mod_header?
Could anyone please help?
Thanks!


mod_jk respects the environment variable JK_WORKER_NAME when choosing a
target worker, but it does not set it.

mod_jk only sets a note with name JK_WORKER_NAME, which is different
from an env var. The n in your log format means note.

Unfortunately most variable use supported in Apache config is for env
vars, not for notes, so you can't directly set the header from a note.

There are two things you can experiment with:

a) using an undocumented mod_rewrite feature to try to copy the note
into an env var and then using that env var to set the header

or

b) not using the normal JkMount or uriworkermap.properties way of
defining the workers responsible for handling the URIs, but instead
using mod_rewrite via setting the env var JK:WORKER_NAME

Ad a)

Works roughly like that (untested):

RewriteCond %{ENV:JK_WORKER_NAME} (.*)
RewriteRule . - [ENV=WORKER:%1]

Note 1: the undocumented feature of mod_rewrite is, that
%{ENV:JK_WORKER_NAME} first looks for a note named JK_WORKER_NAME and
only if it doesn't find it for an env var.

Note 2: The RewriteRule now sets a new env var WORKER to the captured
value of the note. lease choose a new variable name here, not
JK_WORER_NAME.

Now we add

Header add TC-Server-Ip %{WORKER}e

If you choose another name as WORKER for the new env var in the
RewriteRule, please adjust here as well.

Finally: if it doesn't work, try again by placing the Rewrite lines in a
Directory/Directory block. Don't forget to switch

RewriteEngine On

Ad b)

You can use mod_rewrite to set the env var JK_WORKER_NAME (now it is
important to use that name). mod_jk will then route the request to that
worker and since you had set the env var yourself, you can also copy it
to a header.

RewriteRule ^/c - [ENV=JK_WORKER_NAME:liferay]
RewriteRule ^/c/.* - [ENV=JK_WORKER_NAME:liferay]
RewriteRule ^/group - [ENV=JK_WORKER_NAME:liferay]
RewriteRule ^/group/.* - [ENV=JK_WORKER_NAME:liferay]

etc.

and then

Header add TC-Server-Ip %{JK_WORKER_NAME}e

Final remarks:

Your config does not really warrant this effort: you only have one
worker name, so what do you expect in the header? I'm asking, because if
you are using a load balancer worker (assumed name lb) in your real
config, and it has sub workers for example node1 and node2 then
JK_WORKER_NAME will always be lb. To actually get the chosen sub
worker, only recipe 1 has a chance to work. You would there replace
JK_WORJER_NAME in the RewriteCond by JK_WORKER_ROUTE. Unfortunately I
think that the route note is not set before the request actually gets
forwarded and that is to late for mod_rewrite to be able to copy it in
an env var.

In that case (load balancer and you want to know the chosen lb sub
worker) we would either need to add something to mod_jk, or allow
mod_headers to also support notes, or write a special small module.

Having written all that, I think the following patch to mod_headers
would be best. It simply adds support for notes to mod_headers (%{xxx}n
notation):

Index: modules/metadata/mod_headers.c
===
--- modules/metadata/mod_headers.c  (revision 1449529)
+++ modules/metadata/mod_headers.c  (working copy)
@@ -200,6 +200,16 @@
 return (null);
 }

+static const char *header_request_note(request_rec *r, char *a)
+{
+const char *s = apr_table_get(r-notes,a);
+
+if (s)
+return unwrap_header(r-pool, s);
+else
+return (null);
+}
+
 static const char *header_request_ssl_var(request_rec *r, char *name)
 {
 if

Re: mod_jk how to add JK_WORKER_NAME to http-header


Jochen Wißmann wrote:

On 27.02.2013 09:59, André Warnier wrote:

Rainer Jung wrote:

On 26.02.2013 19:41, Jochen Wißmann wrote:

Hello,

i am trying to find an easy way to determine from the http-client side,
which  AJP13-worker handled my request.
So my basic idea is to use mod_header to add mod_jk`s env-variable
JK_WORKER_NAME to the Header of the http-response.
I tried to get something like this working:

httpd.conf:
...
Header add TC-Server %{JK_WORKER_NAME}e
...

All my previous attempts resulted in http-responses looking like this:

 HTTP/1.1 200 OK
 Set-Cookie: ARPT=LRWQXVS110.160.11.26CKMLQ; path=/
 Date: Tue, 26 Feb 2013 18:25:31 GMT
 Server: Apache/2.2.22 (Unix) mod_jk/1.2.36 mod_ssl/2.2.22
OpenSSL/0.9.8x DAV/2
 Set-Cookie: JSESSIONID=A4052BF60BA2007F0B0F47E2699AFDE.liferay0; 
Path=/
 Set-Cookie: GUEST_LANGUAGE_ID=en_US; Expires=Wed, 26-Feb-2014 
18:25:31

GMT; Path=/
 Set-Cookie: COOKIE_SUPPORT=true; Expires=Wed, 26-Feb-2014 18:25:31
GMT; Path=/
 Liferay-Portal: Liferay Portal Community Edition 6.0.6 CE (Bunyan /
Build 6006 / February 17, 2011)
 ETag: 838b4ae2
 Content-Length: 8043
 X-Server-Ip: 110.160.11.26
 TC-Server: (null)
 Content-Type: text/html;charset=utf-8

Why do i get TC-Server: (null) ?
Using the Variable JK_WORKER_NAME to log the worker's name via
mod_log_config works fine.

Am i missing something? Is it even possible to access the env-variable
JK_WORKER_NAME with module mod_header?
Could anyone please help?
Thanks!


mod_jk respects the environment variable JK_WORKER_NAME when choosing a
target worker, but it does not set it.

mod_jk only sets a note with name JK_WORKER_NAME, which is different
from an env var. The n in your log format means note.

Unfortunately most variable use supported in Apache config is for env
vars, not for notes, so you can't directly set the header from a note.

There are two things you can experiment with:

a) using an undocumented mod_rewrite feature to try to copy the note
into an env var and then using that env var to set the header

or

b) not using the normal JkMount or uriworkermap.properties way of
defining the workers responsible for handling the URIs, but instead
using mod_rewrite via setting the env var JK:WORKER_NAME

Ad a)

Works roughly like that (untested):

RewriteCond %{ENV:JK_WORKER_NAME} (.*)
RewriteRule . - [ENV=WORKER:%1]

Note 1: the undocumented feature of mod_rewrite is, that
%{ENV:JK_WORKER_NAME} first looks for a note named JK_WORKER_NAME and
only if it doesn't find it for an env var.

Note 2: The RewriteRule now sets a new env var WORKER to the captured
value of the note. lease choose a new variable name here, not
JK_WORER_NAME.

Now we add

Header add TC-Server-Ip %{WORKER}e

If you choose another name as WORKER for the new env var in the
RewriteRule, please adjust here as well.

Finally: if it doesn't work, try again by placing the Rewrite lines in a
Directory/Directory block. Don't forget to switch

RewriteEngine On

Ad b)

You can use mod_rewrite to set the env var JK_WORKER_NAME (now it is
important to use that name). mod_jk will then route the request to that
worker and since you had set the env var yourself, you can also copy it
to a header.

RewriteRule ^/c - [ENV=JK_WORKER_NAME:liferay]
RewriteRule ^/c/.* - [ENV=JK_WORKER_NAME:liferay]
RewriteRule ^/group - [ENV=JK_WORKER_NAME:liferay]
RewriteRule ^/group/.* - [ENV=JK_WORKER_NAME:liferay]

etc.

and then

Header add TC-Server-Ip %{JK_WORKER_NAME}e

Final remarks:

Your config does not really warrant this effort: you only have one
worker name, so what do you expect in the header? I'm asking, because if
you are using a load balancer worker (assumed name lb) in your real
config, and it has sub workers for example node1 and node2 then
JK_WORKER_NAME will always be lb. To actually get the chosen sub
worker, only recipe 1 has a chance to work. You would there replace
JK_WORJER_NAME in the RewriteCond by JK_WORKER_ROUTE. Unfortunately I
think that the route note is not set before the request actually gets
forwarded and that is to late for mod_rewrite to be able to copy it in
an env var.

In that case (load balancer and you want to know the chosen lb sub
worker) we would either need to add something to mod_jk, or allow
mod_headers to also support notes, or write a special small module.

Having written all that, I think the following patch to mod_headers
would be best. It simply adds support for notes to mod_headers (%{xxx}n
notation):

Index: modules/metadata/mod_headers.c
===
--- modules/metadata/mod_headers.c  (revision 1449529)
+++ modules/metadata/mod_headers.c  (working copy)
@@ -200,6 +200,16 @@
 return (null);
 }

+static const char *header_request_note(request_rec *r, char *a)
+{
+const char *s = apr_table_get(r-notes,a);
+
+if (s)
+return unwrap_header(r-pool, s);
+else
+return (null);
+}
+
 static const char *header_request_ssl_var(request_rec *r, char *name)

Re: Tomcat 7 doesn't start on Windows

On Wed, Feb 27, 2013 at 6:37 AM, computer repair centre 
computer.support.cen...@googlemail.com wrote:


 Please can you provide the value of the JAVA_HOME environment variable?


Excellent question. That question has been wondering in my mind since
yesterday, since Rune stated following in 2 separate emails:

* Using C:\Program Files\Java\jre7\bin\server\jvm.dll
* Tried to use client/jvm.dll instead of server/jvm.dll

Also, might check PATH. I really hope 'multiple' JVMs are not included in
the Windows system PATH as well. It is very common for Windows users to
just append 'stuff' on to Windows system PATH variable, and may forget to
update/remove obsolete 'stuff' from the PATH variable. When I update to
latest Java 7 version, it is always standard procedure for me to make sure
I update JAVA_HOME and PATH.

tomcat-7.0.35 ON Window Server SP 2

2013-02-27 Thread dkumar

Hi,

I have downloaded apache-tomcat-7.0.35.zip and runiing it on Window Server 
SP 2 machine and it is working fine. 
Is it OK to run apache-tomcat-7.0.35 setup on Window Server SP 2 machine? 

Please reply.

Server version: Apache Tomcat/7.0.35
OS Name:Windows Server SP 2  32 bit


Thanks and Regards
Deepak Kumar
Disclaimer and confidentiality clause -
 This message and any attachments relating to official business of CCIL OR ANY 
OF IT'S SUBSIDIARIES is proprietary to CCIL and intended for the original 
addressee only.
The message may contain information that is confidential and subject to legal 
privilege. 
Any views expressed in this message are those of the individual sender. 
If you have received this message in error, please notify the original sender 
immediately and destroy the message and copies thereof and any attachments 
contained in it .
 If you are not the intended recipient of this message, you are hereby notified 
that you must not disseminate, copy, use, distribute, or take any action in 
connection therewith. 
 CCIL cannot ensure that the integrity of this communication has been 
maintained nor that it is free of errors, viruses, interception and/or 
interference. 
CCIL is not liable whatsoever for loss or damage resulting from the opening of 
this message and/or attachments and/or the use of the information contained in 
this message and/or attachments.

Re: Tomcat 7 doesn't start on Windows


computer repair centre wrote:

On Wed, Feb 27, 2013 at 10:18 AM, Rune Stilling s...@rdfined.dk wrote:

Hi again

Thanks for your answers. I have given up. I have tried some of the suggestions:

* Uninstall all JVM's and Tomcats (and reinstall)
* Checked dependcies, yes there were two, that are also present on another 
machine running Tomcat7 (TCP/IP, ADF)
* Tried to use client/jvm.dll instead of server/jvm.dll

Nothing helps - I can still only run the service from the command prompt. I 
find it strange though, that Tomcat isn't able to log anything at all about 
this, but maybe it's all Windows fault?

Hopefully things will work on a new VPS, and I'll quit the old one.

/Rune

Den 26/02/2013 kl. 13.04 skrev Rune Stilling s...@rdfined.dk:



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




Hi Rune,

Please can you provide the value of the JAVA_HOME environment variable?



That has nothing to do with the matter. The wrapper (tomcat7.exe) takes the path of the 
JVM to run from the Registry, not from environment variables.

Run tomcat7w.exe and check the Java tab.

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

Re: Tomcat 7 doesn't start on Windows

2013-02-27 Thread Giles

On 27 February 2013 11:52, André Warnier a...@ice-sa.com wrote:
 computer repair centre wrote:

 On Wed, Feb 27, 2013 at 10:18 AM, Rune Stilling s...@rdfined.dk wrote:

 Hi again

 Thanks for your answers. I have given up. I have tried some of the
 suggestions:

 * Uninstall all JVM's and Tomcats (and reinstall)
 * Checked dependcies, yes there were two, that are also present on
 another machine running Tomcat7 (TCP/IP, ADF)
 * Tried to use client/jvm.dll instead of server/jvm.dll

 Nothing helps - I can still only run the service from the command prompt.
 I find it strange though, that Tomcat isn't able to log anything at all
 about this, but maybe it's all Windows fault?

 Hopefully things will work on a new VPS, and I'll quit the old one.

 /Rune

 Den 26/02/2013 kl. 13.04 skrev Rune Stilling s...@rdfined.dk:



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



 Hi Rune,

 Please can you provide the value of the JAVA_HOME environment variable?


 That has nothing to do with the matter. The wrapper (tomcat7.exe) takes the
 path of the JVM to run from the Registry, not from environment variables.
 Run tomcat7w.exe and check the Java tab.

But it is used by service.bat when installing the service. This issue
could be caused by using the 64-bit installation with the 32-bit JVM.
This would explain why calling the wrapper directly from the command
line does execute successfully.

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

Re: Tomcat 7 doesn't start on Windows

Ok - So I did:

* uninstall Tomcat
* only one jvm present on the system (64 bit)
* setting CATALINA_HOME, JAVA_HOME and JRE_HOME:

CATALINA_HOME=C:\Progra~1\APACHE~1\TOMCAT~1.0
JAVA_HOME=C:\Progra~1\Java
JRE_HOME=C:\Progra~1\Java\jre7

* restarting server
* reinstalling Tomcat7 (using the service installer, not the service.bat file, 
that I can't locate anyway)
* checking Java Virtual Machine in Java tab in Tomcat7w.exe:

C:\Program Files\Java\jre7\bin\server\jvm.dll

* checking PATH:

Path=C:\PARALL~1\Plesk\ADDITI~1\Perl\bin\;C:\Parallels\Plesk\Additional\Python\;C:\Parallels\Plesk\Mail
 Servers\Mail 
Enable\BIN;C:\PARALL~1\Plesk\ADDITI~1\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program
 Files\TortoiseSVN\bin;C:\Program Files (x86)\MySQL\MySQL 
Server5.5\bin;C:\Program Files(x86)\IDM Computer Solutions\UltraEdit\

But - Problem persists.

Is there some registry key I could check related to the installation process?

\Rune

Den 27/02/2013 kl. 12.57 skrev Giles computer.support.cen...@googlemail.com:

 On 27 February 2013 11:52, André Warnier a...@ice-sa.com wrote:
 computer repair centre wrote:
 
 On Wed, Feb 27, 2013 at 10:18 AM, Rune Stilling s...@rdfined.dk wrote:
 
 Hi again
 
 Thanks for your answers. I have given up. I have tried some of the
 suggestions:
 
 * Uninstall all JVM's and Tomcats (and reinstall)
 * Checked dependcies, yes there were two, that are also present on
 another machine running Tomcat7 (TCP/IP, ADF)
 * Tried to use client/jvm.dll instead of server/jvm.dll
 
 Nothing helps - I can still only run the service from the command prompt.
 I find it strange though, that Tomcat isn't able to log anything at all
 about this, but maybe it's all Windows fault?
 
 Hopefully things will work on a new VPS, and I'll quit the old one.
 
 /Rune
 
 Den 26/02/2013 kl. 13.04 skrev Rune Stilling s...@rdfined.dk:
 
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 
 
 
 Hi Rune,
 
 Please can you provide the value of the JAVA_HOME environment variable?
 
 
 That has nothing to do with the matter. The wrapper (tomcat7.exe) takes the
 path of the JVM to run from the Registry, not from environment variables.
 Run tomcat7w.exe and check the Java tab.
 
 But it is used by service.bat when installing the service. This issue
 could be caused by using the 64-bit installation with the 32-bit JVM.
 This would explain why calling the wrapper directly from the command
 line does execute successfully.
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 


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

Re: Tomcat 7 doesn't start on Windows

On Wed, Feb 27, 2013 at 7:11 AM, Rune Stilling s...@rdfined.dk wrote:

 Ok - So I did:

 CATALINA_HOME=C:\Progra~1\APACHE~1\TOMCAT~1.0

 * reinstalling Tomcat7 (using the service installer, not the service.bat
 file, that I can't locate anyway)
 * checking Java Virtual Machine in Java tab in Tomcat7w.exe:


TOMCAT~1.0 ? interesting, never seen a tomcat7 install to folder like that.
See [1] below.

using the service installer = 'sc ...' at command prompt? you cannot locate
service.bat file (in C:\Progra~1\APACHE~1\TOMCAT~1.0)? wow/interesting. I
repeat, see [1] below.


[1] I download .zip file and extract to D:\ root folder, and it should
extract files to D:\apache-tomcat-7.0.37 (or whatever version you are
using). I would 'never' install Tomcat to C:\Program Files or D:\Program
Files.

Re: Tomcat 7 doesn't start on Windows


Giles wrote:

On 27 February 2013 11:52, André Warnier a...@ice-sa.com wrote:

computer repair centre wrote:

On Wed, Feb 27, 2013 at 10:18 AM, Rune Stilling s...@rdfined.dk wrote:

Hi again

Thanks for your answers. I have given up. I have tried some of the
suggestions:

* Uninstall all JVM's and Tomcats (and reinstall)
* Checked dependcies, yes there were two, that are also present on
another machine running Tomcat7 (TCP/IP, ADF)
* Tried to use client/jvm.dll instead of server/jvm.dll

Nothing helps - I can still only run the service from the command prompt.
I find it strange though, that Tomcat isn't able to log anything at all
about this, but maybe it's all Windows fault?

Hopefully things will work on a new VPS, and I'll quit the old one.

/Rune

Den 26/02/2013 kl. 13.04 skrev Rune Stilling s...@rdfined.dk:



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



Hi Rune,

Please can you provide the value of the JAVA_HOME environment variable?


That has nothing to do with the matter. The wrapper (tomcat7.exe) takes the
path of the JVM to run from the Registry, not from environment variables.
Run tomcat7w.exe and check the Java tab.


But it is used by service.bat when installing the service. This issue
could be caused by using the 64-bit installation with the 32-bit JVM.
This would explain why calling the wrapper directly from the command
line does execute successfully.



I believe that the above statement is false.
Whether you run the command
tomcat7 //TS/Tomcat7
from a command-line window, or you let the Windows Service Manager run the same command, 
does not change the fact that tomcat7(.exe) takes its parameters from the same place in 
the Registry.
So if it works one way, and not the other, it is not because of that Registry setting nor 
bacause the JAVA_HOME environment variable.



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

Re: Tomcat 7 doesn't start on Windows

On Wed, Feb 27, 2013 at 7:34 AM, Howard W. Smith, Jr. 
smithh032...@gmail.com wrote:

 On Wed, Feb 27, 2013 at 7:11 AM, Rune Stilling s...@rdfined.dk wrote:

 Ok - So I did:

 CATALINA_HOME=C:\Progra~1\APACHE~1\TOMCAT~1.0


 * reinstalling Tomcat7 (using the service installer, not the service.bat
 file, that I can't locate anyway)
 * checking Java Virtual Machine in Java tab in Tomcat7w.exe:


 TOMCAT~1.0 ? interesting, never seen a tomcat7 install to folder like
 that. See [1] below.

 using the service installer = 'sc ...' at command prompt? you cannot
 locate service.bat file (in C:\Progra~1\APACHE~1\TOMCAT~1.0)?
 wow/interesting. I repeat, see [1] below.


 [1] I download .zip file and extract to D:\ root folder, and it should
 extract files to D:\apache-tomcat-7.0.37 (or whatever version you are
 using). I would 'never' install Tomcat to C:\Program Files or D:\Program
 Files.


Add to [1] above... service.bat is located in D:\apache-tomcat-7.0.37\bin,
after extracting 'all' files from the .zip file, and if 'Use folder names'
was checked/selected prior to extracting files via WinZip.

Re: Tomcat 7 doesn't start on Windows

As I wrote I'm using the service installer 32-bit/64-bit Windows Service 
Installer. This is an exe file and not a zip-archive.

Regarding the paths - I have used windows short paths to avoid eventual 
troubles with spaces in path names.

\Rune

Den 27/02/2013 kl. 13.54 skrev Howard W. Smith, Jr. smithh032...@gmail.com:

 On Wed, Feb 27, 2013 at 7:34 AM, Howard W. Smith, Jr. 
 smithh032...@gmail.com wrote:
 
 On Wed, Feb 27, 2013 at 7:11 AM, Rune Stilling s...@rdfined.dk wrote:
 
 Ok - So I did:
 
 CATALINA_HOME=C:\Progra~1\APACHE~1\TOMCAT~1.0
 
 
 * reinstalling Tomcat7 (using the service installer, not the service.bat
 file, that I can't locate anyway)
 * checking Java Virtual Machine in Java tab in Tomcat7w.exe:
 
 
 TOMCAT~1.0 ? interesting, never seen a tomcat7 install to folder like
 that. See [1] below.
 
 using the service installer = 'sc ...' at command prompt? you cannot
 locate service.bat file (in C:\Progra~1\APACHE~1\TOMCAT~1.0)?
 wow/interesting. I repeat, see [1] below.
 
 
 [1] I download .zip file and extract to D:\ root folder, and it should
 extract files to D:\apache-tomcat-7.0.37 (or whatever version you are
 using). I would 'never' install Tomcat to C:\Program Files or D:\Program
 Files.
 
 
 Add to [1] above... service.bat is located in D:\apache-tomcat-7.0.37\bin,
 after extracting 'all' files from the .zip file, and if 'Use folder names'
 was checked/selected prior to extracting files via WinZip.


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

Re: Tomcat 7 doesn't start on Windows

And BTW - I have several running Tomcat7-instances on other servers that run in 
Program Files-folders.

\Rune

Den 27/02/2013 kl. 13.54 skrev Howard W. Smith, Jr. smithh032...@gmail.com:

 On Wed, Feb 27, 2013 at 7:34 AM, Howard W. Smith, Jr. 
 smithh032...@gmail.com wrote:
 
 On Wed, Feb 27, 2013 at 7:11 AM, Rune Stilling s...@rdfined.dk wrote:
 
 Ok - So I did:
 
 CATALINA_HOME=C:\Progra~1\APACHE~1\TOMCAT~1.0
 
 
 * reinstalling Tomcat7 (using the service installer, not the service.bat
 file, that I can't locate anyway)
 * checking Java Virtual Machine in Java tab in Tomcat7w.exe:
 
 
 TOMCAT~1.0 ? interesting, never seen a tomcat7 install to folder like
 that. See [1] below.
 
 using the service installer = 'sc ...' at command prompt? you cannot
 locate service.bat file (in C:\Progra~1\APACHE~1\TOMCAT~1.0)?
 wow/interesting. I repeat, see [1] below.
 
 
 [1] I download .zip file and extract to D:\ root folder, and it should
 extract files to D:\apache-tomcat-7.0.37 (or whatever version you are
 using). I would 'never' install Tomcat to C:\Program Files or D:\Program
 Files.
 
 
 Add to [1] above... service.bat is located in D:\apache-tomcat-7.0.37\bin,
 after extracting 'all' files from the .zip file, and if 'Use folder names'
 was checked/selected prior to extracting files via WinZip.


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

Re: Tomcat 7 doesn't start on Windows


 As I wrote I'm using the service installer 32-bit/64-bit Windows Service
 Installer. This is an exe file and not a zip-archive.

 Regarding the paths - I have used windows short paths to avoid eventual
 troubles with spaces in path names.


And BTW - I have several running Tomcat7-instances on other servers that
 run in Program Files-folders.


Understood all 3 points and with that, I digress. I already shared what
works best (and is reliable) for me. :)

Re: Tomcat 7 doesn't start on Windows

Rune Stilling wrote:

Is there some registry key I could check related to the installation process?

Call up the Registry Editor, and search for tomcat7.

You should find essentially 2 places :

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7
(under this one, you will find the parameters which Windows needs to know about the
service (such as, how to start it) (it being tomcat7.exe)

HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\
(under this one, you will find the parameters which tomcat7.exe (the service wrapper)
needs to know (such as, which JVM to start and with which parameters)

(and remember, tomcat7.exe is a renamed prunsrv.exe, which is one of the 2 modules that
are part of procrun).

Let's step back a bit.

1) you install Tomcat on the machine, using the Windows installer package from
tomcat.apache.org.

2) this installer creates the Registry value :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\ImagePath =
C:\apache-tomcat-\bin\tomcat7.exe //RS//Tomcat7

(or similar)
This Registry value is the one that will be used by the Windows Service Manager, to know
which program to launch when you click on Services.. Tomcat7...start.

3) when you login as a user onto the machine, open a command window, and run the above
command (C:\apache-tomcat-\bin\tomcat7.exe //RS//Tomcat7), the tomcat7.exe program
runs, and starts a JVM which starts Tomcat, as a Service.

And that works fine, tomcat logs are produced etc.

4) when instead, you open the Windows Service Manager dialog, and ask Windows to start the
Tomcat service, nothing happens.

(Tomcat does not start, tomcat7.exe does not run, no logs are produced etc.)

So the intuitive conclusions would be :
- there is nothing wrong with Tomcat per se. Otherwise, it would not run, no matter how
it is started. There is also nothing wrong with the JVM, for the same reasons.
- there is nothing wrong with the Registry parameters of tomcat7.exe (the ones found
under HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation). Otherwise, in case (3)
above, tomcat7.exe would not be able to start the JVM etc..

So there must be something wrong with the parameters used by the Windows Service Manager
when it tries to start the Tomcat service. (The ones under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\)

What that would be, I couldn't say, and certainly not without access to your
Registry.

But what I would do at this stage is this :

1) de-install Tomcat again (do not delete the installer.exe file that you downloaded,
you'll need it again)
2) using the Registry Editor (carefully), go to the key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\, and delete it (and
everything under it).

3) reboot Windows, and with the Registry Editor, verify that the key is still
deleted
(I am saying that because who knows what MS will have invented yet to re-instate things
that you deleted..)

4) re-install the Tomcat service by re-running the installer
5) try again to start Tomcat

and tell us what happens.

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

Re: Tomcat 7 doesn't start on Windows

Hi André

Thanks for an excellent summary. There's one thing that I haven't been precise 
enough about I can see.

I CANNOT run Tomcat via the RS-parameter:

Tomcat7.exe //RS/Tomcat7

If I try the log produces the following:

[2013-02-27 14:33:55] [info]  [548184] Commons Daemon procrun (1.0.13.0 64-bit) 
started
[2013-02-27 14:33:55] [info]  [548184] Running 'Tomcat7' Service...
[2013-02-27 14:33:55] [error] [548184] StartServiceCtrlDispatcher for 'Tomcat7' 
failed
[2013-02-27 14:33:55] [error] [548184] The service process could not connect to 
the service controller.
[2013-02-27 14:33:55] [error] [548184] Commons Daemon procrun failed with exit 
value: 4 (Failed to run service)
[2013-02-27 14:33:55] [error] [548184] The service process could not connect to 
the service controller.

What I CAN do is to run it via the TS-parameter:

Tomcat7.exe //TS/Tomcat7

But - I'll try what you suggested anyways.

/Rune

Den 27/02/2013 kl. 14.20 skrev André Warnier a...@ice-sa.com:

 Rune Stilling wrote:
 Is there some registry key I could check related to the installation process?
 Call up the Registry Editor, and search for tomcat7.
 
 You should find essentially 2 places :
 
 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7
 (under this one, you will find the parameters which Windows needs to know 
 about the service (such as, how to start it) (it being tomcat7.exe)
 
 HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\
 (under this one, you will find the parameters which tomcat7.exe (the 
 service wrapper) needs to know (such as, which JVM to start and with which 
 parameters)
 
 (and remember, tomcat7.exe is a renamed prunsrv.exe, which is one of the 2 
 modules that are part of procrun).
 
 --
 
 Let's step back a bit.
 
 1) you install Tomcat on the machine, using the Windows installer package 
 from tomcat.apache.org.
 
 2) this installer creates the Registry value :
 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\ImagePath = 
 C:\apache-tomcat-\bin\tomcat7.exe //RS//Tomcat7
 (or similar)
 This Registry value is the one that will be used by the Windows Service 
 Manager, to know which program to launch when you click on Services.. 
 Tomcat7...start.
 
 3) when you login as a user onto the machine, open a command window, and run 
 the above command (C:\apache-tomcat-\bin\tomcat7.exe //RS//Tomcat7), 
 the tomcat7.exe program runs, and starts a JVM which starts Tomcat, as a 
 Service.
 And that works fine, tomcat logs are produced etc.
 
 4) when instead, you open the Windows Service Manager dialog, and ask Windows 
 to start the Tomcat service, nothing happens.
 (Tomcat does not start, tomcat7.exe does not run, no logs are produced etc.)
 
 So the intuitive conclusions would be :
 - there is nothing wrong with Tomcat per se.  Otherwise, it would not run, no 
 matter how it is started.  There is also nothing wrong with the JVM, for the 
 same reasons.
 - there is nothing wrong with the Registry parameters of tomcat7.exe (the 
 ones found under HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation).  
 Otherwise, in case (3) above, tomcat7.exe would not be able to start the JVM 
 etc..
 
 So there must be something wrong with the parameters used by the Windows 
 Service Manager when it tries to start the Tomcat service. (The ones under 
 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\)
 
 What that would be, I couldn't say, and certainly not without access to your 
 Registry.
 
 But what I would do at this stage is this :
 
 1) de-install Tomcat again (do not delete the installer.exe file that you 
 downloaded, you'll need it again)
 2) using the Registry Editor (carefully), go to the key 
 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\, and delete it 
 (and everything under it).
 3) reboot Windows, and with the Registry Editor, verify that the key is still 
 deleted
 (I am saying that because who knows what MS will have invented yet to 
 re-instate things that you deleted..)
 4) re-install the Tomcat service by re-running the installer
 5) try again to start Tomcat
 
 and tell us what happens.
 
 
 
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 


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

RE: Tomcat 7 doesn't start on Windows

2013-02-27 Thread Harris, Jeffrey E.

 -Original Message-
 From: André Warnier [mailto:a...@ice-sa.com]
 Sent: Wednesday, February 27, 2013 8:20 AM
 To: Tomcat Users List
 Subject: Re: Tomcat 7 doesn't start on Windows

 Rune Stilling wrote:

  Is there some registry key I could check related to the installation
 process?

 Call up the Registry Editor, and search for tomcat7.

 You should find essentially 2 places :

 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7
 (under this one, you will find the parameters which Windows needs to
 know about the service (such as, how to start it) (it being
 tomcat7.exe)

 HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\
 (under this one, you will find the parameters which tomcat7.exe (the
 service wrapper) needs to know (such as, which JVM to start and with
 which parameters)

 (and remember, tomcat7.exe is a renamed prunsrv.exe, which is one of
 the 2 modules that are part of procrun).

 --

 Let's step back a bit.

 1) you install Tomcat on the machine, using the Windows installer
 package from tomcat.apache.org.

 2) this installer creates the Registry value :
 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\ImagePath
 = C:\apache-tomcat-\bin\tomcat7.exe //RS//Tomcat7
 (or similar)
 This Registry value is the one that will be used by the Windows Service
 Manager, to know which program to launch when you click on Services..
 Tomcat7...start.

 3) when you login as a user onto the machine, open a command window,
 and run the above command (C:\apache-tomcat-\bin\tomcat7.exe
 //RS//Tomcat7), the tomcat7.exe program runs, and starts a JVM which
 starts Tomcat, as a Service.
 And that works fine, tomcat logs are produced etc.

 4) when instead, you open the Windows Service Manager dialog, and ask
 Windows to start the Tomcat service, nothing happens.
 (Tomcat does not start, tomcat7.exe does not run, no logs are produced
 etc.)

 So the intuitive conclusions would be :
 - there is nothing wrong with Tomcat per se.  Otherwise, it would not
 run, no matter how it is started.  There is also nothing wrong with the
 JVM, for the same reasons.
 - there is nothing wrong with the Registry parameters of tomcat7.exe
 (the ones found under HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software
 Foundation).  Otherwise, in case (3) above, tomcat7.exe would not be
 able to start the JVM etc..

 So there must be something wrong with the parameters used by the
 Windows Service Manager when it tries to start the Tomcat service. (The
 ones under
 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\)

 What that would be, I couldn't say, and certainly not without access to
 your Registry.

 But what I would do at this stage is this :

 1) de-install Tomcat again (do not delete the installer.exe file that
 you downloaded, you'll need it again)
 2) using the Registry Editor (carefully), go to the key
 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\, and
 delete it (and everything under it).
 3) reboot Windows, and with the Registry Editor, verify that the key is
 still deleted (I am saying that because who knows what MS will have
 invented yet to re-instate things that you deleted..)
 4) re-install the Tomcat service by re-running the installer
 5) try again to start Tomcat

 and tell us what happens.

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

You might also want to download process monitor (not process explorer) from 
live.sysinternals.com, and have that running when you try and start the 
service.  Filter out unrelated processes (explorer, iexplorer, csrss, etc.) and 
look for results that are not success (although if you actually filter on 
result is not success, you will probably see some false indicators, for 
example, Windows looks in the local directory and the Path for system DLLs, and 
will report a failure finding them until it does find them in the 
%windir%\system32 folder).  Generally, the fatal errors occur towards the end 
of the run history of the applicable process.

Have you looked in Event Viewer for any additional error messages in the System 
or Application logs?  Increased Tomcat logging to try and identify the source 
of the problem?  I know you have used the command line, but if you start the 
Tomcat monitor (tomcatw.exe) and start the service from the monitor in the 
system tray, does that work?

Finally, do you have any unusual restrictions on your server?  Are any other 
services failing to start?  Based on your last posting, I would guess that it 
is a permissions issue.  Does the system account have full permissions on the 
Tomcat directory?

This e-mail and any attachments are intended only for the use of the 
addressee(s) named herein and may contain proprietary information. If you are 
not the intended recipient of this e-mail or believe that you received

Re: Tomcat 7 doesn't start on Windows

Problem solved!!

Ah finally :) I did as you suggested below and it didn't help, but then I 
looked a bit on the registry values. I found that the ImagePath key looked a 
bit strange. It contained the following value:

C:\Program Files\Apache Software Foundation\Tomcat 7.0\bin\Tomcat7.exe 
ogs\commons-daemon.2013-02-27.log//RS//Tomcat7

I tried to replace it with:

C:\Program Files\Apache Software Foundation\Tomcat 7.0\bin\Tomcat7.exe 
//RS//Tomcat7

And voliá the service would start.

I have no idea where the ogs\commons-daemon.2013-02-27.log comes from, but it 
must be something the installer added, and for some reason the service won't 
start using this value?

Thanks for all the help,
Rune

Den 27/02/2013 kl. 14.20 skrev André Warnier a...@ice-sa.com:

 Rune Stilling wrote:
 Is there some registry key I could check related to the installation process?
 Call up the Registry Editor, and search for tomcat7.
 
 You should find essentially 2 places :
 
 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7
 (under this one, you will find the parameters which Windows needs to know 
 about the service (such as, how to start it) (it being tomcat7.exe)
 
 HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\
 (under this one, you will find the parameters which tomcat7.exe (the 
 service wrapper) needs to know (such as, which JVM to start and with which 
 parameters)
 
 (and remember, tomcat7.exe is a renamed prunsrv.exe, which is one of the 2 
 modules that are part of procrun).
 
 --
 
 Let's step back a bit.
 
 1) you install Tomcat on the machine, using the Windows installer package 
 from tomcat.apache.org.
 
 2) this installer creates the Registry value :
 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\ImagePath = 
 C:\apache-tomcat-\bin\tomcat7.exe //RS//Tomcat7
 (or similar)
 This Registry value is the one that will be used by the Windows Service 
 Manager, to know which program to launch when you click on Services.. 
 Tomcat7...start.
 
 3) when you login as a user onto the machine, open a command window, and run 
 the above command (C:\apache-tomcat-\bin\tomcat7.exe //RS//Tomcat7), 
 the tomcat7.exe program runs, and starts a JVM which starts Tomcat, as a 
 Service.
 And that works fine, tomcat logs are produced etc.
 
 4) when instead, you open the Windows Service Manager dialog, and ask Windows 
 to start the Tomcat service, nothing happens.
 (Tomcat does not start, tomcat7.exe does not run, no logs are produced etc.)
 
 So the intuitive conclusions would be :
 - there is nothing wrong with Tomcat per se.  Otherwise, it would not run, no 
 matter how it is started.  There is also nothing wrong with the JVM, for the 
 same reasons.
 - there is nothing wrong with the Registry parameters of tomcat7.exe (the 
 ones found under HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation).  
 Otherwise, in case (3) above, tomcat7.exe would not be able to start the JVM 
 etc..
 
 So there must be something wrong with the parameters used by the Windows 
 Service Manager when it tries to start the Tomcat service. (The ones under 
 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\)
 
 What that would be, I couldn't say, and certainly not without access to your 
 Registry.
 
 But what I would do at this stage is this :
 
 1) de-install Tomcat again (do not delete the installer.exe file that you 
 downloaded, you'll need it again)
 2) using the Registry Editor (carefully), go to the key 
 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\, and delete it 
 (and everything under it).
 3) reboot Windows, and with the Registry Editor, verify that the key is still 
 deleted
 (I am saying that because who knows what MS will have invented yet to 
 re-instate things that you deleted..)
 4) re-install the Tomcat service by re-running the installer
 5) try again to start Tomcat
 
 and tell us what happens.
 
 
 
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 


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

Re: Tomcat 7 doesn't start on Windows

2013-02-27 Thread Nick Williams


On Feb 27, 2013, at 7:36 AM, Rune Stilling wrote:

 Hi André
 
 Thanks for an excellent summary. There's one thing that I haven't been 
 precise enough about I can see.
 
 I CANNOT run Tomcat via the RS-parameter:
 
 Tomcat7.exe //RS/Tomcat7
 
 If I try the log produces the following:
 
 [2013-02-27 14:33:55] [info]  [548184] Commons Daemon procrun (1.0.13.0 
 64-bit) started
 [2013-02-27 14:33:55] [info]  [548184] Running 'Tomcat7' Service...
 [2013-02-27 14:33:55] [error] [548184] StartServiceCtrlDispatcher for 
 'Tomcat7' failed
 [2013-02-27 14:33:55] [error] [548184] The service process could not connect 
 to the service controller.
 [2013-02-27 14:33:55] [error] [548184] Commons Daemon procrun failed with 
 exit value: 4 (Failed to run service)
 [2013-02-27 14:33:55] [error] [548184] The service process could not connect 
 to the service controller.

This is expected. Per Microsoft's website [1] you cannot run services 
interactively from the command line. (You can start them from the command line, 
i.e. with `sc start`, but you cannot run them from the command line, i.e. with 
`Tomcat7.exe //RS/Tomcat7`.) This is why from the command line it works with 
`Tomcat7.exe //TS/Tomcat7` ... that command tells Tomcat to not attempt to 
connect to the service controller.

The service process could not connect to the service controller in this case 
is unrelated to the fact that you can't start the Tomcat service from the 
service controller. If you got this message when you tried to start the Tomcat 
service normally, then I would be worried.

One thing I would point out is that your JAVA_HOME environmental variable is 
not correct. This should NOT affect Tomcat when it is running as a service, as 
far as I know. JAVA_HOME should be the home directory of a JDK (e.g., 
C:\Program Files\Java\jdk7) and JRE_HOME should be the home directory of a JRE 
(e.g., C:\Program Files\Java\jre7). Your JRE_HOME is correct, but your 
JAVA_HOME is C:\Program Files\Java. Again, this doesn't matter when Tomcat is 
run as a service. Also, Tomcat only NEEDS a JRE_HOME (and only when running not 
as as service), it does not NEED a JAVA_HOME. But if you have a JAVA_HOME, it 
should be correct.

I've encountered and solved hundreds of Tomcat-as-a-Windows-Service problems 
before, but I have never seen Tomcat not log anything. If you don't mind, could 
you run Tomcat7w.exe, screenshot each tab (Alt + Print Screen gets a screenshot 
for just the window instead of the whole thing), put the screenshots online 
somewhere public, and then post links to the screenshots here? My money is on 
finding something amiss there.

Question: When you run the service installer, it installs Tomcat at C:\Program 
Files\Apache Software Foundation\Tomcat 7.0, correct? (Unless, of course, you 
changed it at install time.)

Question: I know at some point you said this, but I can't find the email 
anymore. Can you remind me what version of Windows you are running on?

[1] http://msdn.microsoft.com/en-us/library/ms686324(VS.85).aspx

 
 What I CAN do is to run it via the TS-parameter:
 
 Tomcat7.exe //TS/Tomcat7
 
 But - I'll try what you suggested anyways.
 
 /Rune
 
 Den 27/02/2013 kl. 14.20 skrev André Warnier a...@ice-sa.com:
 
 Rune Stilling wrote:
 Is there some registry key I could check related to the installation 
 process?
 Call up the Registry Editor, and search for tomcat7.
 
 You should find essentially 2 places :
 
 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7
 (under this one, you will find the parameters which Windows needs to know 
 about the service (such as, how to start it) (it being tomcat7.exe)
 
 HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\
 (under this one, you will find the parameters which tomcat7.exe (the 
 service wrapper) needs to know (such as, which JVM to start and with which 
 parameters)
 
 (and remember, tomcat7.exe is a renamed prunsrv.exe, which is one of the 2 
 modules that are part of procrun).
 
 --
 
 Let's step back a bit.
 
 1) you install Tomcat on the machine, using the Windows installer package 
 from tomcat.apache.org.
 
 2) this installer creates the Registry value :
 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\ImagePath = 
 C:\apache-tomcat-\bin\tomcat7.exe //RS//Tomcat7
 (or similar)
 This Registry value is the one that will be used by the Windows Service 
 Manager, to know which program to launch when you click on Services.. 
 Tomcat7...start.
 
 3) when you login as a user onto the machine, open a command window, and run 
 the above command (C:\apache-tomcat-\bin\tomcat7.exe //RS//Tomcat7), 
 the tomcat7.exe program runs, and starts a JVM which starts Tomcat, as a 
 Service.
 And that works fine, tomcat logs are produced etc.
 
 4) when instead, you open the Windows Service Manager dialog, and ask 
 Windows to start the Tomcat service, nothing happens.
 (Tomcat does not start, tomcat7.exe does not run, no logs are produced etc.)
 
 So

RE: Tomcat 7 doesn't start on Windows

2013-02-27 Thread Caldarale, Charles R

 From: Rune Stilling [mailto:s...@rdfined.dk] 
 Subject: Re: Tomcat 7 doesn't start on Windows

 Hi André

Stop top-posting.  Be considerate of others.

I have duplicated the service not starting problem on my Windows 7 box; it's 
looking like a procrun parameter parsing problem, but I'm still chasing it.

 - Chuck

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

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

Re: Tomcat 7 doesn't start on Windows

 I've encountered and solved hundreds of Tomcat-as-a-Windows-Service problems 
 before, but I have never seen Tomcat not log anything. If you don't mind, 
 could you run Tomcat7w.exe, screenshot each tab (Alt + Print Screen gets a 
 screenshot for just the window instead of the whole thing), put the 
 screenshots online somewhere public, and then post links to the screenshots 
 here? My money is on finding something amiss there.

http://rdfined.fastmail.fm/diverse/Tomcat7w.zip

 Question: When you run the service installer, it installs Tomcat at 
 C:\Program Files\Apache Software Foundation\Tomcat 7.0, correct? (Unless, of 
 course, you changed it at install time.)

Yes - It creates that exact path and install files into the Tomcat 7.0 folder.

 Question: I know at some point you said this, but I can't find the email 
 anymore. Can you remind me what version of Windows you are running on?

Microsoft Windows 2003 R2 - Datacenter x64 edition - Service Pack 2
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: mod_jk how to add JK_WORKER_NAME to http-header

2013-02-27 Thread Rainer Jung

On 27.02.2013 12:16, André Warnier wrote:
 Hi. Before you do that, you may want to have another look at this page :
 http://tomcat.apache.org/connectors-doc/reference/apache.html
 and in particular the section at the end labeled : Using SetHandler and
 Environment Variables
 
 I use this way of configuring the proxy-ing of requests via mod_jk,
 rather than the JkMount and uriworkermap style, for some (purely
 personal) reasons :
 - it keeps things in one place (the httpd config file)
 - I believe that it fits better in the Apache httpd configuration
 style, allowing you to use the classical Apache Location,
 LocationMatch etc.. to decide which URLs are being proxied
 - I find it easier that way, to mentally see where and when what happens
 at the Apache level when you use mod_jk + Tomcat, as in fact an Apache
 response handler.
 
 For example, in your case, you could set up the following section in
 Apache, to replace your external uri map :
 
 LocationMatch ^\/(c|group|html|image|language|layouttpl|...)\/
   # in principle, for all those, pass them on to Tomcat..
   SetHandler jakarta-servlet
   SetEnv JK_WORKER_NAME liferay-1
 
   # but for some subset, do not pass them on, and let Apache itself
 handle them
   SetEnvIf REQUEST_URI (some condition) no-jk
   ...
   (set other filters, variables, headers, whatever)
   ...
 /LocationMatch
 
 Just so that you would know about it.

Thanks Andre, in my second recipe I forgot the SetHandler jakarta-servlet.

Rainer

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

Re: tomcat-7.0.35 ON Window Server SP 2

dku...@ccilindia.co.in wrote:

Hi,

I have downloaded apache-tomcat-7.0.35.zip and runiing it on Window Server
SP 2 machine and it is working fine.
Is it OK to run apache-tomcat-7.0.35 setup on Window Server SP 2 machine?

Please reply.

Server version: Apache Tomcat/7.0.35
OS Name:Windows Server SP 2 32 bit

This current version is 7.0.37.
Further down that page, in the section entitled 7.0.37, it shows the various packages
available for download, and there is also a link to a README. This README page provides
plenty of information regarding which package contains what, and the kind of platform and
installation that it corresponds to.

Now considering all that,
- why did you download and install a version 7.0.35, instead of the latest 7.0.37 ? (and
where did you get it from ?)
- why did you not download and install either the 32-bit Windows zip, or the 32/64-bit
Windows Service Installer ?

And in short, why do you waste /our/ time instead of spending some of /your/ time to at
least read what people have already written and posted on the website for everyone to see ?

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

Re: tomcat-7.0.35 ON Window Server SP 2

2013-02-27 Thread Michael-O


Am 2013-02-27 19:36, schrieb André Warnier:

dku...@ccilindia.co.in wrote:

Hi,

I have downloaded apache-tomcat-7.0.35.zip and runiing it on Window
Server SP 2 machine and it is working fine. Is it OK to run
apache-tomcat-7.0.35 setup on Window Server SP 2 machine?
Please reply.

Server version: Apache Tomcat/7.0.35
OS Name:Windows Server SP 2  32 bit




On the home page of Tomcat, at : http://tomcat.apache.org/,
- there is a link Which version, which gives a quick overview of the
available versions an the corresponding Java versions required etc.
- there is also a link Download .. Tomcat 7.0. This leads to a page
which shows the current version of Tomcat 7.x available for download.
This current version is 7.0.37.
Further down that page, in the section entitled 7.0.37, it shows the
various packages available for download, and there is also a link to a
README.  This README page provides plenty of information regarding which
package contains what, and the kind of platform and installation that it
corresponds to.

Now considering all that,
- why did you download and install a version 7.0.35, instead of the
latest 7.0.37 ? (and where did you get it from ?)
- why did you not download and install either the 32-bit Windows zip, or
the 32/64-bit Windows Service Installer ?

And in short, why do you waste /our/ time instead of spending some of
/your/ time to at least read what people have already written and posted
on the website for everyone to see ?


Why are you even answering this? The guy is not even capable to provide 
full OS information.


M



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

tomcat7-maven-plugin: Build on executable war file

2013-02-27 Thread Richard McAleer

Hi,
We're using tomcat7-maven-plugin 2.1 to build an executable war using
the standalone-war-only goal. The maven build still generates the
normal war file as well as the executable .war created by the plugin.
However, since the standalone-war-only goal generates a war that is both
executable and deployable, we really don't need to generate the normal
war file.

Thanks,
Richard

--
Richard McAleer
Developer
Web Development Team

*CARIS* http://www.caris.com
115 Waggoners Lane
Fredericton, New Brunswick
CanadaE3B 2L4
Tel: +1.506.458.8533 Fax: +1.506.459.3849
www.caris.com http://www.caris.com

*Connect with CARIS*
Twitter http://www.twitter.com/CARIS_GIS | LinkedIn
http://www.linkedin.com/groups?mostPopular=gid=3217878 | Facebook
https://www.facebook.com/pages/CARIS-The-Marine-GIS-Experts/123907500987669?v=app_4949752878
| Google+
https://plus.google.com/b/114389770462919844434/114389770462919844434/posts
| YouTube http://www.youtube.com/user/CARISGIS

Download your free copy of CARIS Easy View today!
www.caris.com/easyview http://www.caris.com/easyview

_
This email and any files transmitted with it are confidential and
intended only for the addressee(s). If you are not the intended
recipient(s) please notify us by email reply. You should not use,
disclose, distribute or copy this communication if received in error.

Any views or opinions expressed in this email are solely those of the
author and do not necessarily represent those of the company. No binding
contract will result from this email until such time as a written
document is signed on behalf of the company.

Re: tomcat-7.0.35 ON Window Server SP 2