fasdfasdfasdfa
-
力瓦依丁・库尔班
Mobile:18130819208
qq:895791034
WeChat:lee_vayi
Email:l...@bsoft.com.cn
Company:Bsoft software Company
> From: André Warnier [mailto:a...@ice-sa.com]
> Subject: Re: [OT] Imperialism and sad demise
>
> We also did probably not get the coverage over here, about the
> Google/Topeka story, as this is the first I hear about it.
Let's hope this works outside of the US:
http://goo
Caldarale, Charles R wrote:
From: André Warnier [mailto:a...@ice-sa.com]
Subject: [OT] Imperialism and sad demise
www.lmgtfy.com now seems to lead to a search page named Topeka
By design (or at least intent). This is Google's 1 April response to the city of Topeka,
Kansas offic
"...Toto, I don't think we're in Kansas anymore!"
On Apr 1, 2010, at 4:10 PM, Caldarale, Charles R wrote:
From: André Warnier [mailto:a...@ice-sa.com]
Subject: [OT] Imperialism and sad demise
www.lmgtfy.com now seems to lead to a search page named Topeka
By design
> From: André Warnier [mailto:a...@ice-sa.com]
> Subject: [OT] Imperialism and sad demise
>
> www.lmgtfy.com now seems to lead to a search page named Topeka
By design (or at least intent). This is Google's 1 April response to the city
of Topeka, Kansas officially changing it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Len,
On 4/1/2010 3:30 PM, Len Popp wrote:
> That's terrible! I predict a humungous backlash from lmgtfy users, and
> they'll be forced to restore the old service. Probably by tomorrow
> morning. :-)
I've certainly registered my complaint!
- -chris
-
That's terrible! I predict a humungous backlash from lmgtfy users, and
they'll be forced to restore the old service. Probably by tomorrow
morning. :-)
--
Len
On Thu, Apr 1, 2010 at 15:25, André Warnier wrote:
> Well, fellow Tomcatters, it is with deep sadness that I have to report that
> one o
Well, fellow Tomcatters, it is with deep sadness that I have to report
that one of the most beloved tools used on this forum seems to have been
hijacked.
www.lmgtfy.com now seems to lead to a search page named Topeka, with a
logo eerily reminiscent of something else, but which leads to a search
Remy Maucherat wrote:
On 2/28/06, Peter Lin <[EMAIL PROTECTED]> wrote:
honestly, besides Weblogic, most servlet and ejb containers do not provide
simple and clear instructions for tracing issues. With websphere, you have
to buy an expensive license of WASD and even then debugging an issue won
Peter Lin <[EMAIL PROTECTED]> wrote:
>
> honestly, I really doubt logging will produce anything useful beyond
> the VM dump you already posted. My first hand experience, the logs
> won't help at this point. What needs to happen is to step through the
> code and see exactly what is happening.
>
> i
honestly, I really doubt logging will produce anything useful beyond the VM
dump you already posted. My first hand experience, the logs won't help at
this point. What needs to happen is to step through the code and see exactly
what is happening.
if you don't have access to a profiler, the other op
Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
>
> This could be completely unrelated, but let me throw something at you,
> maybe it will help
> btw. I prefer to run mod_proxy over mod_jk over http, much simpler,
> and
> in *our* load tests has scaled much better during stress.
>
> >Response a
Peter Lin <[EMAIL PROTECTED]> wrote:
>
> my advice is dive in and try to debug it, or hire someone with
> experience debugging webapps.
>
> there's no much others can do for you at this point, since it's
> debugging. good luck.
I've just meant configuring the logging system:
> > > So how can I:
This could be completely unrelated, but let me throw something at you,
maybe it will help
btw. I prefer to run mod_proxy over mod_jk over http, much simpler, and
in *our* load tests has scaled much better during stress.
>Response already committed
This can happen if your servlet/jsp has code
my advice is dive in and try to debug it, or hire someone with experience
debugging webapps.
there's no much others can do for you at this point, since it's debugging.
good luck.
peter
On 3/1/06, Tomasz Nowak <[EMAIL PROTECTED]> wrote:
>
> Tomasz Nowak <[EMAIL PROTECTED]> wrote:
> >
> > Hm. Her
Tomasz Nowak <[EMAIL PROTECTED]> wrote:
>
> Hm. Here is my logging.properties:
> http://www.biochip.pl/logging.properties.txt
> The way new vhosts are added is pretty stupid for me but
> lets forget about the semantics now.
>
> I've added swallowOutput attibute to serveral context.
> How should it
Peter Lin <[EMAIL PROTECTED]> wrote:
>
> another potential solution is to try a different JVM like Bea's
> JRockit. JRockit provides some built in profiling capabilities, so
> that is another way to get some profile data quickly.
I've read about jrockit 5.0 SP1. They say it has a new feature that
Wade Chandler <[EMAIL PROTECTED]> wrote:
>
> Sometimes changing the ratio to not have enough new
> space and then creating too many objects too fast can
> make your application eventually throw OOMEs because
> it can't move the objects into older spaces quick
> enough depending on what you applicat
Nathan Smith <[EMAIL PROTECTED]> wrote:
>
> The problem can be fixed by increasing your -XX:MaxPermSize value to
> more than 256.
I've increased it to 512m now. I'll see.
> Download and use a program called visualgc available here
> http://java.sun.com/performance/jvmstat. You can have it running
Peter Lin <[EMAIL PROTECTED]> wrote:
>
> It's not at all clear why -XX:MaxPermSize=256m isn't working and the
> perm size is still at the default. If the perm gen was set correctly,
> wouldn't the dump show something other than 99%?
You're right, it shows
PSPermGen total 50304K
not the 256
--- Tomasz Nowak <[EMAIL PROTECTED]> wrote:
> Peter Lin <[EMAIL PROTECTED]> wrote:
> >
> > look at the dump, it looks like the permgen ran
> out of space
> >
> > PSPermGen total 50304K, used 50170K
> [0x445f, 0x4771,
> > 0x545f)
> > object space 50304K, 99% used
> [0x445f
Hi Tomasz,
this is the exact point I was making in my previous email. The error
message that was returned was to do with the Java Heap Space. It may be
referring to the entire heap that is allocated to the JVM, who knows.
The problem can be fixed by increasing your -XX:MaxPermSize value to
mo
On 2/28/06, Tomasz Nowak <[EMAIL PROTECTED]> wrote:
>
> Peter Lin <[EMAIL PROTECTED]> wrote:
> >
> > look at the dump, it looks like the permgen ran out of space
> >
> > PSPermGen total 50304K, used 50170K [0x445f, 0x4771,
> > 0x545f)
> > object space 50304K, 99% used [0x445f00
Peter Lin <[EMAIL PROTECTED]> wrote:
>
> look at the dump, it looks like the permgen ran out of space
>
> PSPermGen total 50304K, used 50170K [0x445f, 0x4771,
> 0x545f)
> object space 50304K, 99% used [0x445f,0x476ee878,0x4771)
>
> try increasing your permGen to 128Mb
look at the dump, it looks like the permgen ran out of space
PSPermGen total 50304K, used 50170K [0x445f, 0x4771,
0x545f)
object space 50304K, 99% used [0x445f,0x476ee878,0x4771)
try increasing your permGen to 128Mb. Another option is to use a jdk that
doesn't have pe
Leon Rosenberg <[EMAIL PROTECTED]> wrote:
>
> kill -SIGQUIT (i think its kill -11) your tomcat-java process
Ok, it has happened again ! Simply:
Mar 1, 2006 2:28:34 AM org.apache.catalina.connector.CoyoteAdapter
service
SEVERE: An exception or error occurred in the container during the
request pro
Don't count on it!!
In a message dated 2/28/2006 7:26:33 P.M. Eastern Standard Time,
[EMAIL PROTECTED] writes:
it seems that using a rude tone is a good way to get many answers,
your question got 26 answers, mine, with a similar problem, only 1
(and a not helpful one).
On 3/1/06, Peter Lin <[EMAIL PROTECTED]> wrote:
> On 2/28/06, Tomasz Nowak <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > I've not noticed more then 400-500 java threads, but I'll monitor
> > that. I've set different ulimits form differnt users, BUT user
> > that runs java/tomcat has no limits but one:
On 2/28/06, Tomasz Nowak <[EMAIL PROTECTED]> wrote:
>
>
>
> I've not noticed more then 400-500 java threads, but I'll monitor
> that. I've set different ulimits form differnt users, BUT user
> that runs java/tomcat has no limits but one: -s 2048 (stacksize).
>
> AFAIK that one was recommended by RE
Leon Rosenberg <[EMAIL PROTECTED]> wrote:
>
> you should seriously consider upgrading to 2.6.x linux. 2.4.s thread
> support simply sucks! If your tomcat spawns more than allowed threads
> it will get an outofmemoryerror and simply die... And I don't mean
> your 200 tomcat httpworker threads only,
it seems that using a rude tone is a good way to get many answers,
your question got 26 answers, mine, with a similar problem, only 1
(and a not helpful one).
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-
mcat all the time.
>
> -Original Message-
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Tomasz Nowak
> Sent: Tuesday, February 28, 2006 6:37 PM
> To: users@tomcat.apache.org
> Subject: Re: Sad: Tomcat 5.5.x crashes almost every single day.
>
> Remy Maucherat <[EMAIL PR
I use JProfiler with Tomcat all the time.
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Tomasz Nowak
Sent: Tuesday, February 28, 2006 6:37 PM
To: users@tomcat.apache.org
Subject: Re: Sad: Tomcat 5.5.x crashes almost every single day.
Remy Maucherat <[EM
you should seriously consider upgrading to 2.6.x linux. 2.4.s thread
support simply sucks! If your tomcat spawns more than allowed threads
it will get an outofmemoryerror and simply die... And I don't mean
your 200 tomcat httpworker threads only, but all threads in the jvm,
including database conne
Tim Lucia <[EMAIL PROTECTED]> wrote:
>
> #2 - Do any commercial application server vendors offer you
> assistance on how to find bugs in application code? You're much more
> likely to find these answers using google, or reading wikis or from
> community support. There are hundreds of such discuss
Leon Rosenberg <[EMAIL PROTECTED]> wrote:
>
> We had some serious problems with tomcat, which are solved now,
> however, we are on 5.0.25 (with session patch) and not on 5.5.x yet.
> However, when tomcat dies, what your cpu usage is looking like? 100%?
I've noticed that when tomcat hangs - load av
Nathan Smith <[EMAIL PROTECTED]> wrote:
>
> Hi Tomasz,
>
> you mentioned below that you have a MaxPermSize of 256m.
I have not seen "OOME: PermGen" errors on that machine
but after having some of them on other machine with aditonal
10 webapps deployed I've increased it from default 64m
to 256m to
Remy Maucherat <[EMAIL PROTECTED]> wrote:
>
> In case you haven't noticed, it is extremely hard to do, because
> webapps have their own logging mechanism most of the time. You mention
> the logger element of 4.x, but it didn't actually do anything (it did
> put the internal logging for the specifie
good luck with
Jprofiler as well.
-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 28, 2006 5:47 PM
To: Tomcat Users List
Subject: Re: Sad: Tomcat 5.5.x crashes almost every single day.
On 2/28/06, Peter Lin <[EMAIL PROTECTED]> wrote:
h
Hi Tomasz,
you mentioned below that you have a MaxPermSize of 256m. I would suggest
increasing this value to a much larger amount and even increasing your
-Xms and -Xmx values.
We had a problem with our application in a live environment where it
would regularly get errors like the following;
Tomcat Users:
We also had the dreaded, 'out of memory' errors and periodic crashes
several times every day. Currently, we are stable. With help from
Chuck, we were able to narrow down our problem to that of
insufficient permanent generation memory. The point being that
figuring out JVM
with
Jprofiler as well.
-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 28, 2006 5:47 PM
To: Tomcat Users List
Subject: Re: Sad: Tomcat 5.5.x crashes almost every single day.
On 2/28/06, Peter Lin <[EMAIL PROTECTED]> wrote:
> honestly, be
On 2/28/06, Peter Lin <[EMAIL PROTECTED]> wrote:
> honestly, besides Weblogic, most servlet and ejb containers do not provide
> simple and clear instructions for tracing issues. With websphere, you have
> to buy an expensive license of WASD and even then debugging an issue won't
> be better in my e
On 2/28/06, Tomasz Nowak <[EMAIL PROTECTED]> wrote:
>
> Tim Lucia <[EMAIL PROTECTED]> wrote:
> >
> > Send Tomcat a QUIT (11) signal on Unix, or control/break (run it
> > interactively) on Windows. This will cause the VM to dump all thread
> > stacks.
> >
> > If you don't like Tomcat, you can alway
On 2/28/06, Tomasz Nowak <[EMAIL PROTECTED]> wrote:
> Your right, the tone of my postings is inproper.
> I've been using 'free' software for almost 10 years now
> and I pretty well get the rules. My only excuse is the
> level of my frustration, based on recent Tomcat use.
>
> For now, the only cont
You can always feel free to contribute documentation improvements!
Tim
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Tomasz Nowak
Sent: Tuesday, February 28, 2006 4:36 PM
To: users@tomcat.apache.org
Subject: Re: Sad: Tomcat 5.5.x crashes almost every single day.
Tim Lucia <[EMAIL PROTECTED]> wrote:
>
> Send Tomcat a QUIT (11) signal on Unix, or control/break (run it
> interactively) on Windows. This will cause the VM to dump all thread
> stacks.
>
> If you don't like Tomcat, you can always shell out some big bugs for a
> commercial application server. Fo
Mark Eggers wrote:
I'm confused - but wouldn't an enableLookups on the
AJP connector return the hostname of the remote Apache
server sending the request (and not the remote web
client)?
No.
JkOptions +ForwardLocalAddress
Regards,
Mladen.
-
On 2/28/06, Tomasz Nowak <[EMAIL PROTECTED]> wrote:
> Peter Crowther <[EMAIL PROTECTED]> wrote:
> >
> > Have you tested it for deadlocks that would cause hangs?
> > [...] Profile your application. What's eating memory?
> > Get a thread dump when your application hangs. Is anything
> > deadlocked?
[...skiped...]
> I've been crond-restarting Tomcat 4.1 on Java 1.4 every
> night for more than a year, and now I have to restart
> Tomcat 5.5.15 on Java 1.5 AND apache httpd also almost
> every single day. From my -user point of view, Tomcat
> doesn't change in a good direction. In fact in it is
>
-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Tomasz Nowak
Sent: Tuesday, February 28, 2006 1:32 PM
To: users@tomcat.apache.org
Subject: Re: Sad: Tomcat 5.5.x crashes almost every single day.
Peter Crowther <[EMAIL PROTECTED]> wrote:
>
> Have you tested it for deadlocks that wo
I'm confused - but wouldn't an enableLookups on the
AJP connector return the hostname of the remote Apache
server sending the request (and not the remote web
client)?
I don't know since I'm at work, and I always disable
enableLookups since it's a potential performance hit.
/mde/
--- Tomasz Nowak
Peter Crowther <[EMAIL PROTECTED]> wrote:
>
> Have you tested it for deadlocks that would cause hangs?
> [...] Profile your application. What's eating memory?
> Get a thread dump when your application hangs. Is anything
> deadlocked? What? Where?
How?
http://www.google.com/search?hl=pl&q=%22th
Mark Eggers <[EMAIL PROTECTED]> wrote:
>
> > enableLookups="true" redirectPort="8443" />
>
> Why enableLookups="true" ???
I use request.getRemoteHost in couple of places.
> Also, Cocoon can be very resource-intensive depending
> on which blocks you've built.
Almost always only:
- databases-
> enableLookups="true" redirectPort="8443" />
Why enableLookups="true" ???
Also, Cocoon can be very resource-intensive depending
on which blocks you've built.
JSP under Cocoon 2.1.7 and JDK 1.5 is also
problematic, see for example:
http://issues.apache.org/jira/browse/COCOON-1457
I have so
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Tomasz Nowak
> Probably important:
> ===
[lots of technical details about kit and container config]
Very important
==
Your application. Have you profiled it for memory leaks that would
cause a OOME? Have you tested
Probably important:
===
- 2x Xeon, 3 GB mem
- Linux 2.4.26
- Java 1.5.0_06-b05
- Apache Tomcat 5.5.15
- CATALINA_OPTS="\
-server \
-Djava.awt.headless=true \
-Dfile.encoding=UTF-8 \
-XX:MaxPermSize=256m \
-Xms1024m -Xmx1024m"
-
- mod_jk 1.2.15
- Apache Httpd 1.
57 matches
Mail list logo
