Tested 64-bit Tomcat+ooRexx on Linux using the same Java 17LTS as on Windows and a debug build of ooRexx from trunk (r12316) and the same web application that uses ooRexx in JSPs as on the Windows Tomcat server.
The test will request constantly the same ooRexx JSP page from the Linux server for ten seconds and repeat it once. Each request will cause a Rexx interpreter instance RII to be created in the Tomcat server to execute all Rexx scripts in the requested JSP. (This rii will also have its .output redirected to the 'out'-Java object for that JSP run, such that output of say statements will get sent back as normal text to the client.) After restarting Tomcat, the very first run of fetching as quickly as possible the ooRexx test JSP will be rather quick up (appr. 13 msecs/req) to request # 400 (sometimes up to # 600) after which the requests get visually slower and slower and then (after appr. 30 more requests) start to need a little bit more than a second for each request (e.g. 1179 msecs/req) to return as if something blocks ooRexx serving the JSP. From this point on each request will need a little bit more than a second (a timeout?) until Tomcat gets restarted. Not sure how to debug this, so any advice, ideas and hints very welcome! ---rony P.S.: Did test with three builds of ooRexx from trunk, release, relWithDebInfo, debug, all exhibiting the same behaviour. P.P.S.: There are no errors in the various Linux Tomcat log files. P.P.P.S.: Tomcat on the Windows server, since yesterday's fix, remains responsive no matter how many requests with ooRexx in JSPs get sent to it. _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
