MSIR.0470 SYBMSG(20470,15,1) Can't start new thread, MAXCURS exceeded: Difference between revisions

From m204wiki
Jump to navigation Jump to search
mNo edit summary
(Automatically generated page update)
Line 1: Line 1:
A <var class="product">[http://m204wiki.rocketsoftware.com/images/e/e4/JsdsrNew.pdf Janus Specialty Data Store]</var> thread could not open a new thread as required by the middleware with which it is communicating (presumably a Sybase Adaptive Server) because the middleware had already opened the number of threads indicated by the MAXCURS parameter on the port definition (MAXCURS defaults to 5). Either STOP and DELETE the port and increase MAXCURS, or try to determine why the middleware should require so many threads (5 should be sufficient for most purposes).
A <var class="product">[http://m204wiki.rocketsoftware.com/images/e/e4/JsdsrNew.pdf Janus Specialty Data Store]</var> thread could not open a new thread as required by the middleware with which it is communicating (presumably a Sybase Adaptive Server) because the middleware had already opened the number of threads indicated by the MAXCURS parameter on the port definition (MAXCURS defaults to 5). Either STOP and DELETE the port and increase MAXCURS, or try to determine why the middleware should require so many threads (5 should be sufficient for most purposes).


[[Category:Sirius Mods messages]]
[[Category:Sirius Mods messages]] [[Category:MSIR.0400 - MSIR.0599]]

Revision as of 15:56, 13 August 2015

A Janus Specialty Data Store thread could not open a new thread as required by the middleware with which it is communicating (presumably a Sybase Adaptive Server) because the middleware had already opened the number of threads indicated by the MAXCURS parameter on the port definition (MAXCURS defaults to 5). Either STOP and DELETE the port and increase MAXCURS, or try to determine why the middleware should require so many threads (5 should be sufficient for most purposes).