First, if you want to have a soap endpoint, you need to use
<http:soap-consumer/>
instead of <http:consumer/>. Then for you OOM error, i think it's
mostly a problem
of tuning the thread pools.
Try increasing the servicemix.corePoolSize in
conf/servicemix.properties to 16 maybe,
and try increasing the amount of memory available by ServiceMix.
50 users is not a big number and with the proper configuration, it
should work without any
doubts.
On Sat, May 17, 2008 at 8:46 AM, navigator09 <[EMAIL PROTECTED]> wrote:
>
> Bruce,
>
> I tried making the change from http:endpoint to http:consumer as suggested
> by you. However, now I am getting the following error when trying to access
> the front end wsdl
>
> org.codehaus.xfire.XFireRuntimeException: Couldn't parse stream.. Nested
> excepti
> on is com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
> at [row,col {unknown-source}]: [1,0]
> com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
> at [row,col {unknown-source}]: [1,0]
> at
> com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:6
> 61)
> at
> com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:21
> 34)
> at
> com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.ja
> va:2040)
> at
> com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
> at
> org.codehaus.xfire.util.stax.DepthXMLStreamReader.next(DepthXMLStream
> Reader.java:252)
> at
> org.codehaus.xfire.util.STAXUtils.toNextElement(STAXUtils.java:83)
> at
> org.codehaus.xfire.jaxws.JAXWSBinding.readMessage(JAXWSBinding.java:4
> 1)
> at
> org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandle
> r.java:42)
> at
> org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.jav
> a:131)
> at
> org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoin
> t.java:64)
> at
> org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.
> java:38)
> at
> org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181Ex
> changeProcessor.java:114)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLi
> feCycle.java:538)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(Async
> BaseLifeCycle.java:490)
> at
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLife
> Cycle.java:46)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBoun
> d(DeliveryChannelImpl.java:610)
> at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlo
> w.java:170)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.j
> ava:167)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.jav
> a:134)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
> utor.java:650)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
> .java:675)
> at java.lang.Thread.run(Thread.java:595)
>
> The old http su xbean.xml is as follows
>
> <http:endpoint service="vdssfrontend:Vdssfrontend"
> endpoint="VDSS"
> role="consumer"
> locationURI="http://pd190:8192/vdss";
> soap="true" />
>
> and the modified xbean.xnl is as follows
>
> <http:consumer service="vdssfrontend:httplistener"
> endpoint="listenerEndpoint"
> locationURI="http://pd92:8192/vdss";
> defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
> targetService="vdssfrontend:Vdssfrontend"/>
>
> Also bruce, we have completed the entire integration of the backend system
> over a span of 3 months. In case the load test dosent work for atleast 50
> users ( which is supported by the back-end) the whole development will be
> rejected.
>
> Regards,
> Ganesh
>
>
>
>
>
> bsnyder wrote:
>>
>> On Thu, May 15, 2008 at 11:42 PM, navigator09 <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> Hi,
>>>
>>> We are using servicemix in a production environment to integrate
>>> products.
>>> The servicemic components we are using are 1. Http Su 2. JSR SU.
>>>
>>> The complete configuration runs fine with a small number of concurrent
>>> users (20). But when the number of users increases beyond this number ,
>>> some
>>> threads complete their execution while the others throw the following
>>> error
>>>
>>> java.lang.OutOfMemoryError
>>> at java.lang.StringCoding.encode(StringCoding.java:599)
>>> at java.lang.String.getBytes(String.java:641)
>>> at
>>> org.apache.servicemix.jbi.jaxp.StringSource.getInputStream(StringSource.java:60)
>>> at
>>> com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:719)
>>> at
>>> com.ctc.wstx.stax.WstxInputFactory.createXMLStreamReader(WstxInputFactory.java:341)
>>> at
>>> org.apache.servicemix.jbi.jaxp.StAXSourceTransformer.toXMLStreamReader(StAXSourceTransformer.java:84)
>>> at
>>> org.apache.servicemix.soap.marshalers.SoapWriter.writeContents(SoapWriter.java:218)
>>> at
>>> org.apache.servicemix.soap.marshalers.SoapWriter.writeSoapEnvelope(SoapWriter.java:211)
>>> at
>>> org.apache.servicemix.soap.marshalers.SoapWriter.writeSimpleMessage(SoapWriter.java:113)
>>> at
>>> org.apache.servicemix.soap.marshalers.SoapWriter.write(SoapWriter.java:92)
>>> at
>>> org.apache.servicemix.http.processors.ConsumerProcessor.processResponse(ConsumerProcessor.java:222)
>>> at
>>> org.apache.servicemix.http.processors.ConsumerProcessor.process(ConsumerProcessor.java:203)
>>> at
>>> org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java:71)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
>>> at
>>> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
>>> at
>>> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
>>> at
>>> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
>>> at
>>> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
>>> at
>>> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
>>> at
>>> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
>>> at org.mortbay.jetty.Server.handle(Server.java:313)
>>> at
>>> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)
>>> at
>>> org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:375)
>>> at
>>> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)
>>> at
>>> org.mortbay.jetty.nio.SelectChannelConnector$RetryContinuation.run(SelectChannelConnector.java:511)
>>> at
>>> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
>>> 18:58:44,511 | WARN | btpool1-30 | jetty |
>>> ervicemix.http.jetty.JCLLogger 96 | Error for /vdss/
>>>
>>> I tried the following methods
>>>
>>> 1. Increase the java memory size in the servicemix.bat file.
>>> 2. Increase the value of the properties in the components.properties
>>> file.
>>>
>>> However it still continues to give me the same error. Pls let me know how
>>> to
>>> solve the problem.
>>
>> Well it looks like a Jetty thread pool is being exhausted. Are you
>> using the http:endpoint in your xbean.xml configuration? If so, I'm
>> curious to see your results when using the http:consumer instead of
>> the http:endpoint.
>>
>> Bruce
>> --
>> perl -e 'print
>> unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
>> );'
>>
>> Apache ActiveMQ - http://activemq.org/
>> Apache Camel - http://activemq.org/camel/
>> Apache ServiceMix - http://servicemix.org/
>> Apache Geronimo - http://geronimo.apache.org/
>>
>> Blog: http://bruceblog.org/
>>
>>
>
> --
> View this message in context:
> http://www.nabble.com/Servicemix-Load-Test-Errors-tp17268028p17288707.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
