Focal Point
[CLOSED] Can we run multiple JSCOM3 services/agents with different configurations?

This topic can be found at:
https://forums.informationbuilders.com/eve/forums/a/tpc/f/7971057331/m/6487041886

October 26, 2017, 04:34 AM
Wep5622
[CLOSED] Can we run multiple JSCOM3 services/agents with different configurations?
Currently, we only use the JSCOM3 service on our WFRS for generating XLSX reports. TO make that work with some of our XLST/XLSM templates, we had to increase the available memory to that service to 1GB. As long as we have only a single JSCOM3 service running, that's okay. A couple would probably still be okay, but as soon as were entering higher counts that is probably not going to fly well.

We are looking into adding a PostgreSQL adapter for our local datawarehouse, and it seems that it also uses JSCOM3, probably because it's using a JDBC connection to the database. Or is there a properly native adapter using libpq? that would have our preference...

Now we don't really need to allocate 1GB of Java memory for each connection to our datawarehouse and we would probably want to ramp up the number of available JSCOM3 agents to more than a single one when we go that route. And we want to go that route, it is a great database at hard to beat costs; we could spend most of the money otherwise wasted on licensing costs on hardware instead. If someone can confirm that the PG adapter does not depend on JSCOM3, that would solve this problem right away!


But if things are as we think they are, then I am wondering whether we can create another group of JSCOM3 agents besides the one named 'DEFAULT', much like we do with tscom3 agents. Is that possible? Where can we configure that?



To add a bit more to the challenge: Because of a memory leak in the XLSX unzip/zip JSCOM3 service, we have a script scheduled in the Windows Scheduler that checks every 5 minutes whether the available memory of the jscom3 process has fallen under 900MB and it kills it when that is the case (it restarts automatically when killed). It's far from an ideal solution, but at least this way our XLSX reports don't stop working for longer than 5 minutes...

Obviously, that hack is going to be a problem if we also have other jscom3 processes that are supposed to use under 900MB of memory. I don't think there is any way from the OS side to distinguish one from another, except maybe for its memory "Commit Size".

This message has been edited. Last edited by: FP Mod Chuck,


WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010
: Member of User Group Benelux :
October 26, 2017, 04:39 AM
Tony A
This is really a question for the ATS group via a case on Tech Support I would suggest.

T



In FOCUS
since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2  
WebFOCUS App Studio 8.2.06 standalone on Windows 10