CSWB 1.7.8. crash when TOMCAT active

[Willem Grooters]

Yesterday, I have upgraded CSWB from verion 1.4 to 1.7.8, after I installed all required VMS patches. After reboot, I installed the CSWB files (after I updated PGFLQUO and FILLM according the documentation) and I could run it properly.
But when TOMCAT was started, it crashes with the attached dump.

I'm running JAVA 1.4.2 (not yet P2, will be done).

It might have to do with Global pages (too few left) but in that case, I'd expect a more eloaborate ending...
Anyone an idea what might be the case?

[Ian Miller.]

ACCVIO due to read from address 0 - probably someone not checking the result of a malloc which could fail due to a quota problem.
You can see the number of free global pages in various was but
$ install list/g/su
is my usual. Also monitor process quotas - either in real time using (tool of your choice) or look at the accounting record of the process may give you a hint.

[Willem Grooters]

I don't think process quota are a problem here: Tomcat starts as a detached process and CSWB is run in my interactive session. Global pages may constitute a problem but what I don't understand why the ACCVIO happens. Bad error handling could be a reason and than I'd consider this a bug: It should have told me "Out of resources" in some way, shouldn't it?
Anyway, I'll take your suggestion on this and look into the free space available.

[Willem Grooters]

OK:

$ install list /g/su

Galaxy Group Global Sections


760 Global Sections Used, 381456/213680 Global Pagelets Used/Unused

I added the current sysgen data. It all seems quite good.

[Willem Grooters]

Problem can no longer be reproduced; It may have been that logging off cleared a thing or two? Installation of JAVA 1.4.2-P2? Who knows...

[Willem Grooters]

It did happen again, now using Java 1.4.2-P2 as supplied fy HP.
Rebooted the machine after VMS patch installations. In the startup sequence, Tomcat and Apache are started in batch, but it's a known fact Tomcat will fail (something to do with a logical not properly set, it seems. Still under investigation).
Logged in (as SYSTEM), stopped Apache using SYS$STARTUP:APACHE$SHUTDOWN, and executed the procedure that will start Tomcat and Apache interactively (by invoking the supplied procedures).
When CSWB is now started, the message shows up.
After logout, and login again, there is no problem at all.

CSWB has been set up to enable Java.
I'm using the classic VM (not enough memory to run FastVM).

Willem