Liteview memory issues

[Anonymous]

We have recently deployed a liteview application(server specs detailed below) and are running into problems with Tomcat hanging up intermitttently.
The error message in the log file says " - Java Edition timed out at 30 seconds".
The tomcat window has the following error: "java.lang.OutofmemoryError <
We recently increased our RAM from 1gB to 4gB. Also added an additional processor. The servlet guider recommends setting the -XMS and -XMX to 2/3 of RAM. However,Tomcat refuses to start up if we assign more than 1.7gB to the -xmx and .xms settings.
Any suggestions would be greatly apprecaited.

Server Info:
Windows 2003 Server 5.2.3790
IIS and Tomcat 3.3.1a
JDK 1.3
Cold fusion 4.5
Enterprise Oracle Client(9i for ODBC and 10g for ODAC)

[Anonymous]

This, and other memory errors, are common to LiteView installations. After
running into similar problems for a client a number of years ago and with no
fix from Autodesk, we abandoned LiteView and no longer recommend its
implementation in any environment. These issues have been acknowledged by
Autodesk, but do not expect to see a solution since they are concentrating
their efforts on the new MapGuide Open Source and MapGuide Enterprise which
are new (much better) architectures. MapGuide Open has an AJAX viewer (no
plugin needed) and is far superior to LiteView. You should look at
implementing this platform as your viewerless solution and do away with
LiteView entirely.


--
Andy Morsell, P.E.
Spatial Integrators, Inc.
http://www.SpatialGIS.com


wrote in message news:5111955@discussion.autodesk.com...
We have recently deployed a liteview application(server specs detailed
below) and are running into problems with Tomcat hanging up intermitttently.
The error message in the log file says " - Java Edition timed out at 30
seconds".
The tomcat window has the following error: "java.lang.OutofmemoryError <
stack trace available"

We recently increased our RAM from 1gB to 4gB. Also added an additional
processor. The servlet guider recommends setting the -XMS and -XMX to 2/3
of RAM. However,Tomcat refuses to start up if we assign more than 1.7gB to
the -xmx and .xms settings.
Any suggestions would be greatly apprecaited.

Server Info:
Windows 2003 Server 5.2.3790
IIS and Tomcat 3.3.1a
JDK 1.3
Cold fusion 4.5
Enterprise Oracle Client(9i for ODBC and 10g for ODAC)