You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by si...@8host.pl on 2011/11/26 00:13:04 UTC

Tomcat 5.5 crashes after changing server IP

Hi, i recently move server to new IP, since this change ive got 
permanently this error, i tryed everything but im fail.


[Fri Nov 25 23:56:29 2011] [notice] SELinux policy enabled; httpd 
running as context root:system_r:httpd_t:s0
[Fri Nov 25 23:56:29 2011] [notice] suEXEC mechanism enabled (wrapper: 
/usr/sbin/suexec)
[Fri Nov 25 23:56:29 2011] [info] Init: Seeding PRNG with 256 bytes of 
entropy
[Fri Nov 25 23:56:29 2011] [info] Loading certificate & private key of 
SSL-aware server
[Fri Nov 25 23:56:29 2011] [debug] ssl_engine_pphrase.c(469): 
unencrypted RSA private key - pass phrase not required
[Fri Nov 25 23:56:29 2011] [info] Init: Generating temporary RSA 
private keys (512/1024 bits)
[Fri Nov 25 23:56:29 2011] [info] Init: Generating temporary DH 
parameters (512/1024 bits)
[Fri Nov 25 23:56:29 2011] [info] Init: Initializing (virtual) servers 
for SSL
[Fri Nov 25 23:56:29 2011] [info] Configuring server for SSL protocol
[Fri Nov 25 23:56:29 2011] [debug] ssl_engine_init.c(406): Creating new 
SSL context (protocols: SSLv3, TLSv1)
[Fri Nov 25 23:56:29 2011] [debug] ssl_engine_init.c(602): Configuring 
permitted SSL ciphers 
[ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW]
[Fri Nov 25 23:56:29 2011] [debug] ssl_engine_init.c(730): Configuring 
RSA server certificate
[Fri Nov 25 23:56:29 2011] [warn] RSA server certificate is a CA 
certificate (BasicConstraints: CA == TRUE !?)
[Fri Nov 25 23:56:29 2011] [warn] RSA server certificate CommonName 
(CN) `bilet.8host.pl' does NOT match server name!?
[Fri Nov 25 23:56:29 2011] [debug] ssl_engine_init.c(769): Configuring 
RSA server private key
[Fri Nov 25 23:56:29 2011] [info] Server: Apache/2.2.3, Interface: 
mod_ssl/2.2.3, Library: OpenSSL/0.9.8e-fips-rhel5
[Fri Nov 25 23:56:29 2011] [notice] Digest: generating secret for 
digest authentication ...
[Fri Nov 25 23:56:29 2011] [notice] Digest: done
[Fri Nov 25 23:56:29 2011] [debug] util_ldap.c(2021): LDAP merging 
Shared Cache conf: shm=0x2b1216c74a18 rmm=0x2b1216c74a70 for VHOST: 
bilety.mosir.torun.pl
[Fri Nov 25 23:56:29 2011] [debug] util_ldap.c(2021): LDAP merging 
Shared Cache conf: shm=0x2b1216c74a18 rmm=0x2b1216c74a70 for VHOST: 
bilety.mosir.torun.pl
[Fri Nov 25 23:56:29 2011] [info] APR LDAP: Built with OpenLDAP LDAP 
SDK
[Fri Nov 25 23:56:29 2011] [info] LDAP: SSL support available
[Fri Nov 25 23:56:29 2011] [info] Init: Seeding PRNG with 256 bytes of 
entropy
[Fri Nov 25 23:56:29 2011] [info] Loading certificate & private key of 
SSL-aware server
[Fri Nov 25 23:56:29 2011] [debug] ssl_engine_pphrase.c(469): 
unencrypted RSA private key - pass phrase not required
[Fri Nov 25 23:56:29 2011] [info] Init: Generating temporary RSA 
private keys (512/1024 bits)
[Fri Nov 25 23:56:29 2011] [info] Init: Generating temporary DH 
parameters (512/1024 bits)
[Fri Nov 25 23:56:29 2011] [debug] ssl_scache_shmcb.c(374): shmcb_init 
allocated 512000 bytes of shared memory
[Fri Nov 25 23:56:29 2011] [debug] ssl_scache_shmcb.c(554): entered 
shmcb_init_memory()
[Fri Nov 25 23:56:29 2011] [debug] ssl_scache_shmcb.c(576): for 512000 
bytes, recommending 4265 indexes
[Fri Nov 25 23:56:29 2011] [debug] ssl_scache_shmcb.c(619): 
shmcb_init_memory choices follow
[Fri Nov 25 23:56:29 2011] [debug] ssl_scache_shmcb.c(621): 
division_mask = 0x1F
[Fri Nov 25 23:56:29 2011] [debug] ssl_scache_shmcb.c(623): 
division_offset = 96
[Fri Nov 25 23:56:29 2011] [debug] ssl_scache_shmcb.c(625): 
division_size = 15997
[Fri Nov 25 23:56:29 2011] [debug] ssl_scache_shmcb.c(627): queue_size 
= 2136
[Fri Nov 25 23:56:29 2011] [debug] ssl_scache_shmcb.c(629): index_num = 
133
[Fri Nov 25 23:56:29 2011] [debug] ssl_scache_shmcb.c(631): 
index_offset = 8
[Fri Nov 25 23:56:29 2011] [debug] ssl_scache_shmcb.c(633): index_size 
= 16
[Fri Nov 25 23:56:29 2011] [debug] ssl_scache_shmcb.c(635): 
cache_data_offset = 8
[Fri Nov 25 23:56:29 2011] [debug] ssl_scache_shmcb.c(637): 
cache_data_size = 13853
[Fri Nov 25 23:56:29 2011] [debug] ssl_scache_shmcb.c(650): leaving 
shmcb_init_memory()
[Fri Nov 25 23:56:29 2011] [info] Shared memory session cache 
initialised
[Fri Nov 25 23:56:29 2011] [info] Init: Initializing (virtual) servers 
for SSL
[Fri Nov 25 23:56:29 2011] [info] Configuring server for SSL protocol
[Fri Nov 25 23:56:29 2011] [debug] ssl_engine_init.c(406): Creating new 
SSL context (protocols: SSLv3, TLSv1)
[Fri Nov 25 23:56:29 2011] [debug] ssl_engine_init.c(602): Configuring 
permitted SSL ciphers 
[ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW]
[Fri Nov 25 23:56:29 2011] [debug] ssl_engine_init.c(730): Configuring 
RSA server certificate
[Fri Nov 25 23:56:29 2011] [warn] RSA server certificate is a CA 
certificate (BasicConstraints: CA == TRUE !?)
[Fri Nov 25 23:56:29 2011] [warn] RSA server certificate CommonName 
(CN) `xxxxxx' does NOT match server name!?
[Fri Nov 25 23:56:29 2011] [debug] ssl_engine_init.c(769): Configuring 
RSA server private key
[Fri Nov 25 23:56:29 2011] [info] Server: Apache/2.2.3, Interface: 
mod_ssl/2.2.3, Library: OpenSSL/0.9.8e-fips-rhel5
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 2 in child 1838 for worker proxy:reverse
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 2 in child 1838 for (*)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 1 in child 1838 for worker ajp://localhost:8009/
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 1 in child 1838 for (localhost)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 0 in child 1838 for worker ajp://localhost:8009/
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 0 in child 1838 for (localhost)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 2 in child 1839 for worker proxy:reverse
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
proxy:reverse already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 2 in child 1839 for (*)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 1 in child 1839 for worker ajp://localhost:8009/
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
ajp://localhost:8009/ already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 1 in child 1839 for (localhost)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 0 in child 1839 for worker ajp://localhost:8009/
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
ajp://localhost:8009/ already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 0 in child 1839 for (localhost)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 2 in child 1840 for worker proxy:reverse
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
proxy:reverse already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 2 in child 1840 for (*)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 1 in child 1840 for worker ajp://localhost:8009/
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
ajp://localhost:8009/ already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 1 in child 1840 for (localhost)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 0 in child 1840 for worker ajp://localhost:8009/
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
ajp://localhost:8009/ already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 0 in child 1840 for (localhost)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 2 in child 1841 for worker proxy:reverse
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
proxy:reverse already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 2 in child 1841 for (*)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 1 in child 1841 for worker ajp://localhost:8009/
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
ajp://localhost:8009/ already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 1 in child 1841 for (localhost)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 0 in child 1841 for worker ajp://localhost:8009/
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
ajp://localhost:8009/ already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 0 in child 1841 for (localhost)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 2 in child 1842 for worker proxy:reverse
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
proxy:reverse already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 2 in child 1842 for (*)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 1 in child 1842 for worker ajp://localhost:8009/
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
ajp://localhost:8009/ already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 1 in child 1842 for (localhost)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 0 in child 1842 for worker ajp://localhost:8009/
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
ajp://localhost:8009/ already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 0 in child 1842 for (localhost)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 2 in child 1843 for worker proxy:reverse
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
proxy:reverse already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 2 in child 1843 for (*)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 1 in child 1843 for worker ajp://localhost:8009/
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
ajp://localhost:8009/ already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 1 in child 1843 for (localhost)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 0 in child 1843 for worker ajp://localhost:8009/
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
ajp://localhost:8009/ already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 0 in child 1843 for (localhost)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 2 in child 1844 for worker proxy:reverse
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
proxy:reverse already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 2 in child 1844 for (*)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 1 in child 1844 for worker ajp://localhost:8009/
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
ajp://localhost:8009/ already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 1 in child 1844 for (localhost)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 0 in child 1844 for worker ajp://localhost:8009/
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
ajp://localhost:8009/ already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 0 in child 1844 for (localhost)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 2 in child 1845 for worker proxy:reverse
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
proxy:reverse already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 2 in child 1845 for (*)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 1 in child 1845 for worker ajp://localhost:8009/
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
ajp://localhost:8009/ already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 1 in child 1845 for (localhost)
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1854): proxy: grabbed 
scoreboard slot 0 in child 1845 for worker ajp://localhost:8009/
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1873): proxy: worker 
ajp://localhost:8009/ already initialized
[Fri Nov 25 23:56:29 2011] [debug] proxy_util.c(1967): proxy: 
initialized single connection worker 0 in child 1845 for (localhost)
[Fri Nov 25 23:56:29 2011] [notice] Apache/2.2.3 (CentOS) configured -- 
resuming normal operations
[Fri Nov 25 23:56:29 2011] [info] Server built: Apr  4 2010 17:18:37
[Fri Nov 25 23:56:29 2011] [debug] prefork.c(991): AcceptMutex: sysvsem 
(default: sysvsem)
[Fri Nov 25 23:56:41 2011] [debug] mod_proxy_ajp.c(45): proxy: AJP: 
canonicalising URL //localhost:8009//login.dhtml
[Fri Nov 25 23:56:41 2011] [debug] proxy_util.c(1488): [client 
83.21.83.213] proxy: ajp: found worker ajp://localhost:8009/ for 
ajp://localhost:8009//login.dhtml
[Fri Nov 25 23:56:41 2011] [debug] mod_proxy.c(966): Running scheme ajp 
handler (attempt 0)
[Fri Nov 25 23:56:41 2011] [debug] mod_proxy_http.c(1959): proxy: HTTP: 
declining URL ajp://localhost:8009//login.dhtml
[Fri Nov 25 23:56:41 2011] [debug] mod_proxy_ajp.c(580): proxy: AJP: 
serving URL ajp://localhost:8009//login.dhtml
[Fri Nov 25 23:56:41 2011] [debug] proxy_util.c(2044): proxy: AJP: has 
acquired connection for (localhost)
[Fri Nov 25 23:56:41 2011] [debug] proxy_util.c(2102): proxy: 
connecting ajp://localhost:8009//login.dhtml to localhost:8009
[Fri Nov 25 23:56:41 2011] [debug] proxy_util.c(2195): proxy: connected 
//login.dhtml to localhost:8009
[Fri Nov 25 23:56:41 2011] [debug] proxy_util.c(2347): proxy: AJP: fam 
2 socket created to connect to localhost
[Fri Nov 25 23:56:41 2011] [debug] ajp_header.c(224): Into 
ajp_marshal_into_msgb
[Fri Nov 25 23:56:41 2011] [debug] ajp_header.c(290): 
ajp_marshal_into_msgb: Header[0] [Host] = [xxx]
[Fri Nov 25 23:56:41 2011] [debug] ajp_header.c(290): 
ajp_marshal_into_msgb: Header[1] [User-Agent] = [Mozilla/5.0 (Windows NT 
6.1; WOW64; rv:8.0) Gecko/20100101 Firefox/8.0]
[Fri Nov 25 23:56:41 2011] [debug] ajp_header.c(290): 
ajp_marshal_into_msgb: Header[2] [Accept] = 
[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8]
[Fri Nov 25 23:56:41 2011] [debug] ajp_header.c(290): 
ajp_marshal_into_msgb: Header[3] [Accept-Language] = 
[pl,en-us;q=0.7,en;q=0.3]
[Fri Nov 25 23:56:41 2011] [debug] ajp_header.c(290): 
ajp_marshal_into_msgb: Header[4] [Accept-Encoding] = [gzip, deflate]
[Fri Nov 25 23:56:41 2011] [debug] ajp_header.c(290): 
ajp_marshal_into_msgb: Header[5] [Accept-Charset] = 
[ISO-8859-2,utf-8;q=0.7,*;q=0.7]
[Fri Nov 25 23:56:41 2011] [debug] ajp_header.c(290): 
ajp_marshal_into_msgb: Header[6] [Connection] = [keep-alive]
[Fri Nov 25 23:56:41 2011] [debug] ajp_header.c(290): 
ajp_marshal_into_msgb: Header[7] [Cache-Control] = [max-age=0]
[Fri Nov 25 23:56:41 2011] [debug] ajp_header.c(430): 
ajp_marshal_into_msgb: Done
[Fri Nov 25 23:56:41 2011] [debug] mod_proxy_ajp.c(240): proxy: 
APR_BUCKET_IS_EOS
[Fri Nov 25 23:56:41 2011] [debug] mod_proxy_ajp.c(245): proxy: data to 
read (max 8186 at 4)
[Fri Nov 25 23:56:41 2011] [debug] mod_proxy_ajp.c(260): proxy: got 0 
bytes of data
[Fri Nov 25 23:56:45 2011] [error] (70014)End of file found: 
ajp_ilink_receive() can't receive header
[Fri Nov 25 23:56:45 2011] [error] ajp_read_header: ajp_ilink_receive 
failed
[Fri Nov 25 23:56:45 2011] [error] (120006)APR does not understand this 
error code: proxy: read response failed from (null) (localhost)
[Fri Nov 25 23:56:45 2011] [debug] proxy_util.c(2062): proxy: AJP: has 
released connection for (localhost)
[Fri Nov 25 23:57:23 2011] [debug] mod_proxy_ajp.c(45): proxy: AJP: 
canonicalising URL //localhost:8009//login.dhtml
[Fri Nov 25 23:57:23 2011] [debug] proxy_util.c(1488): [client 
83.21.83.213] proxy: ajp: found worker ajp://localhost:8009/ for 
ajp://localhost:8009//login.dhtml
[Fri Nov 25 23:57:23 2011] [debug] mod_proxy.c(966): Running scheme ajp 
handler (attempt 0)
[Fri Nov 25 23:57:23 2011] [debug] mod_proxy_http.c(1959): proxy: HTTP: 
declining URL ajp://localhost:8009//login.dhtml
[Fri Nov 25 23:57:23 2011] [debug] mod_proxy_ajp.c(580): proxy: AJP: 
serving URL ajp://localhost:8009//login.dhtml
[Fri Nov 25 23:57:23 2011] [debug] proxy_util.c(2044): proxy: AJP: has 
acquired connection for (localhost)
[Fri Nov 25 23:57:23 2011] [debug] proxy_util.c(2102): proxy: 
connecting ajp://localhost:8009//login.dhtml to localhost:8009
[Fri Nov 25 23:57:23 2011] [debug] proxy_util.c(2195): proxy: connected 
//login.dhtml to localhost:8009
[Fri Nov 25 23:57:23 2011] [debug] proxy_util.c(2347): proxy: AJP: fam 
2 socket created to connect to localhost
[Fri Nov 25 23:57:23 2011] [error] (111)Connection refused: proxy: AJP: 
attempt to connect to 127.0.0.1:8009 (localhost) failed
[Fri Nov 25 23:57:23 2011] [error] ap_proxy_connect_backend disabling 
worker for (localhost)
[Fri Nov 25 23:57:23 2011] [error] proxy: AJP: failed to make 
connection to backend: localhost
[Fri Nov 25 23:57:23 2011] [debug] proxy_util.c(2062): proxy: AJP: has 
released connection for (localhost)
[Fri Nov 25 23:57:24 2011] [debug] mod_proxy_ajp.c(45): proxy: AJP: 
canonicalising URL //localhost:8009//login.dhtml
[Fri Nov 25 23:57:24 2011] [debug] proxy_util.c(1488): [client 
83.21.83.213] proxy: ajp: found worker ajp://localhost:8009/ for 
ajp://localhost:8009//login.dhtml
[Fri Nov 25 23:57:24 2011] [debug] mod_proxy.c(966): Running scheme ajp 
handler (attempt 0)
[Fri Nov 25 23:57:24 2011] [debug] mod_proxy_http.c(1959): proxy: HTTP: 
declining URL ajp://localhost:8009//login.dhtml
[Fri Nov 25 23:57:24 2011] [debug] mod_proxy_ajp.c(580): proxy: AJP: 
serving URL ajp://localhost:8009//login.dhtml
[Fri Nov 25 23:57:24 2011] [debug] proxy_util.c(1982): proxy: AJP: 
retrying the worker for (localhost)
[Fri Nov 25 23:57:24 2011] [error] proxy: AJP: disabled connection for 
(localhost)


