On Sun, Oct 7, 2012 at 6:18 PM, Staffan Tylen <staffan.ty...@gmail.com>wrote:

> I'm experiencing a problem with repeated *"Error 48.1:  Failure in system
> service: ERROR CREATING THREAD*" messages. The program is initiating a
> large number of threads using the start method and it seems like I've hit a
> limit of some sort. Is this something that can be adjusted or do I have to
> restrict the number of concurrent threads, if so what is the limit? I'm
> tempted to switch to the 64bit version of ooRexx to see if that helps, but
> by doing that I cannot guarantee that the program will work in a 32bit
> environment, which I'm aiming for.
>

There is nothing built in to the interpreter that limits the number of
threads other than the number allowed by the operating system.  I'm not
sure if you'll get any more by using the 64-bit interpreter or not.

Rick


>
> ooRexx 4.1.2, 32bit, Windows 7
>
> Thanks,
> Staffan
>
>
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> Oorexx-users mailing list
> Oorexx-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-users
>
>
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users

Reply via email to