@Mete Thank you very much for your reply, it helped me a lot. I am able to extend consumer class. and I am able to receive specific message by using selector.
--- In flexcoders@yahoogroups.com, "Mete Atamel" <meteata...@...> wrote: > > We don't have support for selectors in the load-testing-tool yet but it's > very easy to extend the default Consumer.java. If you look into the > internalSend method of mx:Consumer class (http://tinyurl.com/y979gn6), you'll > see that when selector is set, it simply adds a selector header to the > message: > > if (_selector.length > 0) > message.headers[CommandMessage.SELECTOR_HEADER] = _selector; > > Just subclass Consumer.java and override internalSend method to do something > similar. I'll make sure to add selector support in the next version of the > tool. > > Mete > Data Service Team, Adobe Systems. > > --- In flexcoders@yahoogroups.com, "sanjitcs" <sanjit.flex@> wrote: > > > > @Mete thanks you for your reply. > > > > Yes, I am using LCDS 3.0. I have seen the Java based testing tool. I have > > gone through it. I have faced one problem. I want to create a consumer > > which listen for specific message. In Flex we are using mx:consumer > > selector property to get specific message for each user. But I am not be > > able to set selector in this tool. Consumer class does not have setter or > > getter for it. Is there any way to set the selector for consumer. > > > > thanks > > > > > > --- In flexcoders@yahoogroups.com, "Mete Atamel" <meteatamel@> wrote: > > > > > > Are you using LCDS? Because starting in LCDS 3.0, LCDS comes with a Java > > > based load testing tool. It's located under resources/load-testing-tool. > > > We use it internally here at Adobe to do our scalability and performance > > > testing. The latest version which will ship with LCDS 3.1 comes with more > > > useful stuff like latency and message drop detection among other things. > > > It supports testing against BlazeDS Servlet based endpoints, LCDS NIO > > > based endpoints and it has Java versions of mx:Consumer/mx:Producer etc. > > > (no RemoteObject, DataService support yet). > > > > > > > > > -Mete > > > > > > --- In flexcoders@yahoogroups.com, "sanjitcs" <sanjit.flex@> wrote: > > > > > > > > > > > > > > > > thanks for your suggestion arutheunicorn. > > > > I am looking for open source load testing framework. which can help me > > > > to do load testing for messaging on RTMP/RTMPS protocol. > > > > Currently I am developing flex client to do load testing. > > > > If you can provide me direction how can I build java robot that can hit > > > > flex app.. It will be great help for me > > > > > > > > Following are the requirement in short .. > > > > java robot can be able to subscribe multiple consumer to JMS topic with > > > > specific selector and it received data using server side push using > > > > RTMP/RTMPS protocol. > > > > > > > > > > > > Thank you > > > > --- In flexcoders@yahoogroups.com, "arutheunicorn" <arutheunicorn@> > > > > wrote: > > > > > > > > > > > > > > > It depends on what funds you have. Quick Test Pro is the king of the > > > > > hill for overall load & regression testing, followed by it's cheaper > > > > > rival Silk Test by Borland. As for a cheapa$$ solution, you can "try" > > > > > building a Java robot that can hit your flex app....I've done some > > > > > regression testing for Hilton in my days so I know a thing or two > > > > > about the subject. > > > > > --- In flexcoders@yahoogroups.com, "sanjitcs" <sanjit.flex@> wrote: > > > > > > > > > > > > Hi, > > > > > > > > > > > > I am testing application which uses server side push using RTMP > > > > > > protocol to get data from server.I need to perform load testing for > > > > > > application. Could anyone please suggest any Load testing framework. > > > > > > > > > > > > > > > > > > Currently I have tried to develop flex application which subscribes > > > > > > different consumer. I am assuming that it behaves like different > > > > > > consumer(i.e user for application). and i able to load test. Could > > > > > > any one please tells whether assumption is right or wrong. > > > > > > > > > > > > > > > > > > > > >
