RE: mod_jk 1.2.28 errors
André, thanks for the suggestions.
I removed all the time outs except for connection_pool_timeout which I set to
120. I changed the connectionTimeout to 12 and maxThreads to 200 in
server.xml. Things are running much smoother now than before. I still see the
error messages but less frequently than before. I used to see the messages
every 1 to 2 minutes, now it is between 5 minutes and 1 hour.
Where to go from here? How do I determine which timeout needs to be adjusted?
Another more serious issue that I have not solved is the sudden surge of http
connections, from ~30 to over 200 in a matter of few seconds causing all kind
of read timeout and service unavailable errors.
Any suggestions to how to go about fixing or determining the root cause of
either of the two issues?
Here are the latest configurations:
--- workers.properties-
worker.list=loadbl,status
worker.template.port=8009
worker.template.type=ajp13
worker.template.lbfactor=1
worker.template.ping_mode=A
worker.template.connection_pool_timeout=120
worker.worker1.reference=worker.template
worker.worker1.host=jboss_server1
worker.worker2.reference=worker.template
worker.worker2.host= jboss_server2
worker.loadbl.type=lb
worker.loadbl.balance_workers=worker1,worker2
worker.loadbl.sticky_session=True
worker.status.type=status
server.xml --
!-- Define an AJP 1.3 Connector on port 8009 --
Connector port=8009 address=${jboss.bind.address} protocol=AJP/1.3
emptySessionPath=true enableLookups=false redirectPort=8443
maxThreads=200 connectionTimeout=12/
-
-- error messages --
[Thu Oct 28 05:51:57 2010][19938:3086886672] [info]
ajp_service::jk_ajp_common.c (2540): (worker1) sending request to tomcat failed
(unrecoverable), because of client write error (attempt=1)
[Thu Oct 28 05:51:57 2010][19938:3086886672] [info] service::jk_lb_worker.c
(1388): service failed, worker worker1 is in local error state
[Thu Oct 28 05:51:57 2010][19938:3086886672] [info] service::jk_lb_worker.c
(1407): unrecoverable error 200, request failed. Client failed in the middle of
request, we can't recover to another instance.
[Thu Oct 28 05:51:57 2010][19938:3086886672] [info] jk_handler::mod_jk.c
(2611): Aborting connection for worker=loadbl
[Thu Oct 28 06:03:06 2010][27490:3086886672] [info]
ajp_process_callback::jk_ajp_common.c (1882): Writing to client aborted or
client network problems
[Thu Oct 28 06:03:06 2010][27490:3086886672] [info]
ajp_service::jk_ajp_common.c (2540): (worker1) sending request to tomcat failed
(unrecoverable), because of client write error (attempt=1)
[Thu Oct 28 06:03:06 2010][27490:3086886672] [info] service::jk_lb_worker.c
(1388): service failed, worker worker1 is in local error state
[Thu Oct 28 06:03:06 2010][27490:3086886672] [info] service::jk_lb_worker.c
(1407): unrecoverable error 200, request failed. Client failed in the middle of
request, we can't recover to another instance.
[Thu Oct 28 06:03:06 2010][27490:3086886672] [info] jk_handler::mod_jk.c
(2611): Aborting connection for worker=loadbl
[Thu Oct 28 06:38:49 2010][25752:3086886672] [info]
ajp_handle_cping_cpong::jk_ajp_common.c (879): timeout in reply cpong
[Thu Oct 28 06:38:51 2010][25752:3086886672] [info]
ajp_send_request::jk_ajp_common.c (1518): (worker1) failed sending request,
socket -1 prepost cping/cpong failure (errno=110)
[Thu Oct 28 06:38:51 2010][25752:3086886672] [info]
ajp_send_request::jk_ajp_common.c (1574): (worker1) all endpoints are
disconnected, detected by connect check (0), cping (1), send (0)
Thanks,
-mo
-Original Message-
From: André Warnier [mailto:a...@ice-sa.com]
Sent: Tuesday, October 26, 2010 3:15 AM
To: Tomcat Users List
Subject: Re: mod_jk 1.2.28 errors
Pid wrote:
On 26/10/2010 00:05, Hannaoui, Mo wrote:
...
worker.template.ping_mode=A
worker.template.reply_timeout=3
worker.template.socket_connect_timeout=1
worker.template.socket_timeout=10
worker.template.connection_pool_timeout=600
I can't get to the jk docs docs at the moment, but that socket_timeout
seems a little low. Are those the defaults?
1) What happens when you just leave the line
worker.template.ping_mode=A
and *remove* all the other timeout-related lines (to let the defaults be
configured) ?
2) About the Tomcat-side configuration :
!-- Define an AJP 1.3 Connector on port 8009 --
Connector port=8009 address=${jboss.bind.address}
protocol=AJP/1.3
emptySessionPath=true enableLookups=false
redirectPort=8443
maxThreads=800 connectionTimeout=60/
You have MaxClients=250 at the Apache side, and maxThreads=800 at the Tomcat
side (2
times, because 2 Tomcats). Unless each Apache client can issue several
requests to
Tomcat(s) at the same time, that seems a bit unbalanced.
Also, connectionTimeout=60 means that when a client makes a connection
but does not
send a
Can't disable caching of static content
Hi, For some reason Tomcat keeps caching my static content even though I've set the cachingAllowed attribute to false. I've set the following attributes in %CATALINA_HOME%\conf\Catalina\localhost\myContext.xml: Context path=/myContext cachingAllowed=false reloadable=true crossContext=false antiJARLocking=true antiResourceLocking=true ... /Context I even tried to apply the settings to the %CATALINA_HOME%\conf\context.xml. Unfortunately, to no avail. Wat am I missing here? I'm running Tomcat 6.0.24 on Win XP. Thanks in advance, Alex - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Can't disable caching of static content
2010/10/28 Alexander Rosemann alexander.rosem...@gmail.com: Hi, For some reason Tomcat keeps caching my static content even though I've set the cachingAllowed attribute to false. I've set the following attributes in %CATALINA_HOME%\conf\Catalina\localhost\myContext.xml: Context path=/myContext cachingAllowed=false reloadable=true crossContext=false antiJARLocking=true antiResourceLocking=true ... /Context I even tried to apply the settings to the %CATALINA_HOME%\conf\context.xml. Unfortunately, to no avail. Wat am I missing here? I'm running Tomcat 6.0.24 on Win XP. What are your evidences? Note that, because of those anti** options in your Context, your content is copied to some temporary directory and is served from there and not from webapp/appname. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
session data in distributed env
Hi All! I put distributable/ in the web.xml and made all session data serializable. Application deployed successfuly but when when request jumping from one node to another looks like all data stored in session is lost, i c only default values. server.xml: Connector port=9011 protocol=AJP/1.3 emptySessionPath=true crossContext=true/ Engine name=Catalina defaultHost=localhost jvmRoute=cl1 Cluster className=org.apache.catalina.cluster.tcp.SimpleTcpCluster/ Realm className=org.apache.catalina.realm.UserDatabaseRealm resourceName=UserDatabase / Host name=localhost appBase=webapps / /Engine I really dont understand whats happening. Any ideas ? Thanks PS: its all about tomcat-5.5 -- If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby Digital and all the music is free... pgp5VWbmbo6M2.pgp Description: PGP signature
Re: mod_jk 1.2.28 errors
On 26.10.2010 01:05, Hannaoui, Mo wrote:
1. When there are 30 http connections, I see the error below almost
every 1 minute. As the traffic and the number of connections increase,
the frequency of error increases and the performance of the web
application that is being hosted on the system decreases.
[Mon Oct 25 20:59:42 2010][11224:3086337808] [info]
ajp_process_callback::jk_ajp_common.c (1882): Writing to client aborted
or client network problems
This error tells us, that during sending the response back to the
browser a problem was detected. Most likely a connction abort or similar.
This will happen every now and then when users do not wait for a
response and instead proceed clicking on other links. If it happens to
often, then it might indicate that either your application is not
responsive enough, so users have a reason to start clicking while
waiting, or you might have an infrastrutural problem on the way back to
the browser.
Note that the messages are only flagged as [info], because as said
occasional occurence is not problematic.
If you want to decie, whether this is happening due to bad performance,
you should
- add %P %{tid}P %D to your LogFormat for the Apache access log. This
will log the process id, the thread id (for prefork MPM that's always
1) and the duration in microseconds. You can use the pid and tid to
correlate with the jk log messages. In the jk log line it is
[11224:3086337808], the irst number is the pid, the second the tid.
Note that the timestamp in the access log is when the request started,
the time stamp in the JK log is when the response was detected as
broken. The delta should be roughly what is being loged as %D. Choose a
couple of occurances, find the counterparts in the access log and see,
whether they tok especially long. You can also look at what are the
URLs, the user agents, the client IPs etc., all via the access log.
- add an access log to Tomcat and do not forget to add %D to the log
pattern as well. Check whether the same, likely long running requests
also take long according to the Tomcat access log. Note that %D for
Tomcat logs milliseconds, not microseconds like for Apache.
If you find many examples, where Tomcat logs a short time and Apache a
long time, then you likely have a network/firwall/load-balancer/whatever
problem between Apache and the browser. Especially if file sizes are not
huge. In that case Tomcat will be able to stream back to Apache, which
will be able to put all of the response in the TCP send buffer, but
Apache will nevertheless log the error, if the content finally can not
be transmitted.
- next you can start sniffing to find out, what actually was the root
case from the point of view of Apache, e.g. whether a reset was sent by
the client. I did run into cases, where security devices every now and
then reset foreign connections for which they thought they looked like
an attack. Easy to detect with a network sniff: in that case the MAC
address from which the reset was sent was different form the mac address
that sent the rest of the connection packets.
- finally you can try to work your way close to the browser by doing
sniffs further up th enetwork.
2. The number of connections will suddenly surge from say 40 to 90 to
~200 in no time, at which point all I see in mod_jk.log is error
messages and the application either stops responding with the connection
refused or bad gateway error. To fix the problem the Jboss service
usually needs to be restated. This surge is unpredictable and may happen
between 1 and 5 times in 24 hours.
This indicates a prformance problem with the app (or GC problems).
Observed concurrance is roughly:
concurrancy = requests per second * average response time
If the concurrancy spikes, it is usualy actually the response time that
spikes. Add %D to the access logs to verify.
If so, start doing Java thread dumps to analyze what's happening in
JBoss. Also look at per thread CPU load using ps to check, whether there
are special thrads that take to much CPU. Finally check GC activity.
I have read many posts and documents (including
http://kbase.redhat.com/faq/docs/DOC-15866 and used
http://lbconfig.appspot.com/ for base configurations) and changed the
configurations many times, but the problem continues to exist. I think
my current configuration is the worst version so far. It works well only
with low traffic.
Here's the current configuration:
--- workers.properties
...
worker.template.reply_timeout=3
Might be a bit short. Check with your %D logged values. Please do also
add max_reply_timeouts to your load balancer.
...
worker.template.socket_timeout=10
I personally don't like the general socket_timeout. I do like the more
fine-grained individual timeouts.
The source download of mod_jk 1.2.30 contains a well-documented example
configuration (1.2.28 does not). Further official notes about timeouts
are available at:
session data in distributed env
Hi All! I put distributable/ in the web.xml and made all session data serializable. Application deployed successfuly but when when request jumping from one node to another looks like all data stored in session is lost, i c only default values. server.xml: Connector port=9011 protocol=AJP/1.3 emptySessionPath=true crossContext=true/ Engine name=Catalina defaultHost=localhost jvmRoute=cl1 Cluster className=org.apache.catalina.cluster.tcp.SimpleTcpCluster/ Realm className=org.apache.catalina.realm.UserDatabaseRealm resourceName=UserDatabase / Host name=localhost appBase=webapps / /Engine I really dont understand whats happening. Any ideas ? Thanks PS: its all about tomcat-5.5 -- If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby Digital and all the music is free... pgpqpcPkyok2Y.pgp Description: PGP signature
Re: Can't disable caching of static content
I simply changed a static HTML file. I haven't tried disabling all the other options though. Thanks for the hint. On Thu, Oct 28, 2010 at 11:05 AM, Konstantin Kolinko knst.koli...@gmail.com wrote: 2010/10/28 Alexander Rosemann alexander.rosem...@gmail.com: Hi, For some reason Tomcat keeps caching my static content even though I've set the cachingAllowed attribute to false. I've set the following attributes in %CATALINA_HOME%\conf\Catalina\localhost\myContext.xml: Context path=/myContext cachingAllowed=false reloadable=true crossContext=false antiJARLocking=true antiResourceLocking=true ... /Context I even tried to apply the settings to the %CATALINA_HOME%\conf\context.xml. Unfortunately, to no avail. Wat am I missing here? I'm running Tomcat 6.0.24 on Win XP. What are your evidences? Note that, because of those anti** options in your Context, your content is copied to some temporary directory and is served from there and not from webapp/appname. Best regards, Konstantin Kolinko - 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
session data in distributed env
Hi All! I put distributable/ in the web.xml and made all session data serializable. Application deployed successfuly but when when request jumping from one node to another looks like all data stored in session is lost, i c only default values. server.xml: Connector port=9011 protocol=AJP/1.3 emptySessionPath=true crossContext=true/ Engine name=Catalina defaultHost=localhost jvmRoute=cl1 Cluster className=org.apache.catalina.cluster.tcp.SimpleTcpCluster/ Realm className=org.apache.catalina.realm.UserDatabaseRealm resourceName=UserDatabase / Host name=localhost appBase=webapps / /Engine I really dont understand whats happening. Any ideas ? Thanks PS: its all about tomcat-5.5 -- If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby Digital and all the music is free... - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: How to start a daemon without getting the warning?
You should call timer.cancel() on context stop. You can do this from a
ServletContextListener.
Ronald.
Op woensdag, 27 oktober 2010 22:10 schreef Leon Rosenberg
rosenberg.l...@gmail.com:
Hello,
I'm getting following warning with 6.0.29,
after shutdown:
SEVERE: The web application [/moskitodemo] appears to have started a
thread named [MoskitoMemoryPoolReader] but has failed to stop it. This
is very likely to create a memory leak.
here's the snapshot of the code that starts the thread:
public class BuiltInMemoryPoolProducer implements IStatsProducer{
/**
* Timer instance for this producer type.
*/
private static final Timer timer = new Timer(MoskitoMemoryPoolReader,
true);
...
public BuiltInMemoryPoolProducer(MemoryPoolMXBean aPool){
timer.scheduleAtFixedRate(new TimerTask() {
@Override
public void run() {
readMemory();
}
}, 0, 1000L*60);
...}
to my knowledge this thread is a daemon. This knowledge is also shared
by jstack:
MoskitoMemoryPoolReader daemon prio=5 tid=10883f800 nid=0x11a9b2000
in Object.wait() [11a9b1000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on 10a1120d0 (a java.util.TaskQueue)
at java.util.TimerThread.mainLoop(Timer.java:509)
- locked 10a1120d0 (a java.util.TaskQueue)
at java.util.TimerThread.run(Timer.java:462)
So, how can I avoid this warning and where's the bug.
regards
Leon
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: mod_jk makes ajp connector run out of free connections
On 26.10.2010 20:36, Marc Wilmots wrote: 2010/10/26 Mladen Turkmt...@apache.org On 10/26/2010 02:47 PM, Marc Wilmots wrote: Hi Experts, I have the following setup: Apache1 / \ Apache2 Apache3 \ / Tomcat1 All Apaches are version 2.2.3 (RedHat) Apache2 and Apache3 loadbalance Tomcat1 (6.0.18) with mod_jk (2.2.28). In idle state the AJP connector of Tomcat1 only has 7 active connections. After launching a stress test of Tomcat1, it's AJP connector has reached maxThreads (200). After the stress test has finished, there are still 200 active connections in the AJP connector. Because of this, apache2 and apache2 cannot receive any heartbeat message anymore from the AJP connector and mark Tomcat1 as dead. I can access perfectly through port 8080, so Tomcat1 isn't dead at all! You have a usual setup problem where the number of connections in httpd fronting tomcat is too high for a tomcat. And you don't have any mechanism for limiting those connections. Sorry, I realize I had to mention I have a total of 4 Tomcats, which in total make up a maxThreads of 800 (200 each). The Apaches have a maxClients of each 600 (1200 total). 1200 1000, thus your theory is probably right. However, I'm just wondering... I read that when Tomcat reaches the max number of connections, just rejects new connections (I'm omitting the backlog on purpose). Yes. But your calculation above is not right. Each Apache will connect to each Tomcat. So from the point of view of one Tomcat, it has 200 threads, but 1200 posible incoming connections from the Apache Servers. So it is not 1200 800 but 1200 200! Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: ISAPI-Problem
On 27.10.2010 15:24, Jost Richstein wrote: Hi, I have the following problem on a Windows Server 2003 64Bit (AMD). Configuration: IIS 6, isapi_redirect.dll AMD64 Version 1.2.30, Tomcat 5.5.27, JDk 1.6.0_12 64Bit. I am using the following small worker.properties: ps=\ worker.list=ajp13 worker.ajp13.port=8010 worker.ajp13.host=localhost worker.ajp13.type=ajp13 worker.ajp13.connection_pool_size=500 My isapi_redirect.properties contains only (no other parameters set) extension_uri log_file log_level (error) worker_file worker_mount_file My Tomcat site works fine in general, there are up to 1.400 users active and the site answers requests very fast. However I have the following log entries every few minutes (sometimes every few seconds) in jk.log. Every time that pair of entries: [Wed Oct 27 12:15:37.764 2010] [3156:3284] [error] ajp_service::jk_ajp_common.c (2559): (ajp13) connecting to tomcat failed. [Wed Oct 27 12:15:37.811 2010] [3156:3284] [error] HttpExtensionProc::jk_isapi_plugin.c (2195): service() failed with http error 500 Increase your log_level to info. This will provide additional log lines directly before the ones you cited which contain more detailed information about the root cause. Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat Maven and Axis 1.5.1 problem
Hello, I am trying to deploy a webservice on tomcat that implements some axis wsdl2java work. However when I try to launch the code it gives an error in the line when I create an instance of auto-generated ServiceStub. The funny thing is that I am using Maven for building the project. And when maven compiles it it runs a TEST. During the test a tomcat server is launched and the project is deployed. And everything works doing fine there - no errors, the application connects correctly to another server, sending an attachment and getting the proper response - no problem. However when I take the var file and deploy it on a 'normal' tomcat I have the error: org.apache.axis2.deployment.DeploymentException: org.apache.axis2.transport.local.LocalTransportSender at org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:694) at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:121) at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:703) at org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:116) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:206) at org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:150) at org.apache.axis2.client.ServiceClient.init(ServiceClient.java:143) at com.mywebpack.rest.gencode.MywebappServiceStub.init(MywebappServiceStub.java:211) at com.mywebpack.rest.gencode.MywebappServiceStub.init(MywebappServiceStub.java:197) at com.mywebpack.rest.resources.MywebappImpl.init(MywebappImpl.java:86) at com.mywebpack.rest.resources.SearchResource.receiveWavestream(SearchResource.java:163) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:165) at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:67) at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:276) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:133) at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:83) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:133) at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:71) at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1171) at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1103) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1053) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1043) at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:406) at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:477) at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:662) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:873) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.ClassNotFoundException:
Re: Can't disable caching of static content
What are your evidences? Note that, because of those anti** options in your Context, your content is copied to some temporary directory and is served from there and not from webapp/appname. Best regards, Konstantin Kolinko Hi Konstantin, using *only* the cachingAllowed attribute is finally working. I finally can get rid of my proxy server for dev. purposes. Thanks, Alex - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat Maven and Axis 1.5.1 problem
Hello, I am trying to deploy a webservice on tomcat that implements some axis wsdl2java work. However when I try to launch the code it gives an error in the line when I create an instance of auto-generated ServiceStub. The funny thing is that I am using Maven for building the project. And when maven compiles it it runs a TEST. During the test a tomcat server is launched and the project is deployed. And everything works doing fine there - no errors, the application connects correctly to another server, sending an attachment and getting the proper response - no problem. However when I take the var file and deploy it on a 'normal' tomcat I have the error: org.apache.axis2.deployment.DeploymentException: org.apache.axis2.transport.local.LocalTransportSender at org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:694) at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:121) at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:703) at org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:116) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:206) at org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:150) at org.apache.axis2.client.ServiceClient.init(ServiceClient.java:143) at com.mywebpack.rest.gencode.MywebappServiceStub.init(MywebappServiceStub.java:211) at com.mywebpack.rest.gencode.MywebappServiceStub.init(MywebappServiceStub.java:197) at com.mywebpack.rest.resources.MywebappImpl.init(MywebappImpl.java:86) at com.mywebpack.rest.resources.SearchResource.receiveWavestream(SearchResource.java:163) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:165) at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:67) at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:276) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:133) at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:83) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:133) at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:71) at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1171) at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1103) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1053) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1043) at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:406) at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:477) at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:662) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:873) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.ClassNotFoundException:
how can i turn off This is very likely to create a memory leak.
Hello, I investigated an issue (another thread) with new error messages after tomcat update: SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoMemoryPoolReader] but has failed to stop it. This is very likely to create a memory leak. After some research and discussions with colleagues we came to the conclusion that this message is ... well not helping us. Is there a possibility to turn it off? Its annoying to have such messages in the logs after a server shutdown. For explanation: I'm not planing to use webapp reload in my environment, hence, this message is actually just spam. regards Leon - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: how can i turn off This is very likely to create a memory leak.
nevermind, found it, sorry for disturbing. On Thu, Oct 28, 2010 at 3:44 PM, Leon Rosenberg rosenberg.l...@gmail.com wrote: Hello, I investigated an issue (another thread) with new error messages after tomcat update: SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoMemoryPoolReader] but has failed to stop it. This is very likely to create a memory leak. After some research and discussions with colleagues we came to the conclusion that this message is ... well not helping us. Is there a possibility to turn it off? Its annoying to have such messages in the logs after a server shutdown. For explanation: I'm not planing to use webapp reload in my environment, hence, this message is actually just spam. regards Leon - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: how can i turn off This is very likely to create a memory leak.
ok, i revoke my nevermind message, even after I removed JreMemoryLeakPreventionListener I still get the warning. Even weirder: Oct 28, 2010 3:50:55 PM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [Poller SunPKCS11-Darwin] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoIntervalUpdater] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoMemoryReader] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoMemoryPoolReader] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoMemoryPoolReader] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [Thread-6] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:56 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8080 anyplace else except the server.xml to fix it? regards Leon On Thu, Oct 28, 2010 at 3:46 PM, Leon Rosenberg rosenberg.l...@gmail.com wrote: nevermind, found it, sorry for disturbing. On Thu, Oct 28, 2010 at 3:44 PM, Leon Rosenberg rosenberg.l...@gmail.com wrote: Hello, I investigated an issue (another thread) with new error messages after tomcat update: SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoMemoryPoolReader] but has failed to stop it. This is very likely to create a memory leak. After some research and discussions with colleagues we came to the conclusion that this message is ... well not helping us. Is there a possibility to turn it off? Its annoying to have such messages in the logs after a server shutdown. For explanation: I'm not planing to use webapp reload in my environment, hence, this message is actually just spam. regards Leon - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: how can i turn off This is very likely to create a memory leak.
On 28/10/10 14:53, Leon Rosenberg wrote: ok, i revoke my nevermind message, even after I removed JreMemoryLeakPreventionListener I still get the warning. Even weirder: Oct 28, 2010 3:50:55 PM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [Poller SunPKCS11-Darwin] but has failed to stop it. This is very likely to create a memory leak. Note the word 'likely' is not 'defiantly', it is possible that your implementation is 'not' creating a memory leak. If tomcat launches an independent thread (not a tomcat thread) that refers to objects within the tomcat instance (and its pool of threads), this is when a memory leak would occur. This is because objects referenced by the independent thread 'and' the tomcat instance would not be GC'ed when tomcat shuts down, because they are still referenced by a living thread. 'Generally' you will want to stop the independent threads when tomcat shuts down, thus removing the 'likelihood' of memory leaks. If the independent threads have their own shut down hooks that realise tomcat is shutting down and dereference any appropriate objects, a memory leak will 'not' occur. If you want your independent threads to shut down with tomcat because they do not have the own mechanisms, implement a ServletContextListener.contextDestroyed that does so. Regards, Simon Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoIntervalUpdater] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoMemoryReader] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoMemoryPoolReader] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoMemoryPoolReader] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [Thread-6] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:56 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8080 anyplace else except the server.xml to fix it? regards Leon On Thu, Oct 28, 2010 at 3:46 PM, Leon Rosenberg rosenberg.l...@gmail.com wrote: nevermind, found it, sorry for disturbing. On Thu, Oct 28, 2010 at 3:44 PM, Leon Rosenberg rosenberg.l...@gmail.com wrote: Hello, I investigated an issue (another thread) with new error messages after tomcat update: SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoMemoryPoolReader] but has failed to stop it. This is very likely to create a memory leak. After some research and discussions with colleagues we came to the conclusion that this message is ... well not helping us. Is there a possibility to turn it off? Its annoying to have such messages in the logs after a server shutdown. For explanation: I'm not planing to use webapp reload in my environment, hence, this message is actually just spam. regards Leon - 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
Late start of context
Hello, I need that when tomcat starts, some applications may not start until after a certain time (delay). For example: The application A starts after 20. minutes I've searched but nothing found Does anyone know if this is possible? Greetings and thanks -- -- Pedro Rodrigo Cardiel Dpto. de Informática e Ingeniería de Sistemas - Universidad de Zaragoza C/ María de Luna 1, 50018 Zaragoza, Spain Tel:+34 976 762134 e-mail: prod...@unizar.es Grupo IAAA - http://iaaa.cps.unizar.es -- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Late start of context
From: Pedro Rodrigo Cardiel [mailto:prod...@unizar.es] Subject: Late start of context I need that when tomcat starts, some applications may not start until after a certain time (delay). What do you expect to happen when requests arrive for the non-started webapp during the delay period? Generally, any synchronization with external events that the webapp may require is entirely the responsibility of the webapp. You can possibly achieve what you want with some external script that interfaces with the Tomcat manager app (text, not GUI, version) to start and stop a webapp. - 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.
RE: Late start of context
El jue, 28-10-2010 a las 09:46 -0500, Caldarale, Charles R escribió: What do you expect to happen when requests arrive for the non-started webapp during the delay period? Tomcat returns the same as when you stop an application Generally, any synchronization with external events that the webapp may require is entirely the responsibility of the webapp. You can possibly achieve what you want with some external script that interfaces with the Tomcat manager app (text, not GUI, version) to start and stop a webapp. The thing is that there are several heavy applications (the tomcat I have to throw with 2.7 GB of memory) that usually start badly. But if I re-launched by hand one by one then they are loaded properly. So I want to put time between tomcat start an application and again tomcat. -- -- Pedro Rodrigo Cardiel Dpto. de Informática e Ingeniería de Sistemas - Universidad de Zaragoza C/ María de Luna 1, 50018 Zaragoza, Spain Tel:+34 976 762134 e-mail: prod...@unizar.es Grupo IAAA - http://iaaa.cps.unizar.es --
RE: Late start of context
From: Pedro Rodrigo Cardiel [mailto:prod...@unizar.es] Subject: RE: Late start of context The thing is that there are several heavy applications (the tomcat I have to throw with 2.7 GB of memory) that usually start badly. But if I re-launched by hand one by one then they are loaded properly. I think your time would be better spent fixing the startup bugs in the webapps rather than attacking the symptom. - 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.
Re: Late start of context
On 10/28/2010 11:04 AM, Pedro Rodrigo Cardiel wrote: El jue, 28-10-2010 a las 09:46 -0500, Caldarale, Charles R escribió: What do you expect to happen when requests arrive for the non-started webapp during the delay period? Tomcat returns the same as when you stop an application Generally, any synchronization with external events that the webapp may require is entirely the responsibility of the webapp. You can possibly achieve what you want with some external script that interfaces with the Tomcat manager app (text, not GUI, version) to start and stop a webapp. The thing is that there are several heavy applications (the tomcat I have to throw with 2.7 GB of memory) that usually start badly. But if I re-launched by hand one by one then they are loaded properly. So I want to put time between tomcat start an application and again tomcat. In that case, you might consider writing a simple app that uses timers to sequence the startup and shutdown of your various apps. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat decoding plus sign in URL?
Does Tomcat have a way of controlling whether the + sign gets converted to a space in a URL? e.g. In Websphere, there is a setting com.ibm.ws.webcontainer.decodeURLPlusSign source: http://www-01.ibm.com/support/docview.wss?uid=swg1PK23481 -- - -- Robert La Ferla VP Engineering OMS SafeHarbor This message (and any attachments) contains confidential information and is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, distribution, or the taking of any action based on this message, is strictly prohibited. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat 5.5 and 6.0
Hi I would like to know when an application is compatible with 5.5 versions, it is also with 6.0? Or testing should be done? There are any official statements about it? Kind regards, Alfio Vergine Senior Account Director Italy, Turkey Greece EastNets RD Drève Richelle 161 Bldg P B-1410 Waterloo Belgium Mobile: +39 333 8952158 averg...@eastnets.com mailto:averg...@eastnets.com www.eastnets.com http://www.eastnets.com/ CONFIDENTIALITY: This e-mail and any files transmitted with it are confidential and intended solely for the use of the recipient(s) only. Any review, retransmission, dissemination or other use of, or taking any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you have received this e-mail in error please notify the sender immediately and destroy the material whether stored on a computer or otherwise. DISCLAIMER: Any views or opinions presented within this e-mail are solely those of the author and do not necessarily represent those of Eastern Networks ltd., unless otherwise specifically stated. P Please consider the environment before deciding to print this email. *
Re: how can i turn off This is very likely to create a memory leak.
On Thu, Oct 28, 2010 at 4:19 PM, Simon Funnell simon.funn...@propositum.biz wrote: On 28/10/10 14:53, Leon Rosenberg wrote: ok, i revoke my nevermind message, even after I removed JreMemoryLeakPreventionListener I still get the warning. Even weirder: Oct 28, 2010 3:50:55 PM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [Poller SunPKCS11-Darwin] but has failed to stop it. This is very likely to create a memory leak. Note the word 'likely' is not 'defiantly', it is possible that your implementation is 'not' creating a memory leak. but a SEVERE log message should be pretty sure and not likely. If tomcat launches an independent thread (not a tomcat thread) that refers to objects within the tomcat instance (and its pool of threads), this is when a memory leak would occur. This is because objects referenced by the independent thread 'and' the tomcat instance would not be GC'ed when tomcat shuts down, because they are still referenced by a living thread. I really don't get it. I'm stopping tomcat. What do I care about objects living in a webapp which is DEAD in a second in a VM which will be dead in another second? 'Generally' you will want to stop the independent threads when tomcat shuts down, thus removing the 'likelihood' of memory leaks. No actually I don't care. If they have jobs to do, they are free to define their shutdown hooks. Otherwise all daemon threads are automatically killed if the vm is killed. If the independent threads have their own shut down hooks that realise tomcat is shutting down and dereference any appropriate objects, a memory leak will 'not' occur. If you want your independent threads to shut down with tomcat because they do not have the own mechanisms, implement a ServletContextListener.contextDestroyed that does so. Yeah, but I actually don't. I mean I'm hitting ctrl-c in a terminal with running bin/catalina.sh run. I just want to get rid of the message to prevent the admins from jumping up and down cause they detect a SEVERE message in the logs... regards Leon Regards, Simon Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoIntervalUpdater] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoMemoryReader] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoMemoryPoolReader] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoMemoryPoolReader] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [Thread-6] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:56 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8080 anyplace else except the server.xml to fix it? regards Leon On Thu, Oct 28, 2010 at 3:46 PM, Leon Rosenberg rosenberg.l...@gmail.com wrote: nevermind, found it, sorry for disturbing. On Thu, Oct 28, 2010 at 3:44 PM, Leon Rosenberg rosenberg.l...@gmail.com wrote: Hello, I investigated an issue (another thread) with new error messages after tomcat update: SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoMemoryPoolReader] but has failed to stop it. This is very likely to create a memory leak. After some research and discussions with colleagues we came to the conclusion that this message is ... well not helping us. Is there a possibility to turn it off? Its annoying to have such messages in the logs after a server shutdown. For explanation: I'm not planing to use webapp reload in my environment, hence, this message is actually just spam. regards Leon - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To
RE: Tomcat 5.5 and 6.0
From: Alfio Vergine [mailto:averg...@eastnets.com] Subject: Tomcat 5.5 and 6.0 I would like to know when an application is compatible with 5.5 versions, it is also with 6.0? Highly likely. Or testing should be done? Always. There are any official statements about it? http://tomcat.apache.org/migration.html - 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: how can i turn off This is very likely to create a memory leak.
ok, i revoke my nevermind message, even after I removed JreMemoryLeakPreventionListener I still get the warning. Even weirder: Oct 28, 2010 3:50:55 PM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [Poller SunPKCS11-Darwin] but has failed to stop it. This is very likely to create a memory leak. Note the word 'likely' is not 'defiantly', it is possible that your implementation is 'not' creating a memory leak. but a SEVERE log message should be pretty sure and not likely. I agree a WARNING or INFO is more correct on shutdown. This would only be SEVERE if you were restarting your container with a manager or dropping in a new WAR and the JVM will continue running. Maybe the Memory Leak detection ought to have some parameter about whether the Sys Admin actually cares? Or, better couldn't it know if the whole JVM is going down and adjust the level and message accordingly? My 2 cents. Regards, Dave If tomcat launches an independent thread (not a tomcat thread) that refers to objects within the tomcat instance (and its pool of threads), this is when a memory leak would occur. This is because objects referenced by the independent thread 'and' the tomcat instance would not be GC'ed when tomcat shuts down, because they are still referenced by a living thread. I really don't get it. I'm stopping tomcat. What do I care about objects living in a webapp which is DEAD in a second in a VM which will be dead in another second? 'Generally' you will want to stop the independent threads when tomcat shuts down, thus removing the 'likelihood' of memory leaks. No actually I don't care. If they have jobs to do, they are free to define their shutdown hooks. Otherwise all daemon threads are automatically killed if the vm is killed. If the independent threads have their own shut down hooks that realise tomcat is shutting down and dereference any appropriate objects, a memory leak will 'not' occur. If you want your independent threads to shut down with tomcat because they do not have the own mechanisms, implement a ServletContextListener.contextDestroyed that does so. Yeah, but I actually don't. I mean I'm hitting ctrl-c in a terminal with running bin/catalina.sh run. I just want to get rid of the message to prevent the admins from jumping up and down cause they detect a SEVERE message in the logs... regards Leon Regards, Simon Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoIntervalUpdater] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoMemoryReader] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoMemoryPoolReader] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoMemoryPoolReader] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:55 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/moskitodemo] appears to have started a thread named [Thread-6] but has failed to stop it. This is very likely to create a memory leak. Oct 28, 2010 3:50:56 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8080 anyplace else except the server.xml to fix it? regards Leon On Thu, Oct 28, 2010 at 3:46 PM, Leon Rosenberg rosenberg.l...@gmail.com wrote: nevermind, found it, sorry for disturbing. On Thu, Oct 28, 2010 at 3:44 PM, Leon Rosenberg rosenberg.l...@gmail.com wrote: Hello, I investigated an issue (another thread) with new error messages after tomcat update: SEVERE: The web application [/moskitodemo] appears to have started a thread named [MoskitoMemoryPoolReader] but has failed to stop it. This is very likely to create a memory leak. After some research and discussions with colleagues we came to the conclusion that this message is ... well not helping us. Is there a possibility to turn it off? Its annoying to have such messages in the logs after a server shutdown. For explanation: I'm not planing to use webapp reload in my
RV: Session Context variables architecture problem
Dear All, I'm currently using Tomcat 6.0.28 and having some doubt on how to solve and implement this problem: My webapp has a MySQL Database with a table named parameters, in which we have just two columns (property and value). This table is acceded many times but doesn't change often. For performance purposes I want to save this parameters in the user's tomcat session, so they are read from memory and not database. So far so good. Now the problem: how can I tell this sessions that an attribute has changed? I had suggestions of using context variables instead of session variables, but that didn't solve the problem. Any help in this matter is more than welcome. I have no problem in changing the approach, and may be not use sessions at all. Thanks in advance. Best regards, Federico Alvarez. Info: Tomcat 6.0.28 Java 1.6 MySQL 5.5 NOT USING HIBERNATE, so 2nd Level cache is not an option
Tomcat 6.0.18 JNDIRealm ConnectException: Connection timed out
Hi,
i have tomcat 6.0.18 and configured it to use JNDIRealm for a specific path:
Realm className=org.apache.catalina.realm.JNDIRealm
test=89
connectionName=CN=tomcat,CN=
Users,DC=host,DC=de
connectionPassword=***
connectionURL=ldap://host:389/;
referrals=follow
userBase=DC=host,DC=de
userRoleName=memberOf
userSearch=(amp;(sAMAccountName={0})(objectClass=user))
userSubtree=true
/
login-config
auth-methodBASIC/auth-method
realm-nameJNDIRealm/realm-name
/login-config
The problem is that sometimes it is working fine,
but sometimes Tomcat got an exception and users can not be authenticated,
because the connections to ldap (AD) timed out.
2010-10-28 15:53:08,592 ContainerBase.[Catalina]
ERROR [ttp-8443-1] - Exception performing authentication
javax.naming.PartialResultException [Root exception is
javax.naming.CommunicationException: host.de:389 [Root exception is
java.net.ConnectException: Connection timed out: connect]]
Have someone an idea or a hint to find out, why these connections are timing
out sometimes?
Thanks in advance
Re: Tomcat decoding plus sign in URL?
On 28/10/2010 16:41, Robert La Ferla wrote: Does Tomcat have a way of controlling whether the + sign gets converted to a space in a URL? No. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 5.5 and 6.0
Thanks Christine for feedback, I would like to chat about your input when I return to the office. Matthew told me that we will visit TCP to install ITUTils, SeepdR and Mach5 next January. So, I would like to work with you November to finish this feature. Thanks again, yasushi -Original Message- From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: Thursday, October 28, 2010 9:22 AM To: Tomcat Users List Subject: RE: Tomcat 5.5 and 6.0 From: Alfio Vergine [mailto:averg...@eastnets.com] Subject: Tomcat 5.5 and 6.0 I would like to know when an application is compatible with 5.5 versions, it is also with 6.0? Highly likely. Or testing should be done? Always. There are any official statements about it? http://tomcat.apache.org/migration.html - 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 ### This message is for the designated recipient only and may contain privileged or confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. ### - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 6.0.18 JNDIRealm ConnectException: Connection timed out
-Original Message-
From: S.V. [mailto:svku...@googlemail.com]
Subject: Tomcat 6.0.18 JNDIRealm ConnectException: Connection timed out
userBase=DC=host,DC=de
I had this same problem. It depends on where your users are located in AD and
how large the tree is.
This is probably not the right way to do it, but I limited the roleBase and
userBase to specific nodes.
Realm className=org.apache.catalina.realm.JNDIRealm
connectionURL=ldap://url:389;
connectionName=CN=ad_user_account,OU=Service
Accounts,OU=PLANDEV Dept,DC=plandev,DC=maricopa,DC=gov
connectionPassword=***
roleBase=OU=Groups,OU=PLANDEV
Dept,DC=plandev,DC=maricopa,DC=gov
roleSubtree=true
roleName=cn
roleSearch=(member={0})
userBase=OU=PLANDEV Dept,DC=plandev,DC=maricopa,DC=gov
userSearch=(amp;(objectCategory=person)(sAMAccountName={0}))
userSubtree=true
userRoleName=memberOf
/
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: how can i turn off This is very likely to create a memory leak.
On 28/10/2010 17:52, David Fisher wrote: Maybe the Memory Leak detection ought to have some parameter about whether the Sys Admin actually cares? Or, better couldn't it know if the whole JVM is going down and adjust the level and message accordingly? Not sure that's a good idea. On the other hand, Tomcat knows when it's shutting down, so it should be possible to modify the various leak detection methods to ignore or modify them accordingly. Input ideas/patches in the enhancement request here: https://issues.apache.org/bugzilla/show_bug.cgi?id=50175 p 0x62590808.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: RV: Session Context variables architecture problem
On 28/10/2010 18:31, falva...@geocom.com.uy wrote: Dear All, I'm currently using Tomcat 6.0.28 and having some doubt on how to solve and implement this problem: My webapp has a MySQL Database with a table named parameters, in which we have just two columns (property and value). This table is acceded many times but doesn't change often. For performance purposes I want to save this parameters in the user's tomcat session, so they are read from memory and not database. So far so good. Do you actually know that this is a performance problem, or are you guessing that it is? Now the problem: how can I tell this sessions that an attribute has changed? Using the session will mean that you have duplicate copies of this information in each session. I had suggestions of using context variables instead of session variables, but that didn't solve the problem. *If* you need to do this, using the Context is probably better. I would suggest that you created a class which periodically updated all the values by selecting the data in the DB and storing the result in the Context. Implementing a ServletContextListener will give you access to the ServletContext and two methods, for app startup shutdown, which you can use to start the periodic process, and properly stop it (very important). You may consider using a Timer, or something from the java.util.concurrent package. p Any help in this matter is more than welcome. I have no problem in changing the approach, and may be not use sessions at all. Thanks in advance. Best regards, Federico Alvarez. Info: Tomcat 6.0.28 Java 1.6 MySQL 5.5 NOT USING HIBERNATE, so 2nd Level cache is not an option 0x62590808.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: Tomcat Maven and Axis 1.5.1 problem
On 28/10/2010 13:43, srd.pl wrote: Caused by: java.lang.ClassNotFoundException: org.apache.axis2.transport.local.LocalTransportSender at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1438) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1284) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Unknown Source) at org.apache.axis2.util.Loader.loadClass(Loader.java:261) at org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:669) 1 email to the list is sufficent, please be patient. The root cause is a ClassNotFoundException. Are you sure you have included all of the jars in the application? The Axis lists may be a better location to find out more about your problem. p 0x62590808.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
