Thanks Thomas & Greg! Turns out, this is a bit of egg in my face and
a bit of a mystery too... The solution was to set JAVA_HOME to /usr/
java/jdk (which points to /usr/java/jdk1.5.0_06). When leaving it
unset, ant would detect java at /usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/
jre instead and the torque targets would fail. Failure would actually
happen at an earlier point in project-sql when trying to download the
DTD for the schema files (Peer reset connection) if I ran through the
entire process. Just running the project-om target would cause the
error I reported initially also when using velocity 1.3.1. . Now the
mystery to me is how ant would pick the wrong java home... but that
is definitely off topic!
Anyways, for my (and maybe other's) education, what did you mean with
"generating the OM just using the Torque generator package?", Greg?
Did you mean executing the java call from the command line?
I knew I could futz (that's a technical term!!) with the limits via
ulimit, but users can usually not increase the number of descriptors
beyond a certain limit (1024 for my system). And with 240 tables and
4 classes to generate per table, I was probably just hitting that
limit with the wrong vm.
thanks again for your help!
h.
On Apr 25, 2006, at 8:22 AM, Greg Monroe wrote:
FWIW, you generally don't have to increase the system limits
as a whole to get around this problem. There is a command called
ulimit that lets you increase a specific sessions files open
limit from the default of 1024.
When you say good-sized, what does that mean in terms of tables,
etc?
Have you tried generating the OM just using the Torque generator
package? This would help determine if it's Torque or something
else.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
