Windows Server
V 1157
When uploading a new BSV I am receiving the following error;
Server encountered an exception java.lang.OutOfMemoryError
Two bsv's prior to the error were uploaded without any trouble. Server shows know memory leakage and has been restarted. Aware v1157 has been re-installed. Logs show nothing unusual and the startup file in the aware bin dir is correct.
Upload BSV error
-
aware_support
- Posts: 7526
- Joined: Sun Apr 24, 2005 12:36 am
- Contact:
-
christopherb
- Posts: 304
- Joined: Fri Jun 22, 2007 8:26 pm
Support,
c'mon that's the first thing i did. This did not solve the problem. As stated before this was not an issue prior even without pre-memory increase. The application runs as normal speed with no errors shown when running any of the large processes contained within the application.
Could it be something other maybe i didn't think of?
c'mon that's the first thing i did. This did not solve the problem. As stated before this was not an issue prior even without pre-memory increase. The application runs as normal speed with no errors shown when running any of the large processes contained within the application.
Could it be something other maybe i didn't think of?
Cheers,
Christopher
Christopher
-
aware_support
- Posts: 7526
- Joined: Sun Apr 24, 2005 12:36 am
- Contact:
No, it is memory, no doubt about it. Which components did you increase memory for?
I assume this is upload via the browser, not import in the Configuration Tool?
If so, then any of the 3 components (Aware IM Server, Tomcat and JBoss) may need the memory increased - you need to play with all 3. If you just increased the memory for the Aware IM Server, for example, it might not have solved the problem, because some other component is running out of memory. My guess is that it's JBoss in this case.
I assume this is upload via the browser, not import in the Configuration Tool?
If so, then any of the 3 components (Aware IM Server, Tomcat and JBoss) may need the memory increased - you need to play with all 3. If you just increased the memory for the Aware IM Server, for example, it might not have solved the problem, because some other component is running out of memory. My guess is that it's JBoss in this case.
Aware IM Support Team