And "Service Temporarily Unavailable The server is temporarily unable 
to service your request due to maintenance downtime or capacity 
problems. Please try again later."


Only change that ive got was on new install of Tomcat 6 or 7 with 
default config files, then ive got : The web application [] is still 
processing a request that has yet to finish. This is very likely to 
create a memory leak. You can control the time allowed for requests to 
finish by using the unloadDelay attribute of the standard error.


Any ideas ?

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


Re: Tomcat 5.5 crashes after changing server IP

Posted by Pid <pi...@pidster.com>.
On 12/12/2011 12:02, André Warnier wrote:
> sirwiz@8host.pl wrote:
>>>> It is probly Tomcat + Xen (KVM) + Intel (?) releted problem.
>>>
>>> I really have no idea how you come to that conclusion.
>>
>> Like i said when i install Windows 8 on Xen machine, starts Virtuabox
>> on it and new 32bit Centos, tomcat and my api works perfectly. It was
>> running for a 2 years on AMD procesor (with the same config files) and
>> it works like charm also. Problem starts when we switch to new Intel
>> machine. I also try to install the same version of xen on AMD server
>> and it works, that only dont work on xen or kvm. Also i dowload whole
>> Xen disk image and run it on different intel procesor on virtuabox
>> (Windoiws 7) and the same error. Its realy strange situation when i
>> have to virtualize 2 systems to make it work ;). When i convert
>> working virtuabox machine to Xen image, i have the same error.

