Application Networking Manager Web Services Forums

« Back to Technical Discussion

Concurrent sessions per account

Combination View Flat View Tree View
Threads [ Previous | Next ]
Concurrent sessions per account
session token
Answer
10/19/10 10:27 PM
I am developing an ANM web service client (targeting ANM 4.1) and it appears there is a limit of 5 concurrent sessions per ANM account.  Is this deduction correct?  Is it configurable in ANM such that my account could be configured to allow more than 5?
Flag

RE: Concurrent sessions per account
Answer
11/3/10 12:18 PM as a reply to Andrew Swanson.
I am developing an ANM web service client (targeting ANM 4.1) and it appears there is a limit of 5 concurrent sessions per ANM account.  Is this deduction correct?  Is it configurable in ANM such that my account could be configured to allow more than 5?

 

I am one of the developers for ANM 4.1 ws API, ANM 4.1 only allows 5 concurrent API sessions, and this is not configurable. I would like to know is there any reason you will need more than 5 concurrent ws API sessions.
Flag

RE: Concurrent sessions per account
Answer
11/3/10 7:02 PM as a reply to Lei Zhu.
I am enhancing a JavaEE application and the enhancements include using the ANM web service client.  The application is clustered with each cluster member having 50 web container threads.  So, even with the minimum cluster size of 2 cluster members that makes 100 threads that could potentially want to use the ANM web service client concurrently.  Of course that is unlikely to happen but I hope you can see that heavily multi-threaded applications like those hosted in a clustered web application server environment may need more than 5 concurrent sessions.  Also, besides 5 being a small number it is also an odd number which makes it impossible to split evenly across cluster members. 
Flag

RE: Concurrent sessions per account
Answer
11/4/10 12:31 AM as a reply to Andrew Swanson.
I am enhancing a JavaEE application and the enhancements include using the ANM web service client.  The application is clustered with each cluster member having 50 web container threads.  So, even with the minimum cluster size of 2 cluster members that makes 100 threads that could potentially want to use the ANM web service client concurrently.  Of course that is unlikely to happen but I hope you can see that heavily multi-threaded applications like those hosted in a clustered web application server environment may need more than 5 concurrent sessions.  Also, besides 5 being a small number it is also an odd number which makes it impossible to split evenly across cluster members. 

The reason we limit the ws API sessions to 5 is because API shares the same session pool with ANM GUI, more API sessions will affect the performance on ANM. I suggest you to implement a connection pool, which will take care the connections with ANM. We may consider to make the max API sessions configurable in the future release.
Flag