Good call, Jon. I added -Xmx64m to torque.sh's java command and all
went smoothly. How do we prevent others from running into the same
problem? Should we add the boost to torque.sh & torque.bat, although
it might be VM-dependent, or should it be in a FAQ somewhere?
Carl
Jon Stevens wrote:
>
> on 1/16/01 3:40 PM, "Carl Ludewig" <[EMAIL PROTECTED]> wrote:
>
> > We have a schema with 29 tables, and Torque seems to hang after about 10
> > seconds.
> > If we split the schema in half, each half works fine. I tried the test on a
> > simple schema
> > with no foreign keys, etc. and got the same results.
>
> Anything in the turbine.log or velocity.log files? My guess is that your JVM
> is running out of memory.
>
> > Is there any built-in
> > upper bound
> > in Torque with regards to the number of tables or processing time?
>
> of course not.
>
> -jon
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
