[
https://wso2.org/jira/browse/MASHUP-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691#action_15691
]
Tyrell Perera commented on MASHUP-693:
--------------------------------------
This isn't a bug. It is a performance tweak, which needs to be done in a
production deployment.
In conf/axis2.xml there is a parameter called 'maxThreads', which defaults to
150 in a personal server.
One can increase this number depending on the hardware resources available in
the host machine.
> Error which indicating 'maxThreads (150) are being used' appear when 60
> concirrent users are accessing the server.
> ------------------------------------------------------------------------------------------------------------------
>
> Key: MASHUP-693
> URL: https://wso2.org/jira/browse/MASHUP-693
> Project: WSO2 Mashup Server
> Issue Type: Bug
> Components: Core
> Environment: WinXP, JDK1.5
> Reporter: Yumani Ranaweera
> Assignee: Tyrell Perera
>
> Steps:
> -------
> Run a 60 concurrent users for the following scenario : Sign-in, Search,
> Sighout.
> Issue:
> -------
> The following error appears in the console.
> ERROR [2008-02-21 14:21:41,390] All threads (150) are currently busy,
> waiting. Increase maxThreads (150) or check the servlet status
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
