For 2 years i've had problems with an Upcloud server 16gig RAM.
Whenever I leave logging on from a night of programming, the next day Aware will crash.

Recently I was reading a thread where someone said to examine your memory usage... ok, here it is:

According to this, I have WAY TOO MUCH ram allocated.
Yet, I had a crash an hour ago on latest 8.6, even though I restarted last night and turned production logging on, but when done, I unchecked the logging box.

There has been something really flakey about Logging since he went to this new style.
I FREQUENTLY cannot just "turn logging on" - even though the menu option will now appear enabled, NOTHING will appear in the logs until a restart of Aware. And this is REALLY a PITA when during the day, a customer says something itsn't working right, and you can't just [x] enable Logging for 5 mins to check. YOU CAN enable it, just nothing new will appear in the logs... without an Aware restart, which you can't do because its during work hours and bosses would like to have people working, not on smoke breaks. (Some of this is SOMETIMES because you delete the main.log or system.log file (like after a version update) and Aware DOES NOT understand how to correctly create the log file if its not there. Very odd, and reported year(s) ago - but no joy.)
Anyway, since its confused when enabling logging, I think its also confused when disabling. And unless I set NO logging and restart Aware, I'll get a crash.

I HAVE SEEN error message related to MESSAGE QUEUE OVERFLOW stuff - didn't see that today. Just that this server has been up a month or two and the 1st day I have logging turned on (but switched off) it crashes. Yet I have plenty of RAM available.

ALSO _ I have reported before of very odd hacking that has crashed Tomcat (viewable in the logs) but today this wasn't the case.

Could it not be a setting in the awareim.CONF file, java heap size or logging properties setting ?

...Well I don't think so , i can't get my BSV running in 8.7, complains about running out of memory when of I have plenty setup.Tried all sorts of config in the awareim.conf file.

Sounds like it could be related to your problem, memory settings in the setup being ignored by the JVM.

I never had a problem in 8.6 though, but now with all the extra stuff in 8.7 maybe its pushed my BSV over the edge

I wonder if its the OpenJDK version playing up

i don't see "awareim.conf"
what is that?

i don't see "awareim.conf"
what is that?

Its in c:\AwareIM\bin

1. seems to me the only 2 things in there relevant would be:

Initial Java Heap Size (in MB)

wrapper.java.initmemory=20

Maximum Java Heap Size (in MB)

wrapper.java.maxmemory=256

2. Isn't this only used for Aware as a Service? Mine doesn't run as a service.
   see are awareim.conf and wrapper.conf only for running as SVC?

2. Isn't this only used for Aware as a Service? Mine doesn't run as a service.
see are awareim.conf and wrapper.conf only for running as SVC?>

I realised that when replying to you, so where do you setup up java heap size ?

ACDC wrote

Could it not be a setting in the awareim.CONF file, java heap size or logging properties setting ?

...Well I don't think so , i can't get my BSV running in 8.7, complains about running out of memory when of I have plenty setup.Tried all sorts of config in the awareim.conf file.

Sounds like it could be related to your problem, memory settings in the setup being ignored by the JVM.

I never had a problem in 8.6 though, but now with all the extra stuff in 8.7 maybe its pushed my BSV over the edge

I wonder if its the OpenJDK version playing up

related to your mem issues, remember this thread
How do you pass VM arguments to CP.exe?

from my initial image, those 3000 values for memory are saved/used here:

FILE: \awareim\bin\startupOptions.props

#Wed Feb 16 00:25:46 EST 2022
CONFIG_TOOL_STARTUP=..\\JDK\\bin\\java -classpath ../docs/help.jar;../lib/* com.bas.uiconfiguration.Application
AWAREIM_SERVER_STARTUP=..\\JDK\\bin\\java -Xmx3000m -Xms512m -classpath ../lib/*;../CustomJars/* com.bas.newcp.ServerStarterECP
TOMCAT_STARTUP=..\\JDK\\bin\\java -Xmx3000m -Xms512m -classpath ../Tomcat/bin/bootstrap.jar;../Tomcat/bi <...snip>

this stackoverflow page talks about those -X settings

The accepted answer starts off saying "The flag Xmx specifies the maximum memory allocation pool for a Java Virtual Machine (JVM), while Xms specifies the initial memory allocation pool."

... but then also references Oracle's documentation that says "Note that the JVM uses more memory than just the heap. For example Java methods, thread stacks and native handles are allocated in memory separate from the heap, as well as JVM internal data structures."

Makes me wonder if when you view TASK MANAGER and see the memory usage there if thats the total that Oracle talks about. If so, I'm still way under the 3000m max.