Correlation != causation

Have you fixed the other errors in your config?


p

> It seems really unclear what all of this has to do with Tomcat.
> Tomcat is Java code. It runs under a JVM, and uses that JVM's code for
> anything to do with the interface to the underlying OS or hardware.  So
> it should not make an iota of difference to Tomcat under which OS and
> machine it is running.
> On the other hand, the /JVM/ which you are using may have problems, but
> again that has nothing to do fundamentally with Tomcat.
> 
>>
>>
>>>> I install
>>>> tomcat from 5 to 7 on diferent VPS's, always have the same result but
>>>> always i have Xen or KVM and Intel CPU, old serwer has AMD cpu and all
>>>> works great (and some older version of Xen also), but on new Xen or KVM
>>>> based VPS i always have the same problem. But when i run XEN machine
>>>> with Windows 8 and run on it VirtuaBox and starts new 32 bit CentOS all
>>>> work great (but i have virtualization on virtualized machine ;) ). Its
>>>> realy strange problem, and have no idea how to solve it.
>>>
>>> Fix one thing at a time.  Start with your config.
>>
>> It was log from "oryginal" Tomcat instalation, on new install we have
>> only AJP stops and Memory Leak.
>>
> 
> Then provide the new log, or do you just want us to keep guessing ?
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 


-- 

[key:62590808]


Re: Tomcat 5.5 crashes after changing server IP

Posted by André Warnier <aw...@ice-sa.com>.
sirwiz@8host.pl wrote:
>>> It is probly Tomcat + Xen (KVM) + Intel (?) releted problem.
>>
>> I really have no idea how you come to that conclusion.
> 
> Like i said when i install Windows 8 on Xen machine, starts Virtuabox on 
> it and new 32bit Centos, tomcat and my api works perfectly. It was 
> running for a 2 years on AMD procesor (with the same config files) and 
> it works like charm also. Problem starts when we switch to new Intel 
> machine. I also try to install the same version of xen on AMD server and 
> it works, that only dont work on xen or kvm. Also i dowload whole Xen 
> disk image and run it on different intel procesor on virtuabox (Windoiws 
> 7) and the same error. Its realy strange situation when i have to 
> virtualize 2 systems to make it work ;). When i convert working 
> virtuabox machine to Xen image, i have the same error.

It seems really unclear what all of this has to do with Tomcat.
Tomcat is Java code. It runs under a JVM, and uses that JVM's code for anything to do with 
the interface to the underlying OS or hardware.  So it should not make an iota of 
difference to Tomcat under which OS and machine it is running.
On the other hand, the /JVM/ which you are using may have problems, but again that has 
nothing to do fundamentally with Tomcat.

> 
> 
>>> I install
>>> tomcat from 5 to 7 on diferent VPS's, always have the same result but
>>> always i have Xen or KVM and Intel CPU, old serwer has AMD cpu and all
>>> works great (and some older version of Xen also), but on new Xen or KVM
>>> based VPS i always have the same problem. But when i run XEN machine
>>> with Windows 8 and run on it VirtuaBox and starts new 32 bit CentOS all
>>> work great (but i have virtualization on virtualized machine ;) ). Its
>>> realy strange problem, and have no idea how to solve it.
>>
>> Fix one thing at a time.  Start with your config.
> 
> It was log from "oryginal" Tomcat instalation, on new install we have 
> only AJP stops and Memory Leak.
> 

Then provide the new log, or do you just want us to keep guessing ?

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


Re: Tomcat 5.5 crashes after changing server IP

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

SirWiz,

On 12/12/11 6:26 AM, sirwiz@8host.pl wrote:
>>> It is probly Tomcat + Xen (KVM) + Intel (?) releted problem.
>> 
>> I really have no idea how you come to that conclusion.
> 
> Like i said when i install Windows 8 on Xen machine, starts
> Virtuabox on it and new 32bit Centos, tomcat and my api works
> perfectly. It was running for a 2 years on AMD procesor (with the
> same config files) and it works like charm also.

So, you are running a doubly-virtualized environment? That seems ...
unnecessary.

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

iEYEARECAAYFAk7mXugACgkQ9CaO5/Lv0PCMSQCfd71oa1BjWJMrj3nmPC5lo3SL
wbYAoKz4/5McJD6sw7dWkDxzJOaM+cO/
=vdWF
-----END PGP SIGNATURE-----

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


Re: Tomcat 5.5 crashes after changing server IP

Posted by si...@8host.pl.
>> It is probly Tomcat + Xen (KVM) + Intel (?) releted problem.
>
> I really have no idea how you come to that conclusion.

Like i said when i install Windows 8 on Xen machine, starts Virtuabox 
on it and new 32bit Centos, tomcat and my api works perfectly. It was 
running for a 2 years on AMD procesor (with the same config files) and 
it works like charm also. Problem starts when we switch to new Intel 
machine. I also try to install the same version of xen on AMD server and 
it works, that only dont work on xen or kvm. Also i dowload whole Xen 
disk image and run it on different intel procesor on virtuabox (Windoiws 
7) and the same error. Its realy strange situation when i have to 
virtualize 2 systems to make it work ;). When i convert working 
virtuabox machine to Xen image, i have the same error.


>> I install
>> tomcat from 5 to 7 on diferent VPS's, always have the same result 
>> but
>> always i have Xen or KVM and Intel CPU, old serwer has AMD cpu and 
>> all
>> works great (and some older version of Xen also), but on new Xen or 
>> KVM
>> based VPS i always have the same problem. But when i run XEN machine
>> with Windows 8 and run on it VirtuaBox and starts new 32 bit CentOS 
>> all
>> work great (but i have virtualization on virtualized machine ;) ). 
>> Its
>> realy strange problem, and have no idea how to solve it.
>
> Fix one thing at a time.  Start with your config.

It was log from "oryginal" Tomcat instalation, on new install we have 
only AJP stops and Memory Leak.

Best wishes
Marcin


