On our development system it looks like this: [EMAIL PROTECTED] ~]# ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited max nice (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 16384 max locked memory (kbytes, -l) 32 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 max rt priority (-r) 0 stack size (kbytes, -s) 10240 cpu time (seconds, -t) unlimited max user processes (-u) 2047 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
For the system at our client I have to check with their administrator. Benjamin 2007/9/14, Matej Knopp <[EMAIL PROTECTED]>: > > It doesn't look like the jars are issue. What is your file handle > limits? Maybe it's just set too low. > > -Matej > > On 9/14/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > Is this only at your client's site? Why doesn't this show on your own > > test servers? It seems like a configuration issue. > > > > One way to get around this problem is to unzip the jar and put the > > contents on the classpath. This will solve the problem for your client > > until we have found the cause. > > > > Martijn > > > > -- > > Buy Wicket in Action: http://manning.com/dashorst > > Apache Wicket 1.3.0-beta3 is released > > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
