Kris Schneider wrote:
There were definitely some problems with jcp.org, but they seem to have been resolved:
JSP 2.0: http://jcp.org/aboutJava/communityprocess/final/jsr152/
Kris Schneider wrote:For better or worse, that's actually a quote from the JSP 2.0 Spec. (section JSP.2.3.7). However, the spec. also provides some detail to give the definition of "empty" some context:
" The empty operator is a prefix operation that can be used to determine if a value is null or empty."
Originally posted by Ilja Preuss:
You can. The connection wizard is quite good - you tell it what you want to do and how your server is configured, and it will create a configuration and tell you what manual steps you need to do.
DailyRazor Support
Dear Customer,
Your application was overloading the server, we had to stop your tomcat. You can start it at any time, however if we will notice that it's consuming too much of server resources we will suspend your account.
Thank you.
Originally posted by Ernest Friedman-Hill:
Ah! OK, now we're getting somewhere. Read this, my friend:
http://blogs.sun.com/fkieviet/entry/classloader_leaks_the_dreaded_java
Thanks for that article.
Looks very much like what's happening is that your app is handing out references to some of its objects, so that when it is reloaded/redeployed those object persist and prevent the old classes from being collected.
Originally posted by William Brogden:
It is also possible that even with correct memory management code, a number of "simultaneous" requests could exceed the allocated memory. What facilities for memory configuration does "DailyRazor" provide?
DailyRazor support:
PermGen space is always limited to 64Mb, this is a hard limit that will not be overriden. If your application require more PermGen space you should upgrade to dedicated server, where you will be able to have as much space as you like.
In any case, this issue has nothing to do with server itself, it's only your application that require too much memory to run, so basically you have only these choices: 1. Somehow optimise your application to use less classes and libraries or 2. Upgrade to dedicated server.
Originally posted by David O'Meara:
I have been looking at the behaviour of ""+x versus String.valueOf(x) and while the first is slightly shorter and possibly easier to read, my guess is that it involves 3 String instances (one that is probably pooled) while the second would only create the one String instance.
Not a massive difference, but some of them are right in the core of our logic so I thought it was worth pursuing.
Originally posted by Pat Farrell:
Hey, I'm a professional programmer, I expect to get paid for it to work perfectly.
Originally posted by Pat Farrell:
Looks like you are getting help and making progress.
Java is actually fairly easy to do the node/tree stuff