On 12.12.2011 09:03, Pid wrote:
> On 12/12/2011 00:29, sirwiz@8host.pl wrote:
>> One more log:
>>
>> 2011-12-12 00:52:15 org.apache.catalina.core.AprLifecycleListener 
>> init
>> INFO: The APR based Apache Tomcat Native library which allows 
>> optimal
>> performance in production environments was not found on the
>> java.library.path:
>> 
>> /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/server:/usr/lib/jvm/java-1$
>>
>> 2011-12-12 00:52:16 org.apache.tomcat.util.digester.Digester 
>> endElement
>> WARNING:   No rules found matching 'Server/Service/Context'.
>
> You can't define a Context directly under Service in server.xml, it 
> must
> be inside a Host.
>
> You should avoid defining the Context in server.xml at all.  Instead,
> put it in 'torun/META-INF/context.xml'
>
>> 2011-12-12 00:52:16 
>> org.apache.tomcat.util.digester.SetPropertiesRule begin
>> WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting
>> property 'debug' to '0' did not find a matching property.
>
> There is no debug property on Host.
>
>> 2011-12-12 00:52:16 
>> org.apache.tomcat.util.digester.SetPropertiesRule begin
>> WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} 
>> Setting
>> property 'debug' to '0' did not find a matching property.
>
> There is no debug property on Context.
>
>> 2011-12-12 00:52:16 org.apache.coyote.http11.Http11Protocol init
>> INFO: Initializing Coyote HTTP/1.1 on http-8080
>> 2011-12-12 00:52:16 org.apache.catalina.startup.Catalina load
>> INFO: Initialization processed in 1020 ms
>> 2011-12-12 00:52:16 org.apache.catalina.core.StandardService start
>> INFO: Starting service Catalina
>> 2011-12-12 00:52:16 org.apache.catalina.core.StandardEngine start
>> INFO: Starting Servlet Engine: Apache Tomcat/6.0.32
>> 2011-12-12 00:52:17 org.apache.catalina.loader.WebappClassLoader
>> validateJarFile
>> INFO: validateJarFile(/var/www/torun/WEB-INF/lib/servletapi-2.2.jar) 
>> -
>> jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending 
>> class:
>> javax/servlet/Servlet.class
>
> You have a JAR in your application that you should not have.
>
> If you have published /var/www/ (or /var/www/torun) as an Apache 
> HTTPD
> DocumentRoot you are increasing the risk of exposing data that should 
> be
> protected, because Apache HTTPD will bypass Tomcat controls.
>
>> 2011-12-12 00:52:18 org.apache.catalina.startup.HostConfig 
>> deployDescriptor
>> INFO: Deploying configuration descriptor host-manager.xml
>> 2011-12-12 00:52:18 org.apache.catalina.startup.HostConfig 
>> deployDescriptor
>> INFO: Deploying configuration descriptor manager.xml
>> 2011-12-12 00:52:18 org.apache.catalina.startup.HostConfig 
>> deployDirectory
>> INFO: Deploying web application directory docs
>> 2011-12-12 00:52:18 org.apache.catalina.startup.HostConfig 
>> deployDirectory
>> INFO: Deploying web application directory ROOT
>> 2011-12-12 00:52:18 org.apache.catalina.startup.HostConfig 
>> deployDirectory
>> INFO: Deploying web application directory examples
>> 2011-12-12 00:52:18 org.apache.coyote.http11.Http11Protocol start
>> INFO: Starting Coyote HTTP/1.1 on http-8080
>> 2011-12-12 00:52:18 org.apache.jk.common.ChannelSocket init
>> INFO: JK: ajp13 listening on /0.0.0.0:8009
>> 2011-12-12 00:52:18 org.apache.jk.server.JkMain start
>> INFO: Jk running ID=0 time=0/10  config=null
>> 2011-12-12 00:52:18 org.apache.catalina.startup.Catalina start
>> INFO: Server startup in 1976 ms
>> 2011-12-12 00:53:09 org.apache.coyote.http11.Http11Protocol pause
>> INFO: Pausing Coyote HTTP/1.1 on http-8080
>> 2011-12-12 00:53:10 org.apache.catalina.core.StandardService stop
>> INFO: Stopping service Catalina
>
> This looks like a normal stop.
>
>> 2011-12-12 00:53:10 org.apache.catalina.core.StandardWrapper unload
>> INFO: Waiting for 1 instance(s) to be deallocated
>> 2011-12-12 00:53:11 org.apache.catalina.core.StandardWrapper unload
>> INFO: Waiting for 1 instance(s) to be deallocated
>> 2011-12-12 00:53:12 org.apache.catalina.core.StandardWrapper unload
>> INFO: Waiting for 1 instance(s) to be deallocated
>> 2011-12-12 00:53:12 org.apache.catalina.loader.WebappClassLoader
>> clearReferencesThreads
>> SEVERE: The web application [] is still processing a request that 
>> has
>> yet to finish. This is very likely to create a memory leak. You can
>> control the time allowed for requests to finish by using the 
>> unloadDelay
>> attribute of the standard$
>> 2011-12-12 00:53:12 org.apache.coyote.http11.Http11Protocol destroy
>> INFO: Stopping Coyote HTTP/1.1 on http-8080
>
> A request was taking a long time to process & was still running when 
> the
> server stopped.
>
>> It is probly Tomcat + Xen (KVM) + Intel (?) releted problem.
>
> I really have no idea how you come to that conclusion.
>
>
>> I install
>> tomcat from 5 to 7 on diferent VPS's, always have the same result 
>> but
>> always i have Xen or KVM and Intel CPU, old serwer has AMD cpu and 
>> all
>> works great (and some older version of Xen also), but on new Xen or 
>> KVM
>> based VPS i always have the same problem. But when i run XEN machine
>> with Windows 8 and run on it VirtuaBox and starts new 32 bit CentOS 
>> all
>> work great (but i have virtualization on virtualized machine ;) ). 
>> Its
>> realy strange problem, and have no idea how to solve it.
>
> Fix one thing at a time.  Start with your config.
>
>
> p
>
>
>> On 29.11.2011 23:05, Christopher Schultz wrote:
>> Sirwiz,
>>
>> On 11/29/11 11:51 AM, sirwiz@8host.pl wrote:
>>>>> I can run tomcat with examples scripts (i just install t 7.0.23)
>>>>> and i have this error:
>>>>>
>>>>> 2011-11-29 17:38:43 org.apache.coyote.AbstractProtocol start 
>>>>> INFO:
>>>>> Starting ProtocolHandler ["http-bio-8080"] 2011-11-29 17:38:43
>>>>> org.apache.coyote.AbstractProtocol start INFO: Starting
>>>>> ProtocolHandler ["ajp-bio-8009"] 2011-11-29 17:38:43
>>>>> org.apache.catalina.startup.Catalina start INFO: Server startup 
>>>>> in
>>>>> 645 ms 2011-11-29 17:39:50 org.apache.coyote.AbstractProtocol
>>>>> pause INFO: Pausing ProtocolHandler ["http-bio-8080"] 2011-11-29
>>>>> 17:39:50 org.apache.coyote.AbstractProtocol pause INFO: Pausing
>>>>> ProtocolHandler ["ajp-bio-8009"] 2011-11-29 17:39:50
>>>>> org.apache.catalina.core.StandardService stopInternal INFO:
>>>>> Stopping service Catalina 2011-11-29 17:39:50
>>>>> org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 
>>>>> 1
>>>>> instance(s) to be deallocated 2011-11-29 17:39:51
>>>>> org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 
>>>>> 1
>>>>> instance(s) to be deallocated 2011-11-29 17:39:52
>>>>> org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 
>>>>> 1
>>>>> instance(s) to be deallocated 2011-11-29 17:39:52
>>>>> org.apache.catalina.loader.WebappClassLoader
>>>>> clearReferencesThreads SEVERE: The web application [] is still
>>>>> processing a request that has yet to finish. This is very likely 
>>>>> to
>>>>> create a memory leak. You can control the time allowed for $
>>>>> 2011-11-29 17:39:52 org.apache.coyote.AbstractProtocol stop INFO:
>>>>> Stopping ProtocolHandler ["http-bio-8080"] 2011-11-29 17:39:52
>>>>> org.apache.coyote.AbstractProtocol stop INFO: Stopping
>>>>> ProtocolHandler ["ajp-bio-8009"] 2011-11-29 17:39:52
>>>>> org.apache.coyote.AbstractProtocol destroy INFO: Destroying
>>>>> ProtocolHandler ["http-bio-8080"] 2011-11-29 17:39:52
>>>>> org.apache.coyote.AbstractProtocol destroy INFO: Destroying
>>>>> ProtocolHandler ["ajp-bio-8009"]
>>>>>
>>>>>
>>>>> Then server stops.
>>
>> That looks like an orderly shutdown of Tomcat.
>>
>>>>> On old machine it works perfect without any problems. I speak 
>>>>> with
>>>>> my administrator and i get information that this server is a
>>>>> virtualization on XEN, and with IP they change procesor of hub
>>>>> machine, but it shouldnt make difrence to xen virtusalization
>>>>> server.
>>
>> I wouldn't expect Tomcat (or the JVM, really) to get upset with an 
>> IP
>> change at runtime, unless you had bound to an interface that 
>> suddenly
>> disappeared (like you bind to 10.1.1.10 and suddenly that goes 
>> away).
>> My expectation under those circumstances would be that the process
>> just continues and never sees any connections after the IP change.
>>
>> It looks more like your service was intentionally shut down.
>>
>> Are there any other logs?
>>
>> -chris
>>>
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>


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


