users@jersey.java.net

[Jersey] Re: Jersey Test Framework and load testing?

From: Mike Summers <msummers57_at_gmail.com>
Date: Mon, 24 Sep 2012 06:38:31 -0500

Thanks Pavel.

Interesting, I cannot get either Grizzly2 or InMemory to work, they both
explode on startup with contiperf although they work fine without it.

Good deal on point #2. All of my code is @Provider, Mapper, ...
infrastructure, and once the JUnit works I need it stressed without the
container resetting to detect interaction issues.


On Sun, Sep 23, 2012 at 11:02 PM, Pavel Bucek <pavel.bucek_at_oracle.com>wrote:

> On 9/23/12 5:33 AM, Mike Summers wrote:
>
> Jersey Test Framework and contiperf are working well testing our app with
> multiple concurrent requests into a single container. Every "problem" has
> ultimately been an application or 3rd party library issue... generally
> misuse of static vars.
>
> Two points to keep in-mind:
> 1) the Grizzly container works well, the others not so much
>
> InMemory, Grizzly2 and External also works. Embedded Glassfish is not
> really ready and it is not our current priority to improve it.
>
>
> 2) only one @Test per container instance so the test builds itself
> reflecting on the REST API
>
>
> Well, that depends on your application, but we already have RFE for
> resetting/redeploying after every test, so this should be solved soon (at
> least in Jersey 2.x)
>
> Pavel
>
>
>
>
>
> On Mon, Sep 10, 2012 at 8:44 AM, Mike Summers <msummers57_at_gmail.com>wrote:
>
>> Thanks Pavel.
>>
>> Load tests are on this week's agenda, I'll let you know what I discover.
>>
>> --Mike
>>
>>
>> On Mon, Sep 10, 2012 at 8:38 AM, Pavel Bucek <pavel.bucek_at_oracle.com>wrote:
>>
>>> Hello Mike,
>>>
>>> load testing is something completely different from purpose of Jersey
>>> Test Framework, which is designed to create "simple" end-to-end tests. You
>>> might want to look at apache ab or jmeter. JUnitPert looks ok too, but we
>>> don't have any experience with it.
>>>
>>> Regards,
>>> Pavel
>>>
>>>
>>> On 9/7/12 4:57 PM, Mike Summers wrote:
>>>
>>>> I need to shoot a bug that appears to be load related and thought about
>>>> turning one of my Jersey Test Framework tests loose for an extended period
>>>> of time to see if I can trip things up.
>>>>
>>>> I need the container to be instantiated just once, and I'd like
>>>> multiple test threads banging on it.
>>>>
>>>> What if anything do you use to do this?
>>>>
>>>> I'm getting ready to try JUnitPerf, anyone had any luck with this?
>>>> Selenium?
>>>>
>>>> Thanks-- Mike
>>>>
>>>
>>>
>>
>
>