On Wed, Mar 13, 2013 at 9:40 PM, Ian Schneider <[email protected]>wrote:
> 2013-03-13 20:05:43,789 ERROR [renderer.label] - Error adding label to
> the label cache
> java.lang.IllegalArgumentException: alpha value out of range
> at java.awt.AlphaComposite.<init>(AlphaComposite.java:618)
> at java.awt.AlphaComposite.getInstance(AlphaComposite.java:688)
> at
> org.geotools.renderer.style.SLDStyleFactory.getComposite(SLDStyleFactory.java:1024)
>
> Obviously, there could be other ways to handle this specific exception
> so that's not the point. Due to the number of requests coming in,
> looking at the WMS KVP info was not helpful. Adding to the issue, when
> I turned on 'default' logging, my log file rotated 3 times within
> minutes (yes - 4M/min of logging output).
>
> So two thoughts/ideas:
> 1) to prevent stack-trace induced DOS, allow truncating the stack
> trace as an option - either a fixed length or upon a matching prefix
> (javax.servlet.http.HttpServlet.service for example)
>
Does that really cause a DOS attack situation? Is the server being unable
to respond? I believe we'll see a slowdown for sure... wondering how severe
though.
I made a quick check around, don't see any ready made solution to summarize
stack traces in log4j... there's also the thing that just cutting them
won't do it,
as the interesting part is normally at the end of the stack trace.
Something more interesting might be to log just a couple of method lines for
each "caused by" statement, that might help throwing away the bathwater
without the baby along with it...
> 2) to help me find the problematic request/SLD/whatever, an option for
> request-based logging - this might look like log messages being
> collected and logged together (at the end of the response) with the
> request info
>
Uh, no, that would require keeping them in memory and would end up causing
other kinds of trouble.
Normally the answer to debugging multithreaded systems is to add the thread
id to the log output using %t in the pattern.... something that we could
indeed do.
Another thing that I've seen in usage in the cases where more than one
thread is
involved in processing a request is give each request a unique id, and then
propagate
such id around in the code so that all activities related to that request
can be
grepped for
Cheers
Andrea
--
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