Re: Tomcat 5.5 crashes after changing server IP

Posted by Pid <pi...@pidster.com>.
On 12/12/2011 00:29, sirwiz@8host.pl wrote:
> One more log:
> 
> 2011-12-12 00:52:15 org.apache.catalina.core.AprLifecycleListener init
> INFO: The APR based Apache Tomcat Native library which allows optimal
> performance in production environments was not found on the
> java.library.path:
> /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/server:/usr/lib/jvm/java-1$
> 
> 2011-12-12 00:52:16 org.apache.tomcat.util.digester.Digester endElement
> WARNING:   No rules found matching 'Server/Service/Context'.

You can't define a Context directly under Service in server.xml, it must
be inside a Host.

You should avoid defining the Context in server.xml at all.  Instead,
put it in 'torun/META-INF/context.xml'

> 2011-12-12 00:52:16 org.apache.tomcat.util.digester.SetPropertiesRule begin
> WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting
> property 'debug' to '0' did not find a matching property.

There is no debug property on Host.

> 2011-12-12 00:52:16 org.apache.tomcat.util.digester.SetPropertiesRule begin
> WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting
> property 'debug' to '0' did not find a matching property.

There is no debug property on Context.

> 2011-12-12 00:52:16 org.apache.coyote.http11.Http11Protocol init
> INFO: Initializing Coyote HTTP/1.1 on http-8080
> 2011-12-12 00:52:16 org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 1020 ms
> 2011-12-12 00:52:16 org.apache.catalina.core.StandardService start
> INFO: Starting service Catalina
> 2011-12-12 00:52:16 org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/6.0.32
> 2011-12-12 00:52:17 org.apache.catalina.loader.WebappClassLoader
> validateJarFile
> INFO: validateJarFile(/var/www/torun/WEB-INF/lib/servletapi-2.2.jar) -
> jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class:
> javax/servlet/Servlet.class

You have a JAR in your application that you should not have.

If you have published /var/www/ (or /var/www/torun) as an Apache HTTPD
DocumentRoot you are increasing the risk of exposing data that should be
protected, because Apache HTTPD will bypass Tomcat controls.

> 2011-12-12 00:52:18 org.apache.catalina.startup.HostConfig deployDescriptor
> INFO: Deploying configuration descriptor host-manager.xml
> 2011-12-12 00:52:18 org.apache.catalina.startup.HostConfig deployDescriptor
> INFO: Deploying configuration descriptor manager.xml
> 2011-12-12 00:52:18 org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory docs
> 2011-12-12 00:52:18 org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory ROOT
> 2011-12-12 00:52:18 org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory examples
> 2011-12-12 00:52:18 org.apache.coyote.http11.Http11Protocol start
> INFO: Starting Coyote HTTP/1.1 on http-8080
> 2011-12-12 00:52:18 org.apache.jk.common.ChannelSocket init
> INFO: JK: ajp13 listening on /0.0.0.0:8009
> 2011-12-12 00:52:18 org.apache.jk.server.JkMain start
> INFO: Jk running ID=0 time=0/10  config=null
> 2011-12-12 00:52:18 org.apache.catalina.startup.Catalina start
> INFO: Server startup in 1976 ms
> 2011-12-12 00:53:09 org.apache.coyote.http11.Http11Protocol pause
> INFO: Pausing Coyote HTTP/1.1 on http-8080
> 2011-12-12 00:53:10 org.apache.catalina.core.StandardService stop
> INFO: Stopping service Catalina

This looks like a normal stop.

> 2011-12-12 00:53:10 org.apache.catalina.core.StandardWrapper unload
> INFO: Waiting for 1 instance(s) to be deallocated
> 2011-12-12 00:53:11 org.apache.catalina.core.StandardWrapper unload
> INFO: Waiting for 1 instance(s) to be deallocated
> 2011-12-12 00:53:12 org.apache.catalina.core.StandardWrapper unload
> INFO: Waiting for 1 instance(s) to be deallocated
> 2011-12-12 00:53:12 org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads
> SEVERE: The web application [] is still processing a request that has
> yet to finish. This is very likely to create a memory leak. You can
> control the time allowed for requests to finish by using the unloadDelay
> attribute of the standard$
> 2011-12-12 00:53:12 org.apache.coyote.http11.Http11Protocol destroy
> INFO: Stopping Coyote HTTP/1.1 on http-8080

A request was taking a long time to process & was still running when the
server stopped.

> It is probly Tomcat + Xen (KVM) + Intel (?) releted problem.

I really have no idea how you come to that conclusion.


> I install
> tomcat from 5 to 7 on diferent VPS's, always have the same result but
> always i have Xen or KVM and Intel CPU, old serwer has AMD cpu and all
> works great (and some older version of Xen also), but on new Xen or KVM
> based VPS i always have the same problem. But when i run XEN machine
> with Windows 8 and run on it VirtuaBox and starts new 32 bit CentOS all
> work great (but i have virtualization on virtualized machine ;) ). Its
> realy strange problem, and have no idea how to solve it.

Fix one thing at a time.  Start with your config.


p


> On 29.11.2011 23:05, Christopher Schultz wrote:
> Sirwiz,
> 
> On 11/29/11 11:51 AM, sirwiz@8host.pl wrote:
>>>> I can run tomcat with examples scripts (i just install t 7.0.23)
>>>> and i have this error:
>>>>
>>>> 2011-11-29 17:38:43 org.apache.coyote.AbstractProtocol start INFO:
>>>> Starting ProtocolHandler ["http-bio-8080"] 2011-11-29 17:38:43
>>>> org.apache.coyote.AbstractProtocol start INFO: Starting
>>>> ProtocolHandler ["ajp-bio-8009"] 2011-11-29 17:38:43
>>>> org.apache.catalina.startup.Catalina start INFO: Server startup in
>>>> 645 ms 2011-11-29 17:39:50 org.apache.coyote.AbstractProtocol
>>>> pause INFO: Pausing ProtocolHandler ["http-bio-8080"] 2011-11-29
>>>> 17:39:50 org.apache.coyote.AbstractProtocol pause INFO: Pausing
>>>> ProtocolHandler ["ajp-bio-8009"] 2011-11-29 17:39:50
>>>> org.apache.catalina.core.StandardService stopInternal INFO:
>>>> Stopping service Catalina 2011-11-29 17:39:50
>>>> org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 1
>>>> instance(s) to be deallocated 2011-11-29 17:39:51
>>>> org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 1
>>>> instance(s) to be deallocated 2011-11-29 17:39:52
>>>> org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 1
>>>> instance(s) to be deallocated 2011-11-29 17:39:52
>>>> org.apache.catalina.loader.WebappClassLoader
>>>> clearReferencesThreads SEVERE: The web application [] is still
>>>> processing a request that has yet to finish. This is very likely to
>>>> create a memory leak. You can control the time allowed for $
>>>> 2011-11-29 17:39:52 org.apache.coyote.AbstractProtocol stop INFO:
>>>> Stopping ProtocolHandler ["http-bio-8080"] 2011-11-29 17:39:52
>>>> org.apache.coyote.AbstractProtocol stop INFO: Stopping
>>>> ProtocolHandler ["ajp-bio-8009"] 2011-11-29 17:39:52
>>>> org.apache.coyote.AbstractProtocol destroy INFO: Destroying
>>>> ProtocolHandler ["http-bio-8080"] 2011-11-29 17:39:52
>>>> org.apache.coyote.AbstractProtocol destroy INFO: Destroying
>>>> ProtocolHandler ["ajp-bio-8009"]
>>>>
>>>>
>>>> Then server stops.
> 
> That looks like an orderly shutdown of Tomcat.
> 
>>>> On old machine it works perfect without any problems. I speak with
>>>> my administrator and i get information that this server is a
>>>> virtualization on XEN, and with IP they change procesor of hub
>>>> machine, but it shouldnt make difrence to xen virtusalization
>>>> server.
> 
> I wouldn't expect Tomcat (or the JVM, really) to get upset with an IP
> change at runtime, unless you had bound to an interface that suddenly
> disappeared (like you bind to 10.1.1.10 and suddenly that goes away).
> My expectation under those circumstances would be that the process
> just continues and never sees any connections after the IP change.
> 
> It looks more like your service was intentionally shut down.
> 
> Are there any other logs?
> 
> -chris
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 

-- 

[key:62590808]


Re: Tomcat 5.5 crashes after changing server IP

Posted by si...@8host.pl.
One more log:

