[ 
https://issues.apache.org/jira/browse/AXIS2-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291519#comment-13291519
 ] 

Rohit edited comment on AXIS2-5338 at 6/9/12 12:21 PM:
-------------------------------------------------------

Many Many thanks sagara. I was little bit wrong while porting 1.6.2 
upgradation. Today i reworked on upgradation from 1.5.3 to axis1.6.2 and things 
seems to be working fantastic.
One issue is concurrent transaction sometimes changes namespace. please suggest 
pointer to set statis namespace.
                
      was (Author: rohiitj):
    Many Many thanks sagara. I was little bit wrong while porting 1.6.2 
upgradation. Today i reworked on upgradation from 1.5.3 to axis1.6.2 and things 
seems to be working fantastic.
one minor issue i am facing is i am getting new namespaces in response 
everytime i fire the request. is there any way to fetch the static namespace 
against xml nodes...?
                  
> Axis1.5.3 Web service application unable to open more then 50 Concurrent 
> Connections when tested from load runner.
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-5338
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5338
>             Project: Axis2
>          Issue Type: Bug
>          Components: transports
>            Reporter: Rohit
>            Priority: Blocker
>
> I have a axis application through which i am hosting many services. Currently 
> i am doing benchmark.
> My application is deployed on weblogic. and i am running load test from Load 
> Runner.
> I cod see only 50 connections are getting opened per second for 100vusers.
> expectation is more than 90connections. Alternatively i created one more 
> parallel managed wls server(total 2 now) and added the url of same Load 
> Runner, i could see Connection per sec raised to 80/sec. i.e. 40 each.
> I want to achieve Connections of 100per sec from 1 server only which is not 
> possible due to axis2 limiting connection bandwidth.
> I have done lot of analysis. But codnt find any of the solution remarkable. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

Reply via email to