Hi All,
I have a small problem which may be big (:)) internally.
Actually, I am load testing a Restlet application which takes some request
parameters as input, makes a LDAP query and returns data as an XML in response.
So, what happening in this load test is Spiky behavior of CPU.
CPU
Have you run the server with a profiler attached (such as jprobe,
yourkit, etc.)?
Are you load testing at a steady state? I.e., are you just running
the same request over and over in a loop? Or something more complicated?
Are you on a single-core CPU for the test or one core for the load
Hi Roman,
yes, you are right, this was a bug in the StringProvider. It's fixed in
the trunk now. Does it work for you now?
Sorry for the delay, because I have to do a lot of other things in the
moment I do not read the mailing list emails fast. If you note in the
subject that it's a problem
Hi John,
Thanks for response. please see answers inline.
Have you run the server with a profiler attached (such as jprobe, yourkit,
etc.)?
{Prashant} No, we have not used any profiler tool yet.
Are you load testing at a steady state? I.e., are you just running
the same request over
Hi Bruce,
Thanks for the env details.
It seems to be due to a null selector passed as a parameter to the
register() method in ByteUtils. I've added an extra test in ByteUtils. It
might either fully fix the problem or move it somewhere else.
Could you test again with a recent snapshot?
Hi Prashant,
You should indeed try using a profiler. Otherwise, try to isolate the cause
of these spikes, for example replacing the Restlet-LDAP resources with mock
resources and see how it affects the behavior.
If this becomes very urgent or too complex to debug and figure out, we can
help you
Hi Jerôme,
Sorry to answer so late, i'm a little busy :)
I created the corresponding issue:
http://restlet.tigris.org/issues/show_bug.cgi?id=604
Actually, the template value should be 0;service=hihi and not just
hihi.
Isn't it?
Actually, i expected hihi, i believed ';' was a separator (the
Hi Stephan
Thanks for quick fix! It works now for me. At first I wasn't sure if
JAX-RS was responsible, so I didn't mention it in the subject line.
Cheers,
Roman
Stephan Koops wrote:
Hi Roman,
yes, you are right, this was a bug in the StringProvider. It's fixed
in the trunk now. Does it
Good day.
This is a well-intentioned albeit somewhat ignorant question: is
anyone using the Noelios standalone server in a production scenario?
I think of all the hundreds of person-years in something like servlet
technology and wonder if the standalone server is more of a
development
Hello,
I notice there is similar problem just posted today. However, it doesn't seem to
have answer yet. Please let me try again...
My restlet application experiences uneven response time and for a while, the
requests would choked then a big load got processed. In order to isolate the
problem, I
Hi Mark,
If you're using the standalone server, how are you doing basic session
management? With cookies?
One of the basics of REST and also Restlet is, that the communication
between client and server is stateless, that means that there are no
session (for more details and reasons see
If you mean the Net connector in Restlet 1.1 (which does not depend on
any robust external HTTP connector), this is indeed only appropriate
for development or lightly loaded scenarios. We use it for some
production embedded applications, for example, some software that runs
as a service and needs
Thank you, Rob, Stephan. I'm triangulating as fast as I can, and
appreciate your feedback.
inline below...
On Sep 30, 2008, at 12:16 PM, Rob Heittman wrote:
If you mean the Net connector in Restlet 1.1 (which does not depend on
any robust external HTTP connector), this is indeed only
Hi Mark,
I'm just making this up as I go along, but I'm not opposed to learning
something in the process :-) So I had envisioned that my Restlet
application would have two logical clients: 1) the browser for some
requests, and 2) embedded Ajax for others. And I'm starting to wonder
if I
I see that I am in fact using the Simple connector, as per the FirstResource
tutorial, I went out of my way to put its jar on the classpath. This
configuration is what I meant by 'standalone server'.
I like Simple in concept, but I've had some not-so-wonderful
experiences with it in practice.
On Tue, Sep 30, 2008 at 5:55 PM, Rob Heittman [EMAIL PROTECTED]wrote:
P.S. Since Restlet doesn't do it on its own yet, here's my browser
identity cookie generator:
http://gogoego.googlecode.com/svn/trunk/modules/RestletFoundation/src/com/solertium/container/CookieUtility.java
Thanks for
Using an atomic makes more sense. This class predates my reading of
your book ;-) Although, looking at this again, I'm embarrassed to
admit I'm not sure *why* synchronizing on incr doesn't do anything.
Because I'm reassigning it?
Slight problem with newUniqueID(), though. Synchronizing on
Yes. In *Java Concurrency in Practice* lingo, you need to be able to declare
of any non-final, non-volatile field f that is potentially accessed by
multiple threads that f is @GuardedBy(something), where something is
usually this for non-static fields, but could be any object, like the
referent of
I'm using GWT and Restlet 1.1-SNAPSHOT. My server provides a Directory,
from which I can GET a text file and display it in an editable TextArea
in the browser. I have a button that should PUT the modified contents
back to the server but the PUT fails on the server with:
WARNING:
Server OS details? This comes up often on Windows, which will not
allow you to delete a file that has an InputStream open to it. Not
sure why an InputStream would still be open, though ... it's not a
feature if it is.
On Tue, Sep 30, 2008 at 8:48 PM, Jeff Ramsdale [EMAIL PROTECTED] wrote:
I'm
Right. So if it was desirable to do so (for example, if I was doing
something more complicated than counting) I could have declared a random
Object lockObject and the block would be functional, at least.
/threadjack
- R
On Tue, Sep 30, 2008 at 8:30 PM, Tim Peierls [EMAIL PROTECTED] wrote:
In
Shockingly, I'm on Windows XP Pro. Anything special I should do to make
sure I'm not leaving something open?
-jeff
Rob Heittman wrote:
Server OS details? This comes up often on Windows, which will not
allow you to delete a file that has an InputStream open to it. Not
sure why an InputStream
22 matches
Mail list logo