2011-12-12 00:52:15 org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal 
performance in production environments was not found on the 
java.library.path: 
/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/server:/usr/lib/jvm/java-1$
2011-12-12 00:52:16 org.apache.tomcat.util.digester.Digester endElement
WARNING:   No rules found matching 'Server/Service/Context'.
2011-12-12 00:52:16 org.apache.tomcat.util.digester.SetPropertiesRule 
begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting 
property 'debug' to '0' did not find a matching property.
2011-12-12 00:52:16 org.apache.tomcat.util.digester.SetPropertiesRule 
begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} 
Setting property 'debug' to '0' did not find a matching property.
2011-12-12 00:52:16 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
2011-12-12 00:52:16 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1020 ms
2011-12-12 00:52:16 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
2011-12-12 00:52:16 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.32
2011-12-12 00:52:17 org.apache.catalina.loader.WebappClassLoader 
validateJarFile
INFO: validateJarFile(/var/www/torun/WEB-INF/lib/servletapi-2.2.jar) - 
jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: 
javax/servlet/Servlet.class
2011-12-12 00:52:18 org.apache.catalina.startup.HostConfig 
deployDescriptor
INFO: Deploying configuration descriptor host-manager.xml
2011-12-12 00:52:18 org.apache.catalina.startup.HostConfig 
deployDescriptor
INFO: Deploying configuration descriptor manager.xml
2011-12-12 00:52:18 org.apache.catalina.startup.HostConfig 
deployDirectory
INFO: Deploying web application directory docs
2011-12-12 00:52:18 org.apache.catalina.startup.HostConfig 
deployDirectory
INFO: Deploying web application directory ROOT
2011-12-12 00:52:18 org.apache.catalina.startup.HostConfig 
deployDirectory
INFO: Deploying web application directory examples
2011-12-12 00:52:18 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
2011-12-12 00:52:18 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
2011-12-12 00:52:18 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/10  config=null
2011-12-12 00:52:18 org.apache.catalina.startup.Catalina start
INFO: Server startup in 1976 ms
2011-12-12 00:53:09 org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8080
2011-12-12 00:53:10 org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
2011-12-12 00:53:10 org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 1 instance(s) to be deallocated
2011-12-12 00:53:11 org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 1 instance(s) to be deallocated
2011-12-12 00:53:12 org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 1 instance(s) to be deallocated
2011-12-12 00:53:12 org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [] is still processing a request that has 
yet to finish. This is very likely to create a memory leak. You can 
control the time allowed for requests to finish by using the unloadDelay 
attribute of the standard$
2011-12-12 00:53:12 org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080


It is probly Tomcat + Xen (KVM) + Intel (?) releted problem. I install 
tomcat from 5 to 7 on diferent VPS's, always have the same result but 
always i have Xen or KVM and Intel CPU, old serwer has AMD cpu and all 
works great (and some older version of Xen also), but on new Xen or KVM 
based VPS i always have the same problem. But when i run XEN machine 
with Windows 8 and run on it VirtuaBox and starts new 32 bit CentOS all 
work great (but i have virtualization on virtualized machine ;) ). Its 
realy strange problem, and have no idea how to solve it.

Best wishes,
Marcin


On 29.11.2011 23:05, Christopher Schultz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Sirwiz,
>
> On 11/29/11 11:51 AM, sirwiz@8host.pl wrote:
>> I can run tomcat with examples scripts (i just install t 7.0.23)
>> and i have this error:
>>
>> 2011-11-29 17:38:43 org.apache.coyote.AbstractProtocol start INFO:
>> Starting ProtocolHandler ["http-bio-8080"] 2011-11-29 17:38:43
>> org.apache.coyote.AbstractProtocol start INFO: Starting
>> ProtocolHandler ["ajp-bio-8009"] 2011-11-29 17:38:43
>> org.apache.catalina.startup.Catalina start INFO: Server startup in
>> 645 ms 2011-11-29 17:39:50 org.apache.coyote.AbstractProtocol
>> pause INFO: Pausing ProtocolHandler ["http-bio-8080"] 2011-11-29
>> 17:39:50 org.apache.coyote.AbstractProtocol pause INFO: Pausing
>> ProtocolHandler ["ajp-bio-8009"] 2011-11-29 17:39:50
>> org.apache.catalina.core.StandardService stopInternal INFO:
>> Stopping service Catalina 2011-11-29 17:39:50
>> org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 1
>> instance(s) to be deallocated 2011-11-29 17:39:51
>> org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 1
>> instance(s) to be deallocated 2011-11-29 17:39:52
>> org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 1
>> instance(s) to be deallocated 2011-11-29 17:39:52
>> org.apache.catalina.loader.WebappClassLoader
>> clearReferencesThreads SEVERE: The web application [] is still
>> processing a request that has yet to finish. This is very likely to
>> create a memory leak. You can control the time allowed for $
>> 2011-11-29 17:39:52 org.apache.coyote.AbstractProtocol stop INFO:
>> Stopping ProtocolHandler ["http-bio-8080"] 2011-11-29 17:39:52
>> org.apache.coyote.AbstractProtocol stop INFO: Stopping
>> ProtocolHandler ["ajp-bio-8009"] 2011-11-29 17:39:52
>> org.apache.coyote.AbstractProtocol destroy INFO: Destroying
>> ProtocolHandler ["http-bio-8080"] 2011-11-29 17:39:52
>> org.apache.coyote.AbstractProtocol destroy INFO: Destroying
>> ProtocolHandler ["ajp-bio-8009"]
>>
>>
>> Then server stops.
>
> That looks like an orderly shutdown of Tomcat.
>
>> On old machine it works perfect without any problems. I speak with
>> my administrator and i get information that this server is a
>> virtualization on XEN, and with IP they change procesor of hub
>> machine, but it shouldnt make difrence to xen virtusalization
>> server.
>
> I wouldn't expect Tomcat (or the JVM, really) to get upset with an IP
> change at runtime, unless you had bound to an interface that suddenly
> disappeared (like you bind to 10.1.1.10 and suddenly that goes away).
> My expectation under those circumstances would be that the process
> just continues and never sees any connections after the IP change.
>
> It looks more like your service was intentionally shut down.
>
> Are there any other logs?
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk7VVyYACgkQ9CaO5/Lv0PBTVwCeL+lnxoQV1J2yiYn9F0nsqOLU
> Zs0AnjuGeBtmSdp7lZFmpz0mznsd/9S5
> =sOXj
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org


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


Re: Tomcat 5.5 crashes after changing server IP

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

Sirwiz,

On 11/29/11 11:51 AM, sirwiz@8host.pl wrote:
> I can run tomcat with examples scripts (i just install t 7.0.23)
> and i have this error:
> 
> 2011-11-29 17:38:43 org.apache.coyote.AbstractProtocol start INFO:
> Starting ProtocolHandler ["http-bio-8080"] 2011-11-29 17:38:43
> org.apache.coyote.AbstractProtocol start INFO: Starting
> ProtocolHandler ["ajp-bio-8009"] 2011-11-29 17:38:43
> org.apache.catalina.startup.Catalina start INFO: Server startup in
> 645 ms 2011-11-29 17:39:50 org.apache.coyote.AbstractProtocol
> pause INFO: Pausing ProtocolHandler ["http-bio-8080"] 2011-11-29
> 17:39:50 org.apache.coyote.AbstractProtocol pause INFO: Pausing
> ProtocolHandler ["ajp-bio-8009"] 2011-11-29 17:39:50
> org.apache.catalina.core.StandardService stopInternal INFO:
> Stopping service Catalina 2011-11-29 17:39:50
> org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 1
> instance(s) to be deallocated 2011-11-29 17:39:51
> org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 1
> instance(s) to be deallocated 2011-11-29 17:39:52
> org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 1
> instance(s) to be deallocated 2011-11-29 17:39:52
> org.apache.catalina.loader.WebappClassLoader 
> clearReferencesThreads SEVERE: The web application [] is still
> processing a request that has yet to finish. This is very likely to
> create a memory leak. You can control the time allowed for $ 
> 2011-11-29 17:39:52 org.apache.coyote.AbstractProtocol stop INFO:
> Stopping ProtocolHandler ["http-bio-8080"] 2011-11-29 17:39:52
> org.apache.coyote.AbstractProtocol stop INFO: Stopping
> ProtocolHandler ["ajp-bio-8009"] 2011-11-29 17:39:52
> org.apache.coyote.AbstractProtocol destroy INFO: Destroying
> ProtocolHandler ["http-bio-8080"] 2011-11-29 17:39:52
> org.apache.coyote.AbstractProtocol destroy INFO: Destroying
> ProtocolHandler ["ajp-bio-8009"]
> 
> 
> Then server stops.

