OutOfMemoryError: allocLargeObjectOrArray
Dear all: We have some problem with OutOfMemory error. Environment Tomcat: 5.5.25 JDK: jrockit-R27.4.0-jdk1.5.0_12 5130472 [TP-Processor29] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/Mainweb].[default] - Servlet.service() for servlet default threw exception java.lang.OutOfMemoryError: allocLargeObjectOrArray - Object size: 75333648, Num elements: 37666816 at java.lang.String.(String.java:458) at java.io.ByteArrayOutputStream.toString(ByteArrayOutputStream.java:160) at org.apache.tomcat.util.log.CaptureLog.getCapture(CaptureLog.java:48) at org.apache.tomcat.util.log.SystemLogHandler.stopCapture(SystemLogHandler.java:109) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:207) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.jstripe.tomcat.probe.Tomcat55AgentValve.invoke(Tomcat55AgentValve.java:20) at org.apache.catalina.cluster.tcp.ReplicationValve.invoke(ReplicationValve.java:347) 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:151) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:200) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:773) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:703) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:895) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) at java.lang.Thread.run(Thread.java:595) == java.lang.OutOfMemoryError: allocLargeObjectOrArray - Object size: 75333648, Num elements: 37666816 What does it mean about allocLargeObjectOrArray ? I have tried to tune jvm options with "-server -Xms768m -Xmx768m -Xns256m" But tomcat still throw out the same error Any suggestion will be appreciated ^^ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: how to delete \work\Catalina subdirectorys every time tomcat loads
You could edit the startup command script to delete the directory before the start command is run. I am not too sure about the windows services if that is what you are using. It would help if you told us the operating system and method of starting tomcat. --Angus Mezick -Original Message- From: Meir Yanovich [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2008 6:23 AM To: users@tomcat.apache.org Subject: how to delete \work\Catalina subdirectorys every time tomcat loads Hello all i need to be able to remove the cache directory's in the tomcat 6 every time tomcat starting is there some kind of build in method or acceptable way to do that ? thanks allot - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Clustering & failing over with Tomcat 6.0.16
Does it take time for nodeA to resync the sessions after it comes back up? Could Sharad be shutting down nodeB too early? --Angus Mezick -Original Message- From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Sent: Monday, August 11, 2008 11:07 PM To: Tomcat Users List Subject: Re: Clustering & failing over with Tomcat 6.0.16 nope, it should work both ways Gupta, Sharad wrote: > Hi, > > I have a cluster of Tomcat 6.0.16 using DeltaManager. Session > replication works fine, failover works fine for the first time. That is, > the first time I failover from, lets say, nodeA to nodeB, my session is > carried over & the user continues with the existing logged in session > without being asked to log back in. > > But the problem happens when nodeA comes backup & nodeB needs to be > shutdown. The session information is somehow, not carried over as my app > asks me to relogin at that point in time. Is this a desired behaviour > with DeltaManager? > > Thanks > > > > > > > - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: where can i get tocat admin package
I am having the same problem. I have looked here: http://apache.mirror.facebook.com/tomcat/tomcat-6/ and in the lower directories. No mention of the admin pack. Where would it be hiding? Even if I look at 6.0 in the archives, there is no admin app. Has it not been ported over to 6.0? --Angus Mezick x7619 -Original Message- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 12, 2008 3:11 AM To: Tomcat Users List Subject: Re: where can i get tocat admin package tunzaw wrote: > Hi > > Where can i get tomcat admin package? I want to use > http://localhost:8080/admin. > When i attempt to use this url ,tomcat say tomcat admin tool do not already > install.Where can i download tomcat admin package? Have you tried the download pages? Mark - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tomcat admin packagep
When I go to the LambdaProbe site I see this: It is also compatible with Tomcat5 versions 5.0.x and 5.5.x. After poking at the forums it seems that it also works with 6.0. Guess they need some website updates. Link: http://www.lambdaprobe.org/d/index.htm --Angus Mezick -Original Message- From: Christopher Schultz [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 12, 2008 10:17 AM To: Tomcat Users List Subject: Re: tomcat admin package 5) Everyone may as well switch to LambdaProbe, which is much nicer, anyway. - -chris
RE: Communicating on the Tomcat admin port
This page shows how to use ant to execute commands against the manager. http://tomcat.apache.org/tomcat-6.0-doc/manager-howto.html And this is all about using the JMXRemote stuff: http://tomcat.apache.org/tomcat-6.0-doc/monitoring.html --Angus Mezick -Original Message- From: Adam Gordon [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2008 10:59 AM To: Tomcat Users List Subject: Communicating on the Tomcat admin port Is there a way to communicate with Tomcat via the admin port but not have to use the web interface? We're looking at completely automating our deployment process and it would be nice if we could send a signal to Tomcat to shutdown via the command-line. Additionally, if it is possible, are there other things one can do via the admin port? Thanks, --adam - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Default error page generation logic in tomcat
Create your own 404 error page and add it to your web.xml. 404 /error/404.jsp − java.lang.Throwable /error/500.jsp − 500 /error/500.jsp --Angus Mezick -Original Message- From: Raghavendra Datt [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2008 2:33 PM To: users@tomcat.apache.org Subject: Default error page generation logic in tomcat Hi Guys, I had a specific requirement related to tomcat error generation. When a default error page is generated like 404 error page, tomcat appends its version info at the bottom of the page. I don't want this version to be displayed on the error page. I am trying to understand which part of the tomcat code actually does this? Any response will be appreciated. Thanks, Raghu
RE: where to place context configuration
Am I the only one that is REALLY disturbed about that idea of REQUIRING two identical files to run an app? One in the war file and one in the conf directory? If the only in the conf directory takes priority, why the one in the war file needed at all? I am just hoping this isn't in tomcat 6.0.. The idea of relying on the server to use the correct version of possibly different files in a production server makes me VERY nervous. --Angus Mezick -Original Message- From: Robert Dietrick [mailto:[EMAIL PROTECTED] Sent: Thursday, August 14, 2008 2:22 PM To: Tomcat Users List Subject: Re: where to place context configuration I would very much prefer to use only the one in mywebapp/META-INF/contex.xml, as this is much less invasive (does not require changing/adding anything to tomcat's global config directories). But this doesn't seem to work. I can leave it as is (and am becoming resigned to the fact that this is my only option), but this is sort of a maintenance nightmare since the two files need to be kept in sync. Plus, it just seems idiotic to need to declare the context and its resources in two locations. Does either of these files need a 'docBase' or 'path' parameter? It doesn't seem to make a difference either way. -rob On Thu, Aug 14, 2008 at 11:00 AM, Mark Thomas <[EMAIL PROTECTED]> wrote: > Robert Dietrick wrote: >> Hi, >> >> I just noticed that I had a definition in both >> $CATALINA_HOME/conf/Catalina/localhost/mywebapp.xml and in >> $CATALINA_HOME/webapps/mywebapp.war/META-INF/context.xml. In both of >> these context definitions, I define a JNDI database connection pool >> with the same name and identical parameters. This was working fine, >> but it is confusing, redundant, and runs contrary to the >> recommendations in the official documentation. >> >> However, if i remove either one of these files, I get the dreaded >> "Cannot create JDBC driver of class '' for connect URL 'null'" error. >> Can anyone offer any advice? > > Just leave it as is? > > The one in conf will take priority. > > Mark > > > - > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Apache Tomcat 6.0.34
Hello, We hit Authentication bypass and information disclosure CVE-2011-3190 <http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-3190> in tomcat 6.0.32 May i know when Tomcat 6.0.34 will be release? Regards, Angus This message may contain confidential or privileged information. If you are not the intended recipient, please advise us immediately and delete this message. See http://www.datapipe.com/about-us-legal-email-disclaimer.htm for further information on confidentiality and the risks of non-secure electronic communication. If you cannot access these links, please notify us by reply message and we will send the contents to you.
