Comments on: BlazeDS and LCDS Performace difference http://sujitreddyg.wordpress.com/2008/02/04/blazeds-and-lcds-performace-difference/ Mon, 16 Nov 2009 08:57:21 +0000 http://wordpress.com/ hourly 1 By: Ronny http://sujitreddyg.wordpress.com/2008/02/04/blazeds-and-lcds-performace-difference/#comment-27630 Ronny Fri, 09 Oct 2009 08:32:29 +0000 http://sujitreddyg.wordpress.com/?p=32#comment-27630 Mohan: did you find a solution? I got the exact same problem. Mohan: did you find a solution? I got the exact same problem.

]]> By: Kapil Viren Ahuja http://sujitreddyg.wordpress.com/2008/02/04/blazeds-and-lcds-performace-difference/#comment-27555 Kapil Viren Ahuja Thu, 17 Sep 2009 14:27:18 +0000 http://sujitreddyg.wordpress.com/?p=32#comment-27555 NIO is available in LCDS. However, BlazeDS is not going to use it. As of what I heard last, Adobe will stop supporting BlazeDS very soon. By the way - great explanation. NIO is available in LCDS. However, BlazeDS is not going to use it. As of what I heard last, Adobe will stop supporting BlazeDS very soon.

By the way – great explanation.

]]> By: Mahesh http://sujitreddyg.wordpress.com/2008/02/04/blazeds-and-lcds-performace-difference/#comment-27068 Mahesh Thu, 02 Jul 2009 10:46:56 +0000 http://sujitreddyg.wordpress.com/?p=32#comment-27068 Hi Sujit, Im new to BlazeDS. And Im in the process of evaluating BlazeDS's AMF Channeled Remoting technique and traditional HTTPService calls for our Flex app. The deserialization by BlazeDS seems a better advantage over converting Java objects in to XML. But Isnt this deserialization a over head as compared with java-->XML conversion?? This evaluation is on the basis of number of (multiple) users hitting the app. Please share your thought on this. Hi Sujit,
Im new to BlazeDS. And Im in the process of evaluating BlazeDS’s AMF Channeled Remoting technique and traditional HTTPService calls for our Flex app. The deserialization by BlazeDS seems a better advantage over converting Java objects in to XML. But Isnt this deserialization a over head as compared with java–>XML conversion?? This evaluation is on the basis of number of (multiple) users hitting the app. Please share your thought on this.

]]> By: Mohan http://sujitreddyg.wordpress.com/2008/02/04/blazeds-and-lcds-performace-difference/#comment-19105 Mohan Sat, 25 Apr 2009 10:04:15 +0000 http://sujitreddyg.wordpress.com/?p=32#comment-19105 The PUSH thread has been Locked so that all threads were blocked Stack trace: java.net.SocketOutputStream.socketWrite0(Native Method) java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) java.net.SocketOutputStream.write(SocketOutputStream.java:136) org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:737) org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434) org.apache.coyote.http11.InternalOutputBuffer.flush(InternalOutputBuffer.java:299) org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:963) org.apache.coyote.Response.action(Response.java:183) org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:314) org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:288) org.apache.catalina.connector.Response.flushBuffer(Response.java:548) org.apache.catalina.connector.ResponseFacade.flushBuffer(ResponseFacade.java:279) flex.messaging.endpoints.BaseStreamingHTTPEndpoint.streamChunk(BaseStreamingHTTPEndpoint.java:1159) flex.messaging.endpoints.StreamingAMFEndpoint.streamMessages(StreamingAMFEndpoint.java:248) flex.messaging.endpoints.BaseStreamingHTTPEndpoint.handleFlexClientStreamingOpenRequest(BaseStreamingHTTPEndpoint.java:912) - locked java.lang.Object@2c4eed84 flex.messaging.endpoints.BaseStreamingHTTPEndpoint.serviceStreamingRequest(BaseStreamingHTTPEndpoint.java:1131) flex.messaging.endpoints.BaseStreamingHTTPEndpoint.service(BaseStreamingHTTPEndpoint.java:468) flex.messaging.MessageBrokerServlet.service(MessageBrokerServlet.java:377) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) java.lang.Thread.run(Thread.java:619) The PUSH thread has been Locked so that all threads were blocked
Stack trace:
java.net.SocketOutputStream.socketWrite0(Native Method)
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
java.net.SocketOutputStream.write(SocketOutputStream.java:136)
org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:737)
org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434)
org.apache.coyote.http11.InternalOutputBuffer.flush(InternalOutputBuffer.java:299)
org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:963)
org.apache.coyote.Response.action(Response.java:183)
org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:314)
org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:288)
org.apache.catalina.connector.Response.flushBuffer(Response.java:548)
org.apache.catalina.connector.ResponseFacade.flushBuffer(ResponseFacade.java:279)
flex.messaging.endpoints.BaseStreamingHTTPEndpoint.streamChunk(BaseStreamingHTTPEndpoint.java:1159)
flex.messaging.endpoints.StreamingAMFEndpoint.streamMessages(StreamingAMFEndpoint.java:248)
flex.messaging.endpoints.BaseStreamingHTTPEndpoint.handleFlexClientStreamingOpenRequest(BaseStreamingHTTPEndpoint.java:912)
– locked java.lang.Object@2c4eed84
flex.messaging.endpoints.BaseStreamingHTTPEndpoint.serviceStreamingRequest(BaseStreamingHTTPEndpoint.java:1131)
flex.messaging.endpoints.BaseStreamingHTTPEndpoint.service(BaseStreamingHTTPEndpoint.java:468)
flex.messaging.MessageBrokerServlet.service(MessageBrokerServlet.java:377)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
java.lang.Thread.run(Thread.java:619)

]]> By: Sujit Reddy G http://sujitreddyg.wordpress.com/2008/02/04/blazeds-and-lcds-performace-difference/#comment-76 Sujit Reddy G Thu, 14 Feb 2008 15:13:21 +0000 http://sujitreddyg.wordpress.com/?p=32#comment-76 Hi Adam, BlazeDS will start using non-blocking IO API, once they are available. This might take some time. :) Hi Adam,
BlazeDS will start using non-blocking IO API, once they are available. This might take some time. :)

]]> By: Adam http://sujitreddyg.wordpress.com/2008/02/04/blazeds-and-lcds-performace-difference/#comment-75 Adam Thu, 14 Feb 2008 02:23:11 +0000 http://sujitreddyg.wordpress.com/?p=32#comment-75 Five minutes I came across this in the BlazeDS documentation: "each streaming connection open between a FlexClient and the streaming endpoints uses a thread on the server" and I almost screamed. Your post is one of the first that came up in the frenzied Google search that followed. There go my hopes of creating a low-cost performant data streaming solution! It is not totally rocket science to write an NIO server. Do you know if BlazeDS is going to go in that direction? Do you think they will go in that direction before my site gets to a thousand simultaneous users? If so, I'm gonna stick with a 1-CPU installation of LCDS until it happens. Five minutes I came across this in the BlazeDS documentation: “each streaming connection open between a FlexClient and the streaming endpoints uses a thread on the server” and I almost screamed. Your post is one of the first that came up in the frenzied Google search that followed. There go my hopes of creating a low-cost performant data streaming solution! It is not totally rocket science to write an NIO server. Do you know if BlazeDS is going to go in that direction? Do you think they will go in that direction before my site gets to a thousand simultaneous users? If so, I’m gonna stick with a 1-CPU installation of LCDS until it happens.

]]>