That looks like an orderly shutdown of Tomcat.

> On old machine it works perfect without any problems. I speak with
> my administrator and i get information that this server is a
> virtualization on XEN, and with IP they change procesor of hub 
> machine, but it shouldnt make difrence to xen virtusalization
> server.

I wouldn't expect Tomcat (or the JVM, really) to get upset with an IP
change at runtime, unless you had bound to an interface that suddenly
disappeared (like you bind to 10.1.1.10 and suddenly that goes away).
My expectation under those circumstances would be that the process
just continues and never sees any connections after the IP change.

It looks more like your service was intentionally shut down.

Are there any other logs?

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

iEYEARECAAYFAk7VVyYACgkQ9CaO5/Lv0PBTVwCeL+lnxoQV1J2yiYn9F0nsqOLU
Zs0AnjuGeBtmSdp7lZFmpz0mznsd/9S5
=sOXj
-----END PGP SIGNATURE-----

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


Re: Tomcat 5.5 crashes after changing server IP

Posted by si...@8host.pl.
I can run tomcat with examples scripts (i just install t 7.0.23) and i
have this error:

2011-11-29 17:38:43 org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
2011-11-29 17:38:43 org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
2011-11-29 17:38:43 org.apache.catalina.startup.Catalina start
INFO: Server startup in 645 ms
2011-11-29 17:39:50 org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-8080"]
2011-11-29 17:39:50 org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["ajp-bio-8009"]
2011-11-29 17:39:50 org.apache.catalina.core.StandardService 
stopInternal
INFO: Stopping service Catalina
2011-11-29 17:39:50 org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 1 instance(s) to be deallocated
2011-11-29 17:39:51 org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 1 instance(s) to be deallocated
2011-11-29 17:39:52 org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 1 instance(s) to be deallocated
2011-11-29 17:39:52 org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [] is still processing a request that has 
yet to finish. This is very likely to create a memory leak. You can 
control the time allowed for $
2011-11-29 17:39:52 org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-bio-8080"]
2011-11-29 17:39:52 org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["ajp-bio-8009"]
2011-11-29 17:39:52 org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["http-bio-8080"]
2011-11-29 17:39:52 org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["ajp-bio-8009"]


Then server stops. On old machine it works perfect without any 
problems. I speak with my administrator and i get information that this 
server is a virtualization on XEN, and with IP they change procesor of 
hub machine, but it shouldnt make difrence to xen virtusalization 
server.


Any ideas?





