Getting some weirdness with memory-mapped files on a V7 box

We've got a situation (I'm still far from up to speed on any details) 
involving memory-mapped STMFs in Java on a V7 customer box.

I'm not yet privy to the details of what we're doing, but we're trying 
to offload a cache in a Tomcat webapp context, and it's throwing some 
really weird exceptions at us (but it's apparently working fine on other 
hardware platforms, and on the same V7 box if we're running a test 
program from QShell. Among other things, it's giving out-of-memory 
exceptions, even though there's plenty of heap space (and indeed, the 
Tomcat server is running with -Xmx3072m, in a subsystem with a 3G 
private memory pool), and the Tomcat server itself, and another context 
running in it, aren't being affected.

As my colleague was describing what he was doing, I began to wonder, 
could this somehow be getting into a fight with single-level store?

Does anybody here have the slightest idea what could be going on here?

--
JHHL
-- 
This is the Java Programming on and around the IBM i (JAVA400-L) mailing list
To post a message email: JAVA400-L-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at https://archive.midrange.com/java400-l.