Hi,
I was looking at using the maxActiveConnections in the application context,
what I find is. When I reach the limit, as expected the server will not
create a new session, however does return a http 200 status code.
I am wondering would it be possible for me to change this behavior to
return
On Aug 13, 2013, at 6:43 AM, Smith, Mitchell mitchell.sm...@cwc.com wrote:
Hi,
What version of Tomcat are you using? 6.0.x or 7.0.x?
I was looking at using the maxActiveConnections in the application context,
Please include the relevant configuration from your server.xml or context.xml
On 13 August 2013 13:24, Daniel Mikusa dmik...@gopivotal.com wrote:
On Aug 13, 2013, at 6:43 AM, Smith, Mitchell mitchell.sm...@cwc.com
wrote:
Hi,
What version of Tomcat are you using? 6.0.x or 7.0.x?
Tomcat7
I was looking at using the maxActiveConnections in the application
On Aug 13, 2013, at 9:33 AM, Smith, Mitchell mitchell.sm...@cwc.com wrote:
On 13 August 2013 13:24, Daniel Mikusa dmik...@gopivotal.com wrote:
On Aug 13, 2013, at 6:43 AM, Smith, Mitchell mitchell.sm...@cwc.com
wrote:
Hi,
What version of Tomcat are you using? 6.0.x or 7.0.x?
Dan,
I am currently developing/testing with the latest version: 7.0.42
*Note this is different than the configuration you specified above, which
appears like it's trying to restrict the number of sessions that the
manager will create*
Yes, maxActiveSessions is the parameter I am using. As I know
On Aug 13, 2013, at 11:37 AM, Smith, Mitchell mitchell.sm...@cwc.com wrote:
Dan,
I am currently developing/testing with the latest version: 7.0.42
Excellent!
*Note this is different than the configuration you specified above, which
appears like it's trying to restrict the number of