On 26.11.2011 16:41, Pid wrote:
> On 26/11/2011 15:19, Christopher Schultz wrote:
>> Sirwiz,
>>
>> On 11/25/11 10:16 PM, sirwiz@8host.pl wrote:
>>> 2011-11-26 00:42:34 org.apache.catalina.core.AprLifecycleListener
>>> init INFO: The APR based Apache Tomcat Native library which allows
>>> optimal performance in production environments was not found on
>>> the java.library.path:
>>> 
>>> /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/server:/usr/lib/jvm/java-1$
>>
>>>  2011-11-26 00:42:34
>>> org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING:
>>> [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
>>> 'debug' to '0' did not find a matching property. 2011-11-26
>>> 00:42:34 org.apache.tomcat.util.digester.SetPropertiesRule begin
>>> WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context}
>>> Setting property 'debug' to '0' did not find a matching property.
>>
>> Looks like you are using an old server.xml with a new version of
>> Tomcat. Don't do that. Instead, start with the stock server.xml that
>> comes with Tomcat 6 (or 7? It's unclear which one you are using) and
>> add whatever settings you need (like <Connectors> and <Hosts>) that
>> you need.
>>
>> After you are using an appropriate configuration, we'll take another
>> look at the log files.
>
> Also: defining Context in server.xml is now strongly discouraged.
>
> Does your mod_proxy_ajp config actually forward any requests to 
> Tomcat?
> I didn't see any uncommented ProxyPass statements there.
>
>
> p


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


Re: Tomcat 5.5 crashes after changing server IP

Posted by Pid <pi...@pidster.com>.
On 26/11/2011 15:19, Christopher Schultz wrote:
> Sirwiz,
> 
> On 11/25/11 10:16 PM, sirwiz@8host.pl wrote:
>> 2011-11-26 00:42:34 org.apache.catalina.core.AprLifecycleListener
>> init INFO: The APR based Apache Tomcat Native library which allows
>> optimal performance in production environments was not found on
>> the java.library.path: 
>> /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/server:/usr/lib/jvm/java-1$
> 
>>  2011-11-26 00:42:34
>> org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING:
>> [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
>> 'debug' to '0' did not find a matching property. 2011-11-26
>> 00:42:34 org.apache.tomcat.util.digester.SetPropertiesRule begin 
>> WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context}
>> Setting property 'debug' to '0' did not find a matching property.
> 
> Looks like you are using an old server.xml with a new version of
> Tomcat. Don't do that. Instead, start with the stock server.xml that
> comes with Tomcat 6 (or 7? It's unclear which one you are using) and
> add whatever settings you need (like <Connectors> and <Hosts>) that
> you need.
> 
> After you are using an appropriate configuration, we'll take another
> look at the log files.

Also: defining Context in server.xml is now strongly discouraged.

Does your mod_proxy_ajp config actually forward any requests to Tomcat?
I didn't see any uncommented ProxyPass statements there.


p

-- 

[key:62590808]


Re: Tomcat 5.5 crashes after changing server IP

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

Sirwiz,

On 11/25/11 10:16 PM, sirwiz@8host.pl wrote:
> 2011-11-26 00:42:34 org.apache.catalina.core.AprLifecycleListener
> init INFO: The APR based Apache Tomcat Native library which allows
> optimal performance in production environments was not found on
> the java.library.path: 
> /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/server:/usr/lib/jvm/java-1$
>
>  2011-11-26 00:42:34
> org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING:
> [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
> 'debug' to '0' did not find a matching property. 2011-11-26
> 00:42:34 org.apache.tomcat.util.digester.SetPropertiesRule begin 
> WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context}
> Setting property 'debug' to '0' did not find a matching property.

Looks like you are using an old server.xml with a new version of
Tomcat. Don't do that. Instead, start with the stock server.xml that
comes with Tomcat 6 (or 7? It's unclear which one you are using) and
add whatever settings you need (like <Connectors> and <Hosts>) that
you need.

After you are using an appropriate configuration, we'll take another
look at the log files.

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

iEYEARECAAYFAk7RA4UACgkQ9CaO5/Lv0PB7mQCbBc2+9ssTeUArtMCjzYPKYpP9
GJUAn1bWmCqrRl1NrUwMg16Lz+07N5Dg
=Y0HZ
-----END PGP SIGNATURE-----

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


RE: Tomcat 5.5 crashes after changing server IP

Posted by si...@8host.pl.
Tomcat log:

2011-11-26 00:42:34 org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal 
performance in production environments was not found on the 
java.library.path: 
/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/server:/usr/lib/jvm/java-1$
2011-11-26 00:42:34 org.apache.tomcat.util.digester.SetPropertiesRule 
begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting 
property 'debug' to '0' did not find a matching property.
2011-11-26 00:42:34 org.apache.tomcat.util.digester.SetPropertiesRule 
begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} 
Setting property 'debug' to '0' did not find a matching property.
2011-11-26 00:42:35 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
2011-11-26 00:42:35 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1130 ms
2011-11-26 00:42:35 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
2011-11-26 00:42:35 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.32
2011-11-26 00:42:36 org.apache.catalina.loader.WebappClassLoader 
validateJarFile
INFO: validateJarFile(/var/www/torun/WEB-INF/lib/servletapi-2.2.jar) - 
jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: 
javax/servlet/Servlet.class
2011-11-26 00:42:36 org.apache.catalina.startup.HostConfig 
deployDescriptor
INFO: Deploying configuration descriptor host-manager.xml
2011-11-26 00:42:36 org.apache.catalina.startup.HostConfig 
deployDescriptor
INFO: Deploying configuration descriptor manager.xml
2011-11-26 00:42:36 org.apache.catalina.startup.HostConfig 
deployDirectory
INFO: Deploying web application directory docs
2011-11-26 00:42:37 org.apache.catalina.startup.HostConfig 
deployDirectory
INFO: Deploying web application directory ROOT
2011-11-26 00:42:37 org.apache.catalina.startup.HostConfig 
deployDirectory
INFO: Deploying web application directory examples
2011-11-26 00:42:37 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
2011-11-26 00:42:38 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
2011-11-26 00:42:38 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/55  config=null
2011-11-26 00:42:38 org.apache.catalina.startup.Catalina start
INFO: Server startup in 2926 ms
2011-11-26 00:43:44 org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8080
2011-11-26 00:43:45 org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
2011-11-26 00:43:45 org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 1 instance(s) to be deallocated
2011-11-26 00:43:46 org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 1 instance(s) to be deallocated
2011-11-26 00:43:47 org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 1 instance(s) to be deallocated
2011-11-26 00:43:47 org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [] is still processing a request that has 
yet to finish. This is very likely to create a memory leak. You can 
control the time allowed for requests to finish by using the unloadDelay 
attribute of the standard$
2011-11-26 00:43:47 org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080


server.xml:

<?xml version='1.0' encoding='utf-8'?>
<!--
   Licensed to the Apache Software Foundation (ASF) under one or more
   contributor license agreements.  See the NOTICE file distributed with
   this work for additional information regarding copyright ownership.
   The ASF licenses this file to You under the Apache License, Version 
2.0
   (the "License"); you may not use this file except in compliance with
   the License.  You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 
implied.
   See the License for the specific language governing permissions and
   limitations under the License.
-->
<!-- Note:  A "Server" is not itself a "Container", so you may not
      define subcomponents such as "Valves" at this level.
      Documentation at /docs/config/server.html
  -->
<Server port="8005" shutdown="SHUTDOWN">

   <!--APR library loader. Documentation at /docs/apr.html -->
   <Listener className="org.apache.catalina.core.AprLifecycleListener" 
SSLEngine="on" />
   <!--Initialize Jasper prior to webapps are loaded. Documentation at 
/docs/jasper-howto.html -->
   <Listener className="org.apache.catalina.core.JasperListener" />
   <!-- Prevent memory leaks due to use of particular java/javax APIs-->
   <Listener 
className="org.apache.catalina.core.JreMemoryLeakPreventionListener" />
   <!-- JMX Support for the Tomcat server. Documentation at 
/docs/non-existent.html -->
   <Listener 
className="org.apache.catalina.mbeans.ServerLifecycleListener" />
   <Listener 
className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" 
/>

   <!-- Global JNDI resources
        Documentation at /docs/jndi-resources-howto.html
   -->
   <GlobalNamingResources>
     <!-- Editable user database that can also be used by
          UserDatabaseRealm to authenticate users
     -->
     <Resource name="UserDatabase" auth="Container"
               type="org.apache.catalina.UserDatabase"
               description="User database that can be updated and saved"
               
factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
               pathname="conf/tomcat-users.xml" />
   </GlobalNamingResources>

   <!-- A "Service" is a collection of one or more "Connectors" that 
share
        a single "Container" Note:  A "Service" is not itself a 
"Container",
        so you may not define subcomponents such as "Valves" at this 
level.
        Documentation at /docs/config/service.html
    -->
   <Service name="Catalina">

     <!--The connectors can use a shared executor, you can define one or 
more named thread pools-->
     <!--
     <Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
         maxThreads="150" minSpareThreads="4"/>
     -->


     <!-- A "Connector" represents an endpoint by which requests are 
received
          and responses are returned. Documentation at :
          Java HTTP Connector: /docs/config/http.html (blocking & 
non-blocking)
          Java AJP  Connector: /docs/config/ajp.html
          APR (HTTP/AJP) Connector: /docs/apr.html
          Define a non-SSL HTTP/1.1 Connector on port 8080
     -->
     <Connector port="8080" protocol="HTTP/1.1"
                connectionTimeout="20000"
                redirectPort="8443" />
     <!-- A "Connector" using the shared thread pool-->
     <!--
     <Connector executor="tomcatThreadPool"
                port="8080" protocol="HTTP/1.1"
                connectionTimeout="20000"
                redirectPort="8443" />
     -->
     <!-- Define a SSL HTTP/1.1 Connector on port 8443
          This connector uses the JSSE configuration, when using APR, 
the
          connector should be using the OpenSSL style configuration
          described in the APR documentation -->
     <!--
     <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
                maxThreads="150" scheme="https" secure="true"
                clientAuth="false" sslProtocol="TLS" />
     -->

     <!-- Define an AJP 1.3 Connector on port 8009 -->
     <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" />


     <!-- An Engine represents the entry point (within Catalina) that 
processes
          every request.  The Engine implementation for Tomcat stand 
alone
          analyzes the HTTP headers included with the request, and 
passes them
          on to the appropriate Host (virtual host).
          Documentation at /docs/config/engine.html -->

     <!-- You should set jvmRoute to support load-balancing via AJP ie :
     <Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1">
     -->
     <Engine name="Catalina" defaultHost="localhost">

       <!--For clustering, please take a look at documentation at:
           /docs/cluster-howto.html  (simple how to)
           /docs/config/cluster.html (reference documentation) -->
       <!--
       <Cluster 
className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/>
       -->

       <!-- The request dumper valve dumps useful debugging information 
about
            the request and response data received and sent by Tomcat.
            Documentation at: /docs/config/valve.html -->
       <!--
       <Valve 
className="org.apache.catalina.valves.RequestDumperValve"/>
       -->

       <!-- This Realm uses the UserDatabase configured in the global 
JNDI
            resources under the key "UserDatabase".  Any edits
            that are performed against this UserDatabase are immediately
            available for use by the Realm.  -->
       <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
              resourceName="UserDatabase"/>

       <!-- Define the default virtual host
            Note: XML Schema validation will not work with Xerces 2.2.
        -->
       <Host name="localhost"  appBase="webapps"
             unpackWARs="true" autoDeploy="true"
             xmlValidation="false" xmlNamespaceAware="false">

         <!-- SingleSignOn valve, share authentication between web 
applications
              Documentation at: /docs/config/valve.html -->
         <!--
         <Valve 
className="org.apache.catalina.authenticator.SingleSignOn" />
         -->

         <!-- Access log processes all example.
              Documentation at: /docs/config/valve.html -->
         <!--
         <Valve className="org.apache.catalina.valves.AccessLogValve" 
directory="logs"
                prefix="localhost_access_log." suffix=".txt" 
pattern="common" resolveHosts="false"/>
         -->

       </Host>

       <Host name="xxxx.xxxx.xxxx.pl" debug="0" appBase="webapps/common" 
unpackWARs="true" autoDeploy="true">
                <Alias>xxxxxx.pl</Alias>
                                     <Context path="" 
docBase="/var/www/torun" debug="0" reloadable="false" 
crossContext="false">
                                                                      
</Context>
                                                                         
                                      </Host>

     </Engine>
   </Service>
</Server>


proxy_ajp.conf:


LoadModule proxy_ajp_module modules/mod_proxy_ajp.so

#
# When loaded, the mod_proxy_ajp module adds support for
# proxying to an AJP/1.3 backend server (such as Tomcat).
# To proxy to an AJP backend, use the "ajp://" URI scheme;
# Tomcat is configured to listen on port 8009 for AJP requests
# by default.
#

#
# Uncomment the following lines to serve the ROOT webapp
# under the /tomcat/ location, and the jsp-examples webapp
# under the /examples/ location.
#
#ProxyPass /tomcat/ ajp://localhost:8009/
#ProxyPass /examples/ ajp://localhost:8009/jsp-examples/



Can you access Tomcat directly?


No, after changing IP i cant.

Thx

Marcin





On 26.11.2011 02:44, Caldarale, Charles R wrote:
>> From: sirwiz@8host.pl [mailto:sirwiz@8host.pl]
>> Subject: Tomcat 5.5 crashes after changing server IP
>
>> Hi, i recently move server to new IP, since this change ive got
>> permanently this error, i tryed everything but im fail.
>
>> [Fri Nov 25 23:56:29 2011] [notice] SELinux policy enabled; httpd
>> running as context root:system_r:httpd_t:s0
>
> Nice of you to show us the httpd logs, but since you're reporting a
> problem with Tomcat, wouldn't it be more appropriate to send the
> Tomcat logs?  Would also be good to see your server.xml and the
> mod_proxy_ajp config.
>
> Can you access Tomcat directly?
>
>  - 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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: Tomcat 5.5 crashes after changing server IP

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: sirwiz@8host.pl [mailto:sirwiz@8host.pl] 
> Subject: Tomcat 5.5 crashes after changing server IP

> Hi, i recently move server to new IP, since this change ive got 
> permanently this error, i tryed everything but im fail.

> [Fri Nov 25 23:56:29 2011] [notice] SELinux policy enabled; httpd 
> running as context root:system_r:httpd_t:s0

Nice of you to show us the httpd logs, but since you're reporting a problem with Tomcat, wouldn't it be more appropriate to send the Tomcat logs?  Would also be good to see your server.xml and the mod_proxy_ajp config.

Can you access Tomcat directly?

 